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

- Attachments has changed: Diff: --- old +++ new @@ -1 +0,0 @@ -syslog.7z (93.4 kB; application/octet-stream) --- ** [tickets:#1955] imm: Fail to detect veteran node when NCSMDS_UP event comes late** **Status:** fixed **Milestone:** 5.0.1 **Created:** Wed Aug 17, 2016 10:44 AM

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

- **status**: review --> fixed - **Comment**: default (5.2) [staging:e8d47b] changeset: 7996:e8d47b7395b3 user:Hung Nguyen date:Sun Aug 28 12:36:37 2016 +0700 summary: imm: Create missing IMMND node when processing intro messages [#1955]

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

- **status**: accepted --> review --- ** [tickets:#1955] imm: Fail to detect veteran node when NCSMDS_UP event comes late** **Status:** review **Milestone:** 5.0.1 **Created:** Wed Aug 17, 2016 10:44 AM UTC by Hung Nguyen **Last Updated:** Wed Aug 24, 2016 10:51 AM UTC **Owner:** Hung Nguyen

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

TIPC delivers topology events and data messages asynchronously through two separate channels, so you can't assume any specific ordering between topology events (e.g. service UP), and data messages. --- ** [tickets:#1955] imm: Fail to detect veteran node when NCSMDS_UP event comes late**

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

The service event is PRIORITY_VERY_HIGH and the intro message is PRIORITY_HIGH. So service event should always be processed before the intro message. I think the problem comes from MDS (or TIPC), not from the way IMMD puts messages to the mailbox. --- ** [tickets:#1955] imm: Fail to detect

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

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(_cb->veteran_sync_lock,NCS_LOCK_WRITE);

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

After head less , if SC is starting , I can see some code in IMMD Waiting 3 seconds to allow IMMND MDS attachments to get processed. if (cb->mScAbsenceAllowed && cb->ha_state == SA_AMF_HA_ACTIVE) { /* If this

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

-I s in your case issue observed headless case ? >>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

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

System 10 nodes (with HEADLESS feature) with TIPC version is 2.0 - Power off PL-10, PL-9, PL-8 - Power off PL-7, PL-6 - Power off SC-1 - Power off PL-5, PL-4 - Power off SC-2 - After a few minutes, power on SC-1 Issue happens. --- ** [tickets:#1955] imm: Fail to detect veteran node when

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

--- ** [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 17, 2016 10:44 AM UTC **Owner:** Hung Nguyen **Attachments:** -