[
https://issues.apache.org/jira/browse/BEAM-11811?focusedWorklogId=607967&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-607967
]
ASF GitHub Bot logged work on BEAM-11811:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 07/Jun/21 16:16
Start Date: 07/Jun/21 16:16
Worklog Time Spent: 10m
Work Description: zhoufek commented on pull request #14938:
URL: https://github.com/apache/beam/pull/14938#issuecomment-856075593
It looks like some license expired and all the Jenkins instances were taken
offline, so any check depending on it seems permanently stuck in the pending
state.
--
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: 607967)
Time Spent: 3h 50m (was: 3h 40m)
> Don't allow numWorkers > maxNumWorkers.
> ---------------------------------------
>
> Key: BEAM-11811
> URL: https://issues.apache.org/jira/browse/BEAM-11811
> Project: Beam
> Issue Type: Improvement
> Components: runner-dataflow
> Reporter: Kyle Weaver
> Assignee: Zachary Houfek
> Priority: P3
> Time Spent: 3h 50m
> Remaining Estimate: 0h
>
> Right now Dataflow jobs misconfigured with numWorkers > maxNumWorkers will be
> allowed to submit, but will get stuck in the PENDING state, and cannot be
> cancelled normally by users. We should implement a sanity check in each SDK
> to prevent misconfigured jobs from submitting.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
