Description
Per MB-35119's investigation, we found that TopologyChangeDetectorSvc could potentially take some time to start() as it requires target's topology to be retrieved before Start() returns.
(Also, there is a lack of logging for starting process for it which doesn't help debugging)
This MB is to track and see if we can improve the Start() process to avoid it causing timeouts if possible.
Attachments
Issue Links
- relates to
-
MB-35119 [System Test] XDCR "Execution timed out" errors in replication
- Closed