Mailing-List: contact dev-help@apex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@apex.apache.org
Date: Fri, 1 Jul 2016 14:44:11 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: dev@apex.incubator.apache.org
Message-ID: <JIRA.12919391.1445705734000.5262.1467384251057@Atlassian.JIRA>
In-Reply-To: <JIRA.12919391.1445705734000@Atlassian.JIRA>
References: <JIRA.12919391.1445705734000@Atlassian.JIRA> <JIRA.12919391.1445705734000@arcas>
Subject: [jira] [Commented] (APEXCORE-222) Delegate Buffer Server purge to
 StreamingContainer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 01 Jul 2016 14:44:17 -0000


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

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

Github user sandeshh commented on the issue:

    https://github.com/apache/apex-core/pull/350
  
    All the review comments has been addressed.


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