[
https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088117#comment-16088117
]
Vinay Bangalore Srikanth commented on APEXCORE-759:
---------------------------------------------------
I tried these as well -
1x4x1 - THREAD_LOCAL is set between each of the two operators ( a&b, b&c) -
Containers are killed.
1x4x1 - THREAD_LOCAL is set between the first two operators only (a&b only) -
The first two operators execute in container-1, unifier and the third operator
in container-2
And,
1x4x1 - CONTAINER_LOCAL is set between each of the two operators ( a&b, b&c) -
All operators are executed in one container. It works fine. (Unlike the
corresponding case in THREAD_LOCAL)
1x4x1 - CONTAINER_LOCAL is set between the first two operators only (a&b only)
- The first two operators execute in container-1, unifier and the third
operator in container-2
> Topology validation needs to happen correctly for operators connected using
> THREAD_LOCAL stream locality
> --------------------------------------------------------------------------------------------------------
>
> Key: APEXCORE-759
> URL: https://issues.apache.org/jira/browse/APEXCORE-759
> Project: Apache Apex Core
> Issue Type: Bug
> Reporter: Vinay Bangalore Srikanth
> Attachments: apex (1).log, apex.log
>
>
> In my application -
> http://node0.morado.com:9090/static/#/ops/apps/application_1499808956620_0190
> , I have set the locality to be THREAD_LOCAL.
> Upstream operator - Random string generator (with 4 partitions)
> Downstream operator - Custom console operator (with 5 partitions)
> The containers are getting killed. Exceptions from container-launch are seen.
> Logical message has to be displayed by handling exceptions.
> Logs are attached for one of the containers - Id: 01_000126 that was killed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
