[
https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088963#comment-16088963
]
Vlad Rozov commented on APEXCORE-759:
-------------------------------------
Whether stream locality is strict or simply a hint needs to be a part of a
stream locality attribute itself not a setting as some application or even part
of an application's DAG may need to enforce it in case the platform
choice/decision is incorrect. The question is what should be the default, and
IMO, stream locality should be considered as a hint, not as a strict
enforcement. Currently, stream locality is required as the platform itself does
not perform any optimization and blindly follows stream locality attribute. In
this particular case, whether it is THREAD_LOCAL or CONTAINER_LOCAL should not
matter much for an application and the stream locality may change from
THREAD_LOCAL to CONTAINER_LOCAL and back when the partition scheme changes from
1xN to MxN and back to 1xN (should an application support such re-configuration
as in the case of dynamic partitioning).
> 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)
