---
** [tickets:#1179] LOG: Log service shall be able to recover if both SC nodes
goes down**
**Status:** unassigned
**Milestone:** 4.6.FC
**Created:** Mon Oct 20, 2014 01:25 PM UTC by elunlen
**Last Updated:** Mon Oct 20, 2014 01:25 PM UTC
**Owner:** elunlen
The log service shall be able to
- Description has changed:
Diff:
--- old
+++ new
@@ -1,3 +1,3 @@
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.
+NOTE: This is also applica
- Description has changed:
Diff:
--- old
+++ new
@@ -1,3 +1,3 @@
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.
+NOTE: This is also applica
- **status**: unassigned --> accepted
---
** [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 Oct 20, 2014 01:42 PM UTC
**Owner:** elunl
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
Correct "INVALID HANDLE" is not returned. SA_AIS_ERR_BAD_HANDLE is returned
---
** [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 1
- **Milestone**: 4.6.FC --> future
---
** [tickets:#1179] LOG: Log service shall be able to recover if both SC nodes
goes down**
**Status:** accepted
**Milestone:** future
**Created:** Mon Oct 20, 2014 01:25 PM UTC by elunlen
**Last Updated:** Mon Nov 17, 2014 03:39 PM UTC
**Owner:** elunlen
- **Milestone**: future --> 5.0.FC
---
** [tickets:#1179] LOG: Log service shall be able to recover if both SC nodes
goes down**
**Status:** accepted
**Milestone:** 5.0.FC
**Created:** Mon Oct 20, 2014 01:25 PM UTC by elunlen
**Last Updated:** Mon Mar 16, 2015 06:37 AM UTC
**Owner:** elunlen
- **Comment**:
One major criteria for this feature is that it must be configurable. i.e. The
user should be able to turn on/off the feature.
---
** [tickets:#1179] LOG: Log service shall be able to recover if both SC nodes
goes down**
**Status:** accepted
**Milestone:** 5.0.FC
**Created:**
ets] #1179 LOG: Log service shall be able to
recover if both SC nodes goes down
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
an
ensaf-tickets@lists.sourceforge.net>
Subject: [tickets] [opensaf:tickets] #1179 LOG: Log service shall be able to
recover if both SC nodes goes down
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
11 matches
Mail list logo
