[ 
https://issues.apache.org/jira/browse/APEXCORE-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371960#comment-15371960
 ] 

ASF GitHub Bot commented on APEXCORE-222:
-----------------------------------------

GitHub user sandeshh reopened a pull request:

    https://github.com/apache/apex-core/pull/350

    APEXCORE-222 Purging the stale data present in the bufferserver, dire…

    …ctly from the streaming container.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sandeshh/apex-core APEXCORE-222

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/apex-core/pull/350.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #350
    
----
commit 36e3d333d0c4f22d07701cefacaacae0ab81a0eb
Author: sandeshh <sandesh.he...@gmail.com>
Date:   2016-06-28T03:58:07Z

    APEXCORE-222 purging of the buffer server is done from the streaming 
container, instead of StreamingContainerManager

----


> 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)

Reply via email to