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/04 18:59:00 UTC

[jira] [Created] (SAMZA-1636) Disallow setting job.container.thread.pool.size value to 1

Prateek Maheshwari created SAMZA-1636:
-----------------------------------------

             Summary: Disallow setting job.container.thread.pool.size value to 1
                 Key: SAMZA-1636
                 URL: https://issues.apache.org/jira/browse/SAMZA-1636
             Project: Samza
          Issue Type: Bug
            Reporter: Prateek Maheshwari
            Assignee: Xinyu Liu


Setting job.container.thread.pool.size to 1 should make SamzaContainer ignore it and default to 0 instead. With a single processing thread, the extra latency of the message handoff is unnecessary overhead. 

Configuration reference should also be updated to clarify the new behavior. We should also remove the following statement: "Note that the thread pool is not applicable to [sic] AsyncStremTask.processAsync(). ", since the thread pool size can still allow window/commit to proceed in parallel for AsyncStreamTask.

[~xinyu], do you know of any use case where thread.pool.size == 1 is better than sync processing?

 



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