...
For bucket requests, use a separate initialization or setup routine that runs less frequently. Swarm is optimized for calls on individual objects, not domains or buckets (which are centralized resources), so do not make bucket calls on the high-availability code path of your a client application.
Reuse object names. After a named object is deleted, another object with the same name can be created in the same bucket. Unlike unnamed objects, whose UUIDs are not reused, names can be reused.
Pause before recreating. Deleting a named object involves an underlying update, for Swarm to write a special marker value to the name. When recreating a named object after deleting it, wait at least one second.
DELETE for domains and buckets
When you delete Delete any objects contained within a domain or bucket , you need to also delete any objects contained within it, when deleting them or else these objects are orphaned, lost, and consume disk space unnecessarily. These deletes are recursive, iterating until every object contained in the domain or bucket is dealt with.
...
recursive | recursive=true|yes
Grants a 1-week grace period (default) during which you can restore the domain or bucket can be restored before the health processor begins reclaiming the space.
To Edit the health.recursiveDeleteDelay parameter to change the length of the grace period, edit the health.recursiveDeleteDelay parameter.
recursive=now
Grants no grace period. The health processor begins reclaiming the space immediately.
If you have Avoid changing the recursive argument if existing integrations that do not use the recursive argument, you can avoid changing them by adding argument. Add a global configuration parameter: scsp.autoRecursiveDelete=True.
If you An erroneously deleted a domain or bucket , you can get it back can be restored without data loss if it is within the grace period. See Restoring Domains and Buckets.
Reusing bucket names
You can delete a bucket and recreate A bucket can be deleted and another bucket with the same name . However, be can be recreated. Be aware of the following:
The new bucket is a different bucket that happens to have the same name.
After you delete a bucket, all All objects in that a bucket are inaccessible after deleting it, even if you subsequently create another bucket with the same name is subsequently created.
| Info |
|---|
Best practiceWait at least twice the value of cache.realmStaleTimeout before attempting to recreate a bucket with the same name as a bucket deleted: the default is 600 seconds (10 minutes), so wait 20 minutes, then create the new bucket. This waiting period applies to reusing names of buckets: deleting a named object and recreating an object with that name requires only a 1-second pause. |
DELETE for unnamed objects
...
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
If the method succeeds, the The content associated with the name or UUID supplied in the request is no longer available if the method succeeds. This does not imply that all copies of the content were erased. The cluster now responds to any READ request for that UUID with a 404 Not Found error.
...
Application deleting an object - All online replicas in a single cluster are removed immediately after a delete method is executed on an object. (An online replica is one that resides on a cluster node that is on line online at the time the delete is issued.) In addition, the cluster remembers the name or UUID has been deleted for 14 days, in the event that one or more nodes holding replicas of the deleted object are off line at the time the delete was issued.
Policy deleting an object - An object can have a storage policy defined by the application and stored along with it. Part of the storage policy may be an expiration period, beyond which the object is to be removed. In the case of a policy-defined deletion, all replicas, wherever they are stored, are deleted at approximately the same time and become unavailable at most one second after the expiration date and time.
...