Comment 1 for bug 1786154

Hi Mahesh, looks like assumption the code in ConfigClientManager::InitConfigClient() is not fully correct. While it is correct that none of the other tasks mentioned cannot be running at the same, time, there is no logic there to infer that there is no task has already triggered to run especially the config_reader_ task, when reinit of the db is triggered I guess due to signal USR1.

We have to add logic to check if config_reader_ task_trigger is triggered and if so, pause. Later, when ever config_reader_ task trigger is complete, we have to wakeup reinit again.