[
https://issues.apache.org/jira/browse/BEAM-14449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ning updated BEAM-14449:
------------------------
Description:
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!
was:
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).
> 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
>
>
> 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!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
