Distributed Data Ingestion and Processing System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems for processing and analyzing large data sets, such as those used in customer support systems, face challenges in scalability and efficiency, particularly when handling increasing data loads and supporting multiple operating system versions, as they are not easily adaptable to accommodate growing data volumes and complex relational databases.

Innovation Solution

A distributed analytic computing system architecture that includes an ingestion section for preprocessing and storing data, a processing section for performing Map Reduce operations using HDFS and HBASE, and a data access interface for sophisticated indexing and analytics, allowing for scalable handling of large data sets by breaking data into smaller sections and using metadata for efficient storage and retrieval.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional systems (NFS, RDBMS, Java, perl) are used for data processing, then current data loads can be handled, but scalability to support future products and increasing data volume is limited

Engineering Contradiction:
ImprovescalabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments data into smaller blocks distributed across multiple nodes in a Hadoop cluster. Each node independently processes assigned data blocks, enabling scalable handling of increasing data volumes without requiring complex monolithic system architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The Hadoop framework provides a universal platform that can handle diverse data processing tasks including MapReduce computations, distributed file storage (HDFS), and various data formats. This multi-functional architecture replaces multiple specialized systems (NFS, RDBMS, Java, perl) with a single scalable infrastructure.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Productivity

If Map Reduce distributed computing system is used, then large data sets can be processed efficiently, but system complexity increases with master node and data node coordination

Engineering Contradiction:
Improvedata processing efficiencyVSAvoidsystem architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The MapReduce system implements self-service through automatic task scheduling, dynamic resource allocation, and fault tolerance mechanisms. The master node automatically assigns tasks to data nodes, monitors execution, and handles failures without manual intervention, reducing operational complexity despite architectural sophistication.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system dynamically adapts to varying workloads by automatically allocating computing resources, adjusting task distribution across nodes, and scaling cluster capacity. This dynamic behavior enables efficient processing of different data volumes without requiring static, over-provisioned architecture.

Inventive Principle:
Principle #15Dynamics

3Quantity of substance

If data is stored in distributed file system (HDFS), then data capacity and accessibility improve, but data retrieval and processing time may increase due to distributed nature

Engineering Contradiction:
Improvedata storage capacityVSAvoiddata retrieval time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

Data is divided into blocks distributed across multiple storage nodes, enabling parallel read operations. Multiple nodes can simultaneously retrieve different blocks needed for processing, reducing overall retrieval time compared to sequential access from a single storage system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary data localization by storing data blocks close to where they will be processed. Map tasks are scheduled on nodes that already have or can quickly access the required data blocks, minimizing network transfer time and accelerating processing.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9582541B2Systems, methods, and computer program products to ingest, process, and output large data
Publication Date: 2017.02.28 NETAPP INC
  • US9582541B2 patent drawing
  • US9582541B2 patent drawing
  • US9582541B2 patent drawing

AI summary

A method for ingesting data, the method comprising receiving a file including a plurality of portions, each of the portions corresponding to a respective characteristic of a hardware or software component in a deployed system; breaking the file into a plurality of sections, each of the sections corresponding to a respective portion of the file; for each section, adding first metadata to uniquely identify the file and provide a name for the section; and distributing the sections to a plurality of container files.