if (cb->mScAbsenceAllowed &&
                        pEvt->info.immd.type == IMMD_EVT_ND2D_INTRO &&
                        pEvt->info.immd.info.ctrl_msg.refresh == 2) {

                prio = NCS_IPC_PRIORITY_HIGH;

                m_NCS_LOCK(&immd_cb->veteran_sync_lock,NCS_LOCK_WRITE);
                if (cb->veteran_sync_sel.raise_obj != -1) { /* Check if the 
sel_obj is not destroyed */
                        m_NCS_SEL_OBJ_IND(&cb->veteran_sync_sel);
                }
                m_NCS_UNLOCK(&immd_cb->veteran_sync_lock,NCS_LOCK_WRITE);
        }


When the payload IMMND, sent intro message, the priority of this message is 
increased to NCS_IPC_PRIORITY_HIGH. The service event that should have been 
arrived before is also waiting in the mailbox with NCS_IPC_PRIORITY_VERY_HIGH. 
Since, both the INTRO message and service event are now of high priority, there 
is a chance that message is processed before service event.


---

** [tickets:#1955] imm: Fail to detect veteran node when NCSMDS_UP event comes 
late**

**Status:** accepted
**Milestone:** 5.0.1
**Created:** Wed Aug 17, 2016 10:44 AM UTC by Hung Nguyen
**Last Updated:** Wed Aug 24, 2016 07:01 AM UTC
**Owner:** Hung Nguyen
**Attachments:**

- 
[syslog.7z](https://sourceforge.net/p/opensaf/tickets/1955/attachment/syslog.7z)
 (93.4 kB; application/octet-stream)


Sometimes, the NCSMDS_UP event comes after the messages.
In this case, IMMD received the IMMD_EVT_ND2D_INTRO message before the 
NCSMDS_UP event.
IMMD failed to process the intro message because the node info had not been 
added to cb->immnd_tree.
~~~
Aug 12 08:13:53 SC-1 osafimmd[11184]: WA Node not found 566314186398634
Aug 12 08:13:53 SC-1 osafimmd[11184]: WA Error returned from processing message 
err:2 msg-type:2
Aug 12 08:13:53 SC-1 osafimmnd[11199]: NO SERVER STATE: IMM_SERVER_ANONYMOUS 
--> IMM_SERVER_CLUSTER_WAITING
Aug 12 08:13:53 SC-1 osafimmd[11184]: NO New IMMND process is on ACTIVE 
Controller at 2010f
Aug 12 08:13:53 SC-1 osafimmd[11184]: NO Extended intro from node 2010f
Aug 12 08:13:53 SC-1 osafimmd[11184]: NO First SC IMMND (OpenSAF 4.4 or later) 
attached 2010f
Aug 12 08:13:53 SC-1 osafimmd[11184]: NO Attached Nodes:2 Accepted nodes:1 
KnownVeteran:0 doReply:1
Aug 12 08:13:53 SC-1 osafimmd[11184]: NO First IMMND on SC found at 2010f this 
IMMD at 2010f. Cluster is loading, *not* 2PBE => designating that IMMND as 
coordinator
Aug 12 08:13:53 SC-1 osafimmnd[11199]: NO This IMMND is now the NEW Coord
~~~
IMMND on SC-1 was elected as coordinator insted of the veteran.


The MDS messages come from 'Dsock' socket and MDS events come from 'BSRsock'.
Since MDS uses two different sockets so I think we can't fix this problem in 
MDS.
IMM has to somehow handle this case.




---

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

Reply via email to