apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-596) Committed method on operators not called when stream locality is THREAD_LOCAL
Date Tue, 17 Jan 2017 07:17:26 GMT

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

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

Github user francisf closed the pull request at:

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


> 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
>
> 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.4#6332)

Mime
View raw message