You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Prateek Maheshwari (JIRA)" <ji...@apache.org> on 2018/04/23 17:50:00 UTC

[jira] [Updated] (SAMZA-1682) Task callback timeout should not apply when wrapping StreamTask with AsyncStreamTaskAdapter

     [ https://issues.apache.org/jira/browse/SAMZA-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prateek Maheshwari updated SAMZA-1682:
--------------------------------------
    Fix Version/s: 0.15.0

> Task callback timeout should not apply when wrapping StreamTask with AsyncStreamTaskAdapter
> -------------------------------------------------------------------------------------------
>
>                 Key: SAMZA-1682
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1682
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Prateek Maheshwari
>            Priority: Minor
>             Fix For: 0.15.0
>
>
> When using the AsyncRunLoop (i.e., with "single.thread.mode" = false), StreamTasks are wrapped in AsyncStreamTaskAdapter. This means that the task.callback.timeout.ms configuration applies to these StreamTask too. This can cause confusion since the user isn't expecting any callbacks. The documentation for the task.callback.timeout.ms configuration is also unclear, and states that it only applies to AsyncStreamTask.
> We should default the callback to Integer.MAX_VALUE when wrapping an StreamTask.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)