In ticket 3291, a new message was introduced which is sent from the log director to the log agent. When a log agent that contains #3291 run with a log director that doesn't contains #3291, that log agent must wait for 10s. We should avoid this.
<143>1 2022-02-19T14:06:22.358273+01:00 SC-2 osafamfd 27233 osafamfd [meta sequenceId="749743"] 27233:log/agent/lga_agent.cc:409 >> saLogInitialize
...
<143>1 2022-02-19T14:06:32.359774+01:00 SC-2 osafamfd 27233 osafamfd [meta sequenceId="749784"] 27233:log/agent/lga_agent.cc:348 TR Waiting for initial clm status timeout
<143>1 2022-02-19T14:06:32.359838+01:00 SC-2 osafamfd 27233 osafamfd [meta sequenceId="749785"] 27233:log/agent/lga_agent.cc:361 << WaitLogServerUp
commit b99fd24c88e4f08799bfcfa9eaa2d585ba426593 (HEAD -> develop, origin/develop, ticket-3310)
Author: hieu.h.hoang hieu.h.hoang@dektech.com.au
Date: Tue Mar 8 10:33:18 2022 +0700
In previous commit, the log agent 5.22.01 is still blocked for 10s if it runs with new log director. The log agent 5.22.01 will wait for the initial message but its subpart version is 1. Therefore the log director doesn't know that it needs to send the initial message.
A different approach is the log director always send the initial message no matter what version of log agent is.
commit 78cbf3c763439e24d3db459fe5a0d6e5974c693e (HEAD -> develop, origin/develop, ticket-3310)
Author: hieu.h.hoang hieu.h.hoang@dektech.com.au
Date: Thu Mar 17 15:27:01 2022 +0700