- Description has changed:
Diff:
~~~~
--- old
+++ new
@@ -1,3 +1,4 @@
-As mentioned in the ticket [#2934], after split-recovery, it is expected to
have IMMND restarted due to its epoch is different with one in the other
partition.
+As mentioned in the ticket [#2934], it is possible to have epoch counters
mismatched
+b/w one on IMMND veteran(s) located at this partition and one from active IMMD
on another partition after split-brain recovery.
With that, instead of generating coredump in such case, we should syslog error
message and have IMMND self-terminated.
~~~~
---
** [tickets:#2942] imm: coredump is generated after split-brain recovery **
**Status:** review
**Milestone:** 5.18.12
**Created:** Fri Oct 19, 2018 07:32 AM UTC by Vu Minh Nguyen
**Last Updated:** Fri Oct 19, 2018 08:21 AM UTC
**Owner:** Vu Minh Nguyen
As mentioned in the ticket [#2934], it is possible to have epoch counters
mismatched
b/w one on IMMND veteran(s) located at this partition and one from active IMMD
on another partition after split-brain recovery.
With that, instead of generating coredump in such case, we should syslog error
message and have IMMND self-terminated.
---
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.
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
