osaf/services/saf/clmsv/nodeagent/main.c |  5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)


The OpenSAF start time for standby system controllers had degraded between
OpenSAF 4.7 and OpenSAF 5.0. The reason was that the CLM node director did not
reply to NID until the standby node had joined the cluster, and therefore the
whole startup of the standby controller was delayed. This was not a problem in
OpenSAF 4.7 because the CLM node agent was started much later in the NID
sequence. The CLM node agent has now been changed so that it replies to NID
properly during startup, which solves this regression.

diff --git a/osaf/services/saf/clmsv/nodeagent/main.c 
b/osaf/services/saf/clmsv/nodeagent/main.c
--- a/osaf/services/saf/clmsv/nodeagent/main.c
+++ b/osaf/services/saf/clmsv/nodeagent/main.c
@@ -729,6 +729,11 @@ int main(int argc, char *argv[])
                ElectionStarterConstructor(clmna_cb->nid_started,
                                           clmna_cb->node_info.node_id);
 
+       if (clmna_cb->nid_started &&
+           nid_notify("CLMNA", rc, NULL) != NCSCC_RC_SUCCESS) {
+               LOG_ER("nid notify failed");
+       }
+
        fds[FD_TERM].fd = term_fd;
        fds[FD_TERM].events = POLLIN;
        fds[FD_AMF].fd = clmna_cb->nid_started ?

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel

Reply via email to