guyben e94ab94d13 Shorten the lock timeout for rdeStaging ... Sometimes rdeStaging reduce shards die after the lock is acquired. When that happens - the (automatic) rerun of the shard fails because the lock is in place causing that specific TLD to not stage and await the next call to rdeStaging. rdeStaging runs every 4 hours, but the current lock lives for 5 hours. This means that on the next rerun of rdeStaging, the lock still hasn't timed out so it fails again, and we have to wait for the subsequent run - a total delay of 8 hours. Shortening the lock timeout to be less than the 4 hours rdeStaging rerun time solves this issue. NOTE: This is just a "quick patch" solution. To really fix the rdeStaging failure we need to fix the lock itself. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=166102387		2017-08-29 16:59:18 -04:00
..
files	Allow admins to access registrar console without a RegistrarContact	2017-08-29 15:43:36 -04:00
BUILD	Move the environment configuration YAML files into the main JAR	2017-02-06 16:46:52 -05:00
ConfigUtils.java	Update copyright year on all license headers	2017-02-02 16:27:22 -05:00
package-info.java	Update copyright year on all license headers	2017-02-02 16:27:22 -05:00
RdapNoticeDescriptor.java	Update copyright year on all license headers	2017-02-02 16:27:22 -05:00
RegistryConfig.java	Shorten the lock timeout for rdeStaging	2017-08-29 16:59:18 -04:00
RegistryConfigSettings.java	Allow admins to access registrar console without a RegistrarContact	2017-08-29 15:43:36 -04:00
RegistryEnvironment.java	Update copyright year on all license headers	2017-02-02 16:27:22 -05:00
YamlUtils.java	Make YamlUtils work with arbitrary classes	2017-08-29 16:37:11 -04:00