Error removing instances of successfully completed cloud dataflow jobs -


I see the following error when the job is close to:

  2015- 01- 22T11: 25: 59.785 Z (6A 513 162 C 75566 FA): early worker pool Teedaun 2015-01-22T11: 25: 59.793 J: (6A 513 162 C 7556 A9 a): workers stop by the pool as the asynchronous ... 2015-01-22T11: 35: 59.867 J: (564988ad48e37d5d): perform failure phase failure 1 2015-01-22T11: 35: 59.870 Z: (564988ad48e37857): workflow failed. Reason: (6a513162c7556e36): Step teardown_resource_global_gce_worker_pool69: resource worker _pool_resource 2015-01-22T11: 36: 00.121 Z failed to close: (564988ad48e37bc8): input generator stop 2015-01-22T11: 36: 00.153Z: (E-9 B 8 a 1 B 4 a 36 D 7 A3): cleaning 2015-01-22T11: 36: 00.169 J: (E9be8alb4a36db46): tear pending resources ... January 22, 2015 1:36:01 PM com.google. cloud.dataflow.sdk.runners.BlockingDataflowPipelineRunner run information with job condition FAILED  

after that, workers examples are not deleted and I manually kill them Will not.

Is this a known bug?

Thank you, G

Sorry for the problem This is a well-known issue is. When we address it, then I will update this thread, and thank you for your patience.

Update

This problem has been fixed in the service.


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -