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) THREAD_LOCAL exception not handled.
Date Fri, 14 Jul 2017 00:14:00 GMT

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

Thomas Weise commented on APEXCORE-759:

Are you sure this is a bug? If not, then please ask a question on the mailing list. It only
makes sense to have a THREAD_LOCAL stream when upstream and downstream operator are chained
(parallel partitioned), in which case the partition counts will be the same.

> 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

View raw message