- Description has changed:
Diff:
~~~~
--- old
+++ new
@@ -6,7 +6,7 @@
Observed behaviour:
Since components are taking time in stopping all components during 'opensad
stop' of SC-2, Amfnd hasn't exited. But, all middleware components assignments
are stopped. Only Amfnd and Amfd is alive with few more components to stop.
But SC-1 has come up till Amfd and since two Amfd is Act now, so SC-2 Amfd
exits by saying "Duplicate ACTIVE detected, exiting".
-Till this time, services states including Amfd is in bad state as they
couldn't differentiate whether it is headless state or cluster comming up. This
is true also as the system is in half middle of headless and cluster coming up.
+Till this time, services states including Amfd is in bad state as they
couldn't differentiate whether it is headless state or failover. This is true
also as the system is in half middle of headless and failover.
Expected behaviour
~~~~
---
** [tickets:#2151] osaf: system in not in correct state during Act controller
comming up**
**Status:** unassigned
**Milestone:** 5.2.FC
**Created:** Mon Oct 31, 2016 10:54 AM UTC by Nagendra Kumar
**Last Updated:** Mon Oct 31, 2016 10:54 AM UTC
**Owner:** nobody
Steps to reproduce:
1. Start two controllers(SC-1 Act, SC-2 Standby) and two paylods. Configure 50
components on SC-2 and unlock them. Keep 1 sec delay in each component stop
script.
2. Stop SC-1 and after that, stop SC-2.
3. During SC-2 is going down, start SC-1.
Observed behaviour:
Since components are taking time in stopping all components during 'opensad
stop' of SC-2, Amfnd hasn't exited. But, all middleware components assignments
are stopped. Only Amfnd and Amfd is alive with few more components to stop.
But SC-1 has come up till Amfd and since two Amfd is Act now, so SC-2 Amfd
exits by saying "Duplicate ACTIVE detected, exiting".
Till this time, services states including Amfd is in bad state as they couldn't
differentiate whether it is headless state or failover. This is true also as
the system is in half middle of headless and failover.
Expected behaviour
In my view:
FMS should stop and shouldn't proceed if peer is going down. i.e. FMS should
figure out on SC-1 that the peer system is going down. And should allow SC-1
only if all services are down i.e. it gets node down (may be cb->immd_down &&
cb->immnd_down && cb->amfnd_down && cb->amfd_down && cb->fm_down).
---
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.
------------------------------------------------------------------------------
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive.
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
