- Description has changed:

Diff:

~~~~

--- old
+++ new
@@ -12,4 +12,15 @@
 2019-06-05 12:52:31.833 SC-2 osafamfd[254]: NO Receive message with event 
type:12, msg_type:31, from node:2030f, msg_id:0
 2019-06-05 12:52:31.834 SC-2 osafamfd[254]: NO Receive message with event 
type:13, msg_type:32, from node:2030f, msg_id:0
 
-
+~~~
+handle_event_in_failover_state() {
+..
+    while (!cb->evtqueue.empty()) {
+      AVDEVTQUEUE queueevt = cb->evtqueue.front();
+      cb->evtqueue.pop();
+      processevent(cb, queueevt->evt);
+      delete queueevt;
+    }
+..
+}
+~~~

~~~~




---

** [tickets:#3050] amfd: stuck in infinite loop if controller failover occurs 
during split network**

**Status:** review
**Milestone:** 5.19.06
**Created:** Wed Jun 05, 2019 03:45 AM UTC by Gary Lee
**Last Updated:** Thu Jun 06, 2019 12:33 AM UTC
**Owner:** Gary Lee


If SC absence is enabled, amfd can sometimes get stuck in an infinite loop 
processing compcsi and sisu sync messages, if a controller failover occurs 
during a split network event.

Steps to reproduce:
        1. Enable SC absence
        2. Put active SC [SC-1] and 1 payload in a network partition. Thus the 
cluster is split into 2 partitions:
           * Smaller partition: active SC [SC-1]+ 1 payloads
           * Bigger partition: standby SC [SC-2] + the remaining payloads
        3. Block active SC [SC-1] from consensus service causing it to 
self-fence
        4. Merge network
        5.  SC-2 will receive sync messages from a PL that will loop forever in 
AMFD causing a node failfast

2019-06-05 12:52:31.833 SC-2 osafamfd[254]: NO Receive message with event 
type:12, msg_type:31, from node:2030f, msg_id:0
2019-06-05 12:52:31.834 SC-2 osafamfd[254]: NO Receive message with event 
type:13, msg_type:32, from node:2030f, msg_id:0

~~~
handle_event_in_failover_state() {
..
    while (!cb->evtqueue.empty()) {
      AVDEVTQUEUE queueevt = cb->evtqueue.front();
      cb->evtqueue.pop();
      processevent(cb, queueevt->evt);
      delete queueevt;
    }
..
}
~~~



---

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