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.
---
** [tickets:#3310] log: log agent is blocked for 10s**
**Status:** accepted
**Milestone:** 5.22.04
**Created:** Tue Mar 08, 2022 03:32 AM UTC by Hieu Hong Hoang
**Last Updated:** Thu Mar 17, 2022 08:08 AM UTC
**Owner:** Hieu Hong Hoang
In [ticket 3291](https://sourceforge.net/p/opensaf/tickets/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
~~~
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
