[
https://issues.apache.org/jira/browse/SAMZA-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15868607#comment-15868607
]
ASF GitHub Bot commented on SAMZA-1084:
---------------------------------------
GitHub user navina opened a pull request:
https://github.com/apache/samza/pull/54
SAMZA-1084 - User thread does not see errors from the processor thread
Adding a ProcessorLifecycleCallback for specifying user-defined error
handling
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navina/samza SAMZA-1084
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/samza/pull/54.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #54
----
commit f473f73cbb60047e77eac5d715e2dd2b5ef51234
Author: navina <[email protected]>
Date: 2017-02-15T21:32:25Z
SAMZA-1084 - User thread does not see errors from the processor thread when
using the StreamProcessor API
----
> User thread does not see errors from the processor thread when using the
> StreamProcessor API
> --------------------------------------------------------------------------------------------
>
> Key: SAMZA-1084
> URL: https://issues.apache.org/jira/browse/SAMZA-1084
> Project: Samza
> Issue Type: Bug
> Reporter: Navina Ramesh
> Assignee: Navina Ramesh
> Fix For: 0.13.0
>
>
> The current user model for StreamProcessor API allows the user to start
> (asynchronous) and stop processor. awaitStart allows the user to wait until
> the processor actually initializes and starts processing messages. There are
> certain limitations to this API:
> 1. In case the processor fails during processing or prior to processing, the
> error is not propagated to the user context. It is very hard to troubleshoot
> and take action on error/shutdown.
> 2. There is also no way for the user to check the status of the processor.
> 3. (More of implementation detail than an API issue) Another issue is that we
> are using an Executor to run the container in a separate thread. The
> container uses another Executor to run the tasks. We need to understand the
> performance impact of using 2 levels of Executors in a single StreamProcessor
> instance.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
