Sam McVeety
Reputation: 3214
Why does Dataflow leave behind some disks after pipeline update?
After running "update" on my pipeline, I noticed that there are newly created persistent disks that are not attached to any instances after 10+ minutes.
Upvotes: 3
Views: 56
Answers (1)
Sam McVeety
Reputation: 3214
This is an ongoing known issue with the Dataflow service that causes orphaned disks during the pipeline update process. These extra disks can be safely deleted. The team is working on a fix.
UPDATE: The issue has now been fixed in the Dataflow service.
Upvotes: 2
Related Questions
- Update a pipeline in Google Cloud Dataflow
- Google Dataflow Apache beam version upgrade fails if we update and existing pipeline
- When does a pubsub message get acked in a Dataflow pipeline?
- How to update a Dataflow incompatible pipeline without loosing in data?
- Dataflow pipeline does not start with -v parameter
- Force update of SideInput on updating Dataflow pipeline
- Dataflow: Accessing a value provider after the pipeline is complete
- Executing a pipeline only after another one finishes on google dataflow