apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Weise (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-759) Operators connected using THREAD_LOCAL stream locality should enforce parallel partition scheme
Date Fri, 14 Jul 2017 01:47:00 GMT

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

Thomas Weise commented on APEXCORE-759:
---------------------------------------

There is no restriction for CONTAINER_LOCAL. THREAD_LOCAL requires a common root, hence 4
x 5 won't work, but 1 x N should, but please double check... 

> Operators connected using THREAD_LOCAL stream locality should enforce parallel partition
scheme
> -----------------------------------------------------------------------------------------------
>
>                 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)

Mime
View raw message