[
https://issues.apache.org/jira/browse/APEXCORE-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187425#comment-16187425
]
ASF GitHub Bot commented on APEXCORE-769:
-----------------------------------------
vrozov closed pull request #567: APEXCORE-769 Clearing oioGroups to remove
information from prior depl…
URL: https://github.com/apache/apex-core/pull/567
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> activate() called multiple times for redeployed operator when stream is
> THREAD_LOCAL
> -------------------------------------------------------------------------------------
>
> Key: APEXCORE-769
> URL: https://issues.apache.org/jira/browse/APEXCORE-769
> Project: Apache Apex Core
> Issue Type: Bug
> Reporter: Francis Fernandes
> Assignee: Francis Fernandes
>
> activate() is called during the redeployment of operators when the stream
> locality is set to THREAD_LOCALITY. This happens for all the child operator
> nodes when they are redeployed in the same container that were previously
> deployed. A simple way to simulate this is by killing an upstream(non
> thread-local) operator's container.
> The cause for this happening is, when setupOiOGroups() is called inside
> StreamingContainer, the child nodes are appended to the oioGroups values.
> These values were populated as a part of the previous deployment. A possible
> fix is to call oioGroups.clear() at the beginning of setOiOGroups().
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
