You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/03/19 17:19:00 UTC

[jira] [Commented] (BEAM-11811) Don't allow numWorkers > maxNumWorkers.

    [ https://issues.apache.org/jira/browse/BEAM-11811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17305052#comment-17305052 ] 

Beam JIRA Bot commented on BEAM-11811:
--------------------------------------

This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.

> 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: Kyle Weaver
>            Priority: P3
>              Labels: stale-assigned
>          Time Spent: 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)