For rolling upgrades only
commit 653edb5d9b217f1a3280b5aed8597fb53ffa5f61 (HEAD -> develop,
origin/develop, ticket-2521)
Author: Rafael Odzakow <rafael.odza...@ericsson.com>
Date: Wed Jul 19 11:52:57 2017 +0200
smf: no node locking when procedures are empty [#2521]
---
** [tickets:#2451] clm: Make the cluster reset admin op safe**
**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Wed May 03, 2017 10:51 AM UTC by Anders Widell
**Last Updated:** Sat Jul 01, 2017 04:15 PM UTC
**Owner:** nobody
The cluster reset admin operation that was implemented in ticket [#2053] is not
safe: if a node reboots very fast it can come up again and join the old cluster
before other nodes have rebooted. See mail discussion:
https://sourceforge.net/p/opensaf/mailman/message/35398725/
This can be solved by implementing a two-phase cluster reset or by introducing
a cluster generation number which is increased at each cluster reset (maybe
both ordered an spontaneous cluster resets). A node will not be allowed to join
the cluster with a different cluster genration without first rebooting.
---
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
