You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by "Tushar Gosavi (JIRA)" <ji...@apache.org> on 2017/05/05 10:47:11 UTC

[jira] [Closed] (APEXCORE-596) Committed method on operators not called when stream locality is THREAD_LOCAL

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

Tushar Gosavi closed APEXCORE-596.
----------------------------------

Closing after 3.6.0 release

> Committed method on operators not called when stream locality is THREAD_LOCAL
> -----------------------------------------------------------------------------
>
>                 Key: APEXCORE-596
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-596
>             Project: Apache Apex Core
>          Issue Type: Bug
>    Affects Versions: 3.5.0
>            Reporter: Francis Fernandes
>            Assignee: Francis Fernandes
>            Priority: Minor
>             Fix For: 3.6.0
>
>
> When the locality of the stream connecting the two operators is Locality.THREAD_LOCAL, the committed method is not called for some operators. These operators implement the Operator.CheckpointListener. e.g. AbstractFileOutputOperator
> For thread local during activate  we do not set the thread in the node's context
> Because the thread is not set, we skip this operator in the processHeartBeatResponse and the committed is not called
> {code}
> if (thread == null || !thread.isAlive()) {
>           continue;
>         }
> {code}
> We need this condition for invalid operators (operator failures) in case of other localities. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)