[ 
https://issues.apache.org/jira/browse/BEAM-8151?focusedWorklogId=342937&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-342937
 ]

ASF GitHub Bot logged work on BEAM-8151:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 13/Nov/19 21:58
            Start Date: 13/Nov/19 21:58
    Worklog Time Spent: 10m 
      Work Description: aaltay commented on pull request #9477: [BEAM-8151, 
BEAM-7848] Swap to using an unbounded thread pool which shrinks when threads 
are not being used.
URL: https://github.com/apache/beam/pull/9477#discussion_r346016216
 
 

 ##########
 File path: sdks/python/apache_beam/runners/worker/sdk_worker_main.py
 ##########
 @@ -190,7 +190,7 @@ def _get_worker_count(pipeline_options):
   future releases.
 
   Returns:
-    an int containing the worker_threads to use. Default is 12
+    an int containing the worker_threads to use. Default is 10000.
 
 Review comment:
   Also update L206? (`return 12`)
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 342937)
    Time Spent: 10h 50m  (was: 10h 40m)

> Allow the Python SDK to use many many threads
> ---------------------------------------------
>
>                 Key: BEAM-8151
>                 URL: https://issues.apache.org/jira/browse/BEAM-8151
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-py-core, sdk-py-harness
>            Reporter: Luke Cwik
>            Assignee: Luke Cwik
>            Priority: Major
>          Time Spent: 10h 50m
>  Remaining Estimate: 0h
>
> We need to use a thread pool which shrinks the number of active threads when 
> they are not being used.
>  
> This is to prevent any stuckness issues related to a runner scheduling more 
> work items then there are "work" threads inside the SDK harness.
>  
> By default the control plane should have all "requests" being processed in 
> parallel and the runner is responsible for not overloading the SDK with too 
> much work.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to