Start of Jira datacenter replication thread NodeReindexServiceThread is not synchronised with Jira start localhost-startStop thread

Summary

There could be race condition between Jira DC index replication thread NodeReindexServiceThread:thread-1 and Jira localhost-startStop-1 thread during the start-up.
Start of the NodeReindexServiceThread:thread-1 is not synchronized with start-up thread, it just has 10sec delay. In some conditions, this time will be not enough and this could lead to the contention of the resources and possible start-up failure (see for example JRASERVER-67613) or slow start-up.

Environment

• Jira DC

Steps to Reproduce

1. Start Jira node
2. Create condition when Jira starts takes a long time, see for example JRASERVER-67614
3. Start taking frequent thread dumps with 2s intervals, we see both 2 thread RUNNABLE:

   "NodeReindexServiceThread:thread-1" #172 prio=5 os_prio=0 tid=0x00007f3696f9a800 nid=0x43de runnable [0x00007f34d19ea000]
      java.lang.Thread.State: RUNNABLE
   
   "localhost-startStop-1" #29 daemon prio=5 os_prio=0 tid=0x00007f36a0001800 nid=0x4227 runnable [0x00007f3701afe000]
      java.lang.Thread.State: RUNNABLE
   

Expected Results

Thread NodeReindexServiceThread:thread-1 will finish for the initialization of the Jira start.

Notes

None

Workaround

None