Open topic with navigation

# MaxRetry

The maximum number of times that HPE Content Component attempts to obtain a lock. After this number of attempts, HPE Content Component logs a message and flushes to disk without a lock.

Note: If you use a FlushLockFile, HPE Content Component reattempts to obtain the lock every second. If you use Redis lock servers, the interval between retries varies, and you might want to change the value of `MaxRetry` to avoid waiting for too long to obtain a lock.

Type: | String
Default: | 200
Required: | No
Configuration Section: | FlushLock
Example: | `MaxRetry=50`
See Also: | BackoffSeconds

© 2016 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