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

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

                Author: ASF GitHub Bot
            Created on: 07/Sep/19 01:58
            Start Date: 07/Sep/19 01:58
    Worklog Time Spent: 10m 
      Work Description: aaltay commented on issue #9477: [BEAM-8151, BEAM-7848] 
Up the max number of threads inside the SDK harness to a default of 10k
URL: https://github.com/apache/beam/pull/9477#issuecomment-529062034
 
 
   Precommit is failing with:
   
   16:09:15 collapsing-thread-pool-executor 2018.6 has requirement 
futures==3.2.0, but you have futures 3.3.0.
   16:09:15 ERROR: InvocationError for command 
/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Python_Phrase/src/sdks/python/test-suites/tox/py2/build/srcs/sdks/python/target/.tox-py27-lint/py27-lint/bin/pip
 check (exited with code 1)
   16:09:15 py27-lint run-test-post: commands[0] | 
/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Python_Phrase/src/sdks/python/test-suites/tox/py2/build/srcs/sdks/python/scripts/run_tox_cleanup.sh
   16:09:15 ___________________________________ summary 
____________________________________
   16:09:15 ERROR:   py27-lint: commands failed
   
   The reason is a dependency conflict.
   collapsing-thread-pool-executor requires futures == 3.2.0 for python 2.7 
(https://github.com/ftpsolutions/collapsing-thread-pool-executor/blob/master/setup.py#L22)
   
   Beam's setup.py accepts "'futures>=3.2.0,<4.0.0; python_version < "3.0"',"
   
   We can do a few things:
   - Update collapsing-thread-pool-executor to relax the upper bound for 
futures dependency
   - Update beam to restict its futures dependency to use 3.2.0
 
----------------------------------------------------------------
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:
us...@infra.apache.org


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

    Worklog Id:     (was: 308260)
    Time Spent: 5h 20m  (was: 5h 10m)

> 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: 5h 20m
>  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.2#803003)

Reply via email to