Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
Description
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.
Attachments
Issue Links
- is duplicated by
-
SAMZA-1680 There should be no TaskCallbackTimeoutException for StreamTask jobs.
- Resolved