Open topic with navigation

# BackoffSeconds

The maximum number of seconds that HPE Content Component waits between attempts to obtain a lock. This parameter has an effect only when you are using Redis lock servers.

The exact amount of time that the server waits is random (but lower than this value), to prevent multiple servers attempting to get locks at the same time.

You can use MaxRetry to control the number of times HPE Content Component attempts to obtain the lock.

NOTE:

If you use a FlushLockFile, HPE Content Component reattempts to obtain the lock every second, and `BackoffSeconds` has no effect.

Type: | Long
Default: | 30
Allowed Range: | Minimum: 1
Required: | No
Configuration Section: | FlushLock
Example: | `BackoffSeconds=15`
See Also: | MaxRetry

© 2017 Hewlett Packard Enterprise Development LP | Send documentation feedback to HPE Close Send documentation feedback To open the configured email client on this computer, open an email window. Otherwise, copy the information below to a web mail client, and send this email to AutonomyTPFeedback@hpe.com. We appreciate your feedback! Product: Topic Title: Help Topic: Feedback:

_HP_HTML5_bannerTitle.htm