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-1683) Deprecate RunLoop and job.container.single.thread.mode configuration

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

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

> Deprecate RunLoop and job.container.single.thread.mode configuration
> --------------------------------------------------------------------
>
>                 Key: SAMZA-1683
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1683
>             Project: Samza
>          Issue Type: Improvement
>            Reporter: Prateek Maheshwari
>            Priority: Minor
>             Fix For: 0.15.0
>
>
> It's often unclear to users what the difference between "job.container.single.thread.mode"
> and "job.container.thread.pool.size" configurations is. 
> Since, AsyncRunLoop has been the default for a while and it can mimic single threaded RunLoop behavior with "job.container.thread.pool.size" == 0, we should remove the older RunLoop class and the corresponding "job.container.single.thread.mode" configuration.



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