- **status**: fixed --> review
- **Comment**:
Re-open this ticket since the new active IMMD (switches from STANDBY role) has
problem with dead IMMND in the immnd_tree. The dead IMMND should be cleanup
before switching to ACTIVE.
---
** [tickets:#2418] imm: Info of dead IMMND remains in standby IMMD**
**Status:** review
**Milestone:** 5.17.06
**Created:** Mon Apr 10, 2017 10:23 AM UTC by Hung Nguyen
**Last Updated:** Tue Apr 25, 2017 06:45 AM UTC
**Owner:** Hung Nguyen
**Attachments:**
- [log.tgz](https://sourceforge.net/p/opensaf/tickets/2418/attachment/log.tgz)
(149.4 kB; application/x-compressed)
When Standby IMMD is up at the same time with a IMMND exiting, the info of that
IMMND might not be removed from **immnd_tree** of the Standby IMMD.
Details of the problem is explained in the sequence diagram below
[sequence
diagram](http://sequencediagram.org/index.html?initialData=A4QwTgLglgxloDsIAICCBhAKgWgJIFl8ARAKFElnhCWQGVMAhPQ0kkAIwHsAPZTgNwCmYOo2bFkAYjCCAJgC5kRAPIB1AHLJBQmgDMwnALbIC+dUT4JkCTrMHIAGiRJdeA4aKamii3AigoxLQAOgh+Acj4DOjI1LLIAM6CgdHIBgA29hCcdBBx7ACezvReLMjYAHxoWOIW8uic6bIJBQgwaYIAjgCuggkQziQYON7lVSW1ig1NLW0dCcCcCEmhEAAW9qbmyOlQ-chQbenddgnI65uE20vWtvZOzhw8fEIiw7VSMgpKapragnoDMYthYbjY7I5nK4Xh53t4ADQTbyKTAbExXCx7DqGdzxfRGaojMrsbooGSGECHM6HTy1IA)
SC-5 was Active, SC-2 was Standby, IMMND on SC-1 was exiting
~~~
18:35:03 SC-1 osafimmnd[441]: exiting for shutdown
18:35:03 SC-2 osafrded[413]: NO RDE role set to STANDBY
18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3,
dest:568511936070075)
18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3,
dest:567412424442298)
18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3,
dest:566312912814523)
18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3,
dest:565213401186744)
18:35:03 SC-5 osafimmd[433]: NO MDS event from svc_id 25 (change:4,
dest:564113889558969)
~~~
Down event for IMMND@SC-1 was received on SC-5 but not on SC-2.
</br>
**The symptoms:**
1. If the down IMMND is the corrdinator, that results in when that Standby IMMD
becomes Active, it fails to elect new coordinator as there's already a
coordinator in the **immnd_tree**.
~~~
18:35:11 SC-2 osafimmd[430]: WA IMMND coordinator at 2050f apparently crashed
=> electing new coord
~~~
No more logs about newly elected coordinator were printed out.
</br>
2. When IMMND@SC-1 is up again, it will fail to introduce to IMMD because the
IMMD already have IMMND@SC-1 in **immnd_tree** with a wrong epoch.
~~~
18:35:29 SC-1 osafimmnd[441]: NO SERVER STATE: IMM_SERVER_ANONYMOUS -->
IMM_SERVER_CLUSTER_WAITING
18:35:29 SC-1 osafimmnd[441]: NO This IMMND is now the NEW Coord
18:35:29 SC-1 osafimmnd[441]: ER 3 > 0, exiting
~~~
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
