[
https://issues.apache.org/jira/browse/BEAM-14449?focusedWorklogId=774783&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-774783
]
ASF GitHub Bot logged work on BEAM-14449:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 25/May/22 19:23
Start Date: 25/May/22 19:23
Worklog Time Spent: 10m
Work Description: KevinGG commented on PR #17736:
URL: https://github.com/apache/beam/pull/17736#issuecomment-1137763456
R: @rohdesamuel
PTAL, thx!
Issue Time Tracking
-------------------
Worklog Id: (was: 774783)
Time Spent: 40m (was: 0.5h)
> Support cluster provisioning when using Flink on Dataproc
> ---------------------------------------------------------
>
> Key: BEAM-14449
> URL: https://issues.apache.org/jira/browse/BEAM-14449
> Project: Beam
> Issue Type: Improvement
> Components: runner-py-interactive
> Reporter: Ning
> Assignee: Ning
> Priority: P2
> Attachments: image-2022-05-16-11-25-32-904.png,
> image-2022-05-16-11-28-12-702.png
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Provide the capability for the user to explicitly provision a cluster.
> Current implementation provisions each cluster at the location specified by
> GoogleCloudOptions using 3 worker nodes. There is no explicit API to
> configure the number or shape of workers.
> We could use the WorkerOptions to allow customers to explicitly provision a
> cluster and expose an explicit API (with UX in notebook extension) for
> customers to change the size of a cluster connected with their notebook
> (until we have an auto scaling solution with Dataproc for Flink).
> The API looks like this when configuring the workers for a dataproc cluster
> when creating it:
> !image-2022-05-16-11-25-32-904.png!
> An example request setting the masterConfig and workerConfig:
> !image-2022-05-16-11-28-12-702.png!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
