-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Minor - P4
-
None
-
Affects Version/s: 1.9.0
-
Component/s: Sharding
-
None
-
Sharding
-
ALL
If processes using the distributed lock take longer than a few minutes to complete, it is possible that the config servers could go unresponsive during the process, come back up, and be queried by other processes before the still-running process has a chance to ping again, leading to an incorrect forcing. Think the easiest way to avoid this is to re-acquire the distributed lock every 5-7 mins or so in long-running processes (1/2 the timeout time)?