- **status**: assigned --> duplicate
- **Comment**:
The problem has been solved in [ticket
3291](https://sourceforge.net/p/opensaf/tickets/3291/) .
---
** [tickets:#3292] log: Introduce an initial clm node status**
**Status:** duplicate
**Milestone:** 5.21.12
**Created:** Mon Oct 18, 2021 09:02 AM UTC by Hieu Hong Hoang
**Last Updated:** Thu Nov 25, 2021 08:40 AM UTC
**Owner:** Hieu Hong Hoang
Currently, loga don't know when logd is ready for a request. In this ticket, we
introduce a new message from logd to loga. When logd detect a log agent is up,
logd will send the initial clm node status to loga. Loga should wait for that
message before sending any request to logd.
This callback could solve the issue with priority of messages in
[1396](https://sourceforge.net/p/opensaf/tickets/1396/).
In 1396: the agent down message received before the initial client message but
it's processed after the initial client message due to the priority of messages.
If the loga wait for the initial clm node status message before sending the
initial client message, all messages will be processed in right order.
Following is the order of processing messages:
1. logd: agent up message
2. loga: initial clm node status message
3. logd: initial client message
4. logd: final client message
5. logd: agent down message
---
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
