GCS Soft Delete Objects - Very Bad Experience

We noticed by mid Feb that soft delete for GCS is enabled for all the buckets, the feature official release date was in March (https://cloud.google.com/resources/storage/soft-delete-announce?hl=en)
 
Enabling soft delete from GCP side caused bucket sizes/number of objects to increase heavily , some buckets increased very aggressively due to rewrite nature of the application 
 
Total number of soft deleted objects in a single project increased heavily ( double our current live objects)- is it expected to start paying for this service by June without requesting it ?
 
 
We use hadoop connector  for some heavy operations with GCS (read/write/rewrite etc ... )
 
We noticed major degradation in performance recently listing and getting objects metadata which heavily depending on number of objects 
 
That Change (enabling soft delete) impacted our business heavily , and we were expecting proper communication before applying it.

it's expected to be optional and customer to enable it per bucket in case it's needed 
 
If our account is enabled to access new features, we are expecting to explain similar features before applying it with impact highlighted.
 
Do we have any benchmarking details related to hadoop gcs connector with soft delete objects ?
4 5 749
5 REPLIES 5

So, I understand your concerns about the unexpected impact of GCS soft delete on your operations. It's important to reach out to Google Cloud Support for assistance and clarification on the billing aspect, expressing the negative impact on performance and the desire for advanced communication on feature rollout. Inquire about benchmarking details for Hadoop GCS connector with soft delete objects to better understand performance implications.

Pero cómo google hace pruebas en sus recursos sin permiso?! 

have you found a way to disable the soft-delete feature from a bucket (or better yet, project and org-wide)? I have had trouble finding a soft-delete related setting in the UI or terraform provider

the below commands can help to disable soft-delete-objects , it's per bucket or can use gs://* for all the bucket in a project

### To disable soft delete 
$gcloud storage buckets update --clear-soft-delete gs://BUCKET-NAME

but i face some issues executing disable commands reported in the below link:
https://issuetracker.google.com/issues/327390321 

To automatically change the retention duration of GCS soft delete, each time a new GCS bucket is created in your org, you can use a combination of Audit Log -> Eventarc -> Cloud Run. See this code example.

Top Labels in this Space