apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pramod Immaneni (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (APEXCORE-759) THREAD_LOCAL exception not handled.
Date Fri, 14 Jul 2017 01:07:01 GMT

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

Pramod Immaneni edited comment on APEXCORE-759 at 7/14/17 1:06 AM:
-------------------------------------------------------------------

We catch this when parallel partitioning and MxN are specified at the same time, maybe we
are not doing it in this case. It may not be possible to catch this at dag validation, not
until physical plan is created, because of custom partitioners.


was (Author: pramodssimmaneni):
We catch this when parallel partitioning and MxN are specified at the same time, maybe we
are not doing it in this case. It may not be possible to catch this at dag validation, not
until physical plan is created.

> THREAD_LOCAL exception not handled. 
> ------------------------------------
>
>                 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