apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Weise (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (APEXMALHAR-1938) Operator checkpointing in distributed in-memory store
Date Sun, 03 Jan 2016 08:59:44 GMT

     [ https://issues.apache.org/jira/browse/APEXMALHAR-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Thomas Weise updated APEXMALHAR-1938:
    Reporter: Ashish Tadose  (was: Ashish Pareek)

> Operator checkpointing in distributed in-memory store
> -----------------------------------------------------
>                 Key: APEXMALHAR-1938
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-1938
>             Project: Apache Apex Malhar
>          Issue Type: New Feature
>          Components: adapters other
>            Reporter: Ashish Tadose
>            Assignee: Ashish Tadose
>            Priority: Minor
>              Labels: roadmap
> 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

This message was sent by Atlassian JIRA

View raw message