为什么Dataflow工作人员不尊重悉尼新区域？

I'm trying to set the region of my Dataflow (Java SDK 2.0.0) pipeline to one of australia-southeast1-a, australia-southeast1-b, or australia-southeast1-c (i.e. one of the regions in Sydney):

我正在尝试将我的Dataflow（Java SDK 2.0.0）管道区域设置为澳大利亚 - 东南1-a，澳大利亚 - 东南1-b或澳大利亚 - 东南1-c（即悉尼的其中一个区域）之一：

public static void main(String... args) {
        DataflowPipelineOptions options = PipelineOptionsFactory
                .fromArgs(args)
                .withValidation()
                .as(DataflowPipelineOptions.class);
        options.setRunner(DataflowRunner.class);
        options.setJobName("sydney-dataflow-pipeline");
        options.setStagingLocation("gs://<redacted>/jars");
        options.setTempLocation("gs://<redacted>/jars");
        options.setRegion("australia-southeast1-a"); //<<--trying to set region to Sydney
        options.setMaxNumWorkers(3);
        Pipeline pipeline = Pipeline.create(options);
        pipeline.apply
        [..]
        pipeline.run(); //run it
    }

However, the GCE instances in the worker pool keep spinning up in the US region (us-central1-f):

但是，工作池中的GCE实例在美国地区（us-central1-f）继续开放：

Why are the workers not spinning up in the specified region?

为什么工人不在指定地区开火？

1 个解决方案

#1

The Javadoc lists this method as @Hidden and @Experimental, with the note:

Javadoc将此方法列为@Hidden和@Experimental，并附注：

"The Cloud Dataflow service does not yet honor this setting. However, once service support is added then users of this SDK will be able to control the region."

“Cloud Dataflow服务尚未遵循此设置。但是，一旦添加了服务支持，此SDK的用户将能够控制该区域。”

The setZone method can still be used to control worker location.

setZone方法仍可用于控制工作人员的位置。

#1