larryruili a365b82d42 Update publish queue with practical retry params ... The unlimited exponential backoff makes cascading failure a serious problem, when encountering burst DNS load. Originally, it was exponential backoff, with min 1 sec max 1 hour. This changes it to be linearly scaling from 30 seconds to 10 minutes. Min 30 seconds is used to avoid over-retrying due to lock contention. Max 10 minutes allows for more retries within our 1 hour SLA. Finally, we're switching to linear scaling to increase the number of 'quick' retries for low backoff time, before ultimately settling on the upper bound of 10 minutes (if a task ever gets to that point, it's probably misconfigured.) ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=186041553		2018-02-20 16:00:33 -05:00
..
backend/WEB-INF	Add publish functionality to billing pipeline	2018-01-04 17:17:59 -05:00
default/WEB-INF	Update publish queue with practical retry params	2018-02-20 16:00:33 -05:00
META-INF	mv com/google/domain/registry google/registry	2016-05-13 18:55:08 -04:00
tools/WEB-INF	Move ResaveAllEppResources mapreduce from tools service to backend	2017-09-20 10:27:17 -04:00