I now have two patches for handling this situation.
The idea is that the agent detects when the server goes down (both active and
standby). When this happen the agent will invalidate all handles to all clients
and free all resources.
The clients will now get "INVALID HANDLE" as a reply in all API-s except
Initialize. If a client tries to Initialize and the server is still down "TRY
AGAIN" will be returned. This is all handled in the agent.
On the server there is the possibility that IMM runtime objects will be left as
"stray" objects if both nodes goes down in an uncontrolled way. Therefore I
have added a function that during start/init active server search for "stray"
objects and delete them. Attached are two patches one for the agent and one for
the server.
Please look at them and comment
Attachment: lgs_1179_enh.zip (7.3 kB; application/zip)
---
** [tickets:#1179] LOG: Log service shall be able to recover if both SC nodes
goes down**
**Status:** accepted
**Milestone:** 4.6.FC
**Created:** Mon Oct 20, 2014 01:25 PM UTC by elunlen
**Last Updated:** Mon Nov 10, 2014 11:23 AM UTC
**Owner:** elunlen
The log service shall be able to recover if both SC nodes goes down at the same
time. This is not possible today. A cluster restart is needed.
NOTE: This is also applicable for the NTF service. [#1180]
---
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
