apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandesh (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (APEXCORE-222) Delegate Buffer Server purge to StreamingContainer
Date Mon, 18 Jul 2016 01:44:20 GMT

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

Sandesh resolved APEXCORE-222.
------------------------------
       Resolution: Fixed
    Fix Version/s: 3.5.0

> 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
>             Fix For: 3.5.0
>
>
> 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)

Mime
View raw message