Table of Contents |
---|
The SCSP SEND method applies to both named and unnamed objects. The SEND request allows explicit transmission of a newly written object from a source cluster to a remote one, such as for keeping two clusters immediately synchronized. The feed SEND method works with any feed type as of Swarm 11.2, so it can force synchronous processing of a specific object on one or more of those feeds.
...
The SEND request needs query arguments for feedid, feedtype, or both, which is a union of all those provided arguments; SEND reverts to the legacy behavior if neither is provided.
Argument | Values, Examples | Notes |
---|---|---|
admin | none | SEND is used by an |
feedid | all | integer
| Specifies one or more specific feeds as the replication destination. Reference existing feed IDs ( Swarm returns a 400 Bad Request error if an integer value is not an existing feed. The SEND operation succeeds if the object being sent does not match the feed definition (because of a domain restriction), but no data is transferred. |
feedtype | all | search | replication | s3backup
| Specifies one or more types of feeds as the replication destination, from among these values: Swarm returns an HTTP 400 Bad Request error if the feedtype is not a valid value. The SEND operation succeeds if the object being sent does not match the feed definition (because of a domain restriction), but no data is transferred. |
timeout | true | number of seconds | false
| Sets how long to wait for replication to complete; if disabled ( Using timeout=true waits for the Swarm setting scsp.defaultFeedSendTimeout time in seconds, which defaults to 30. Specifying a positive number for the timeout overrides the value in the Swarm setting. |
force | yes | no | true | false | If the value is true or yes, Swarm forces re-processing of the object though any associated feeds for objects previously processed. |
...