Forced Parallelism Configuration for Hadoop Change Data Capture

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Hadoop's default configurations result in poor performance and throughput when processing Change Data Capture (CDC) data, limiting parallelism due to file size constraints, which fails to meet service level agreements (SLAs).

Innovation Solution

Implementing a forced parallelism configuration across all Hadoop data nodes during critical processing steps, such as data quality checks and change data capture record applications, to enhance processing efficiency and throughput.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If default Hadoop configurations are used to process CDC data, then the system is simple to operate, but performance and throughput are poor causing missed SLAs

Engineering Contradiction:
Improvedata throughputVSAvoidparallelism configuration
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent changes Hadoop configuration parameters to enable forced parallelism across all data nodes. Specifically, it modifies the parallelism configuration from the default file-size-based limitation to a forced parallelism mode that distributes CDC processing across the full set of data nodes, thereby dramatically improving throughput while maintaining operational simplicity through configuration management

Inventive Principle:
Principle #35Parameter changes

2Productivity

If forced parallelism configuration is applied across all data nodes, then performance and throughput improve significantly, but system complexity increases

Engineering Contradiction:
Improveprocessing efficiencyVSAvoidparallelism configuration
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the CDC processing workload across all available data nodes in the Hadoop cluster. By dividing the processing task into parallel segments that can be executed simultaneously on multiple nodes, the system achieves significant performance improvement. The segmentation is managed through configuration that assigns different portions of the CDC data stream to different data nodes for parallel processing

Inventive Principle:
Principle #1Segmentation

3Productivity

If parallelism is constrained to file block size, then the system is easier to manage, but the number of data nodes involved is limited reducing throughput

Engineering Contradiction:
Improvenumber of data nodes utilizedVSAvoidparallelism management
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent implements dynamic parallelism management that adapts to the CDC workload requirements. Instead of being statically constrained by file block sizes, the system dynamically adjusts the degree of parallelism by forcing utilization of all available data nodes. This dynamic approach allows the system to optimize resource utilization based on the actual processing needs of CDC operations rather than being limited by fixed configuration parameters

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11669509B2System and method for achieving optimal change data capture (CDC) on hadoop
Publication Date: 2023.06.06 JPMORGAN CHASE BANK NA
  • US11669509B2 patent drawing
  • US11669509B2 patent drawing
  • US11669509B2 patent drawing

AI summary

An embodiment of the present invention is directed to configuring optimal parallelism on Hadoop processes at specific processing points for improved performance and throughput. An embodiment of the present invention forces Hadoop into high parallelism independent of a HDFS file size. An embodiment of the present invention achieves an order of magnitude improvement in performance and data throughputs to meet the SLAs. An embodiment of the present invention provides a design pattern unique to distributed processing in Hadoop to accomplish the required data throughputs for the CDC process.