You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@apex.apache.org by "Sandesh (JIRA)" <ji...@apache.org> on 2016/06/14 14:53:01 UTC

[jira] [Assigned] (APEXCORE-222) Delegate Buffer Server purge to StreamingContainer

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

Sandesh reassigned APEXCORE-222:
--------------------------------

    Assignee: Sandesh

> Delegate Buffer Server purge to StreamingContainer
> --------------------------------------------------
>
>                 Key: APEXCORE-222
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-222
>             Project: Apache Apex Core
>          Issue Type: Improvement
>            Reporter: Thomas Weise
>            Assignee: Sandesh
>
> Currently the purge requests are sent to the buffer servers from the app master. This interaction exists parallel to the heartbeat protocol. Instead, the committed window ID that is propagated through the heartbeat response can be used in StreamingContainer to initiate the purge with the local buffer server, similar to how the committed callback on the operator occurs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)