guyben f22a42cd42 Lengthen the publishDnsUpdates maximum lock duration ... Having a short maximum lock duration doesn't affect the lock performance - since the lock is only in use while the command is running anyway (which doesn't depend on the maximum lock duration). It only affects the behavior if the command running time is longer than the maximum lock duration. If that happens - the command will fail, retry, and fail again forever. This may be a left-over from the old code, where the publishDnsUpdates itself read the domains from the pull queue and published them - which would mean that killing the command doesn't undo the work done. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=182255446		2018-01-19 14:54:54 -05:00
..
com/google/testing/builddefs	Update copyright year on all license headers	2017-02-02 16:27:22 -05:00
google/registry	Lengthen the publishDnsUpdates maximum lock duration	2018-01-19 14:54:54 -05:00