- **status**: review --> fixed
- **Comment**:
commit d2bbaba8c28f68f5cb1a5e620022d673cc03600e
Author: thuan.tran <[email protected]>
Date: Wed Sep 16 14:18:33 2020 +0700
imm: fix immnd crash in multi partitioned clusters rejoin [#3219]
Before IMMND get re-intro response from IMMD, it may get broadcast
event from IMMD (e.g: IMMND_EVT_D2ND_PBE_PRTO_PURGE_MUTATIONS) then
crash because it used to be on different partition. As IMMND crash
then it cannot reboot node as expected. Solution:
- IMMND prioritize re-introduce response msg from IMMD.
- IMMND ignore broadcast events from IMMD if re-introduce on-going.
---
** [tickets:#3219] imm: immnd crash in multi partitioned clusters rejoin**
**Status:** fixed
**Milestone:** 5.20.11
**Created:** Wed Sep 16, 2020 11:43 AM UTC by Thuan Tran
**Last Updated:** Wed Sep 16, 2020 01:51 PM UTC
**Owner:** Thuan Tran
Under scenario multi partitioned cluster rejoin, IMMND crash as following:
~~~
2020-09-15 18:39:59.310 SC-6 osafimmnd[195]: NO Re-introduce-me
highestProcessed:4358 highestReceived:4358 ex_immd_node_id=2070f
2020-09-15 18:39:59.310 SC-6 osafimmnd[195]: src/imm/immnd/immnd_evt.c:10158:
immnd_evt_proc_pbe_prto_purge_mutations: Assertion 'cb->mRulingEpoch <=
evt->info.ctrl.rulingEpoch' failed.
~~~
Then node don't reboot as expected even it used to on different partition with
current coordinator.
---
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
