Menu ▾ ▴

#3292 log: Introduce an initial clm node status

5.22.01
duplicate
Hieu Hong Hoang
None
defect
log
-
major
False
2022-01-23
2021-10-18
Hieu Hong Hoang
No

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.
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

Discussion

  • Hieu Hong Hoang

    Hieu Hong Hoang - 2021-11-25
    • summary: log: Introduce an initial node status callback --> log: Introduce an initial clm node status
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,9 +1,9 @@
-Currently, loga don't know when logd is ready for a request. In this ticket, we introduce a new callback from logd to loga. When logd detect a log agent is up, logd will send the initial node status to loga. Loga should wait for that message before sending any request to logd.
+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 node status message before sending the  initial client message, all messages will be processed in right order. Following is the order of processing 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 node status message
+2. loga: initial clm node status message
 3. logd: initial client message
 4. logd: final client message
 5. logd: agent down message
     

  • Hieu Hong Hoang

    Hieu Hong Hoang - 2021-12-08
    • status: assigned --> duplicate
     

  • Hieu Hong Hoang

    Hieu Hong Hoang - 2021-12-08

    The problem has been solved in ticket 3291 .

     

  • Gary Lee

    Gary Lee - 2022-01-23
    • Type: enhancement --> defect
     

Log in to post a comment.