[APEXMALHAR-1938] Operator checkpointing in distributed in-memory store

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.4.0
• Component/s: adapters other
• Labels: roadmap
• Assignee: Ashish Tadose
• Reporter: Ashish Tadose
• Created: 11/Dec/15 16:21
• Updated: 24/May/16 17:05
• Resolved: 22/Feb/16 19:47

Description

Currently Apex engine provides operator checkpointing in Hdfs ( with Hdfs backed StorageAgents i.e. FSStorageAgent & AsyncFSStorageAgent )
As operator check-pointing is critical functionality of Apex streaming platform to ensure fault tolerant behavior, platform should also provide alternate StorageAgents which will work seamlessly with large applications that requires Exactly once semantics.
HDFS read/write latency is limited and doesn't improve beyond certain point because of disk io & staging writes. Having alternate strategy to this check-pointing in fault tolerant distributed in-memory grid would ensure application stability and performance is not impacted by checkpointing

This feature will add below functionalities

• A KeyValue store interface which is used by In-memory checkpointing storage agent.
• Abstract implementation of KeyValue storage agent which can be configured with concrete implementation of KeyValue store for checkpointing.
• Concrete implementation of In memory storage agent for Apache Geode

This feature depends on below APEX core feature
https://issues.apache.org/jira/browse/APEXCORE-283

• Interface for storage agent to provide application id
• Stram client changes to pass applicationId

Sub-Tasks

• Remove redundant StorageAgent interface Malhar library: Closed