This is a (known ?) problem of clma or nid.
I also always observe that problem on standby SC.
On active SC, IMMND is started right away.
~~~
May 23 15:32:48 CONTROLLER-1 opensafd: Starting OpenSAF Services(5.0.0 - )
(Using TIPC)
May 23 15:32:48 CONTROLLER-1 osafclmna[27809]: Started
May 23 15:32:49 CONTROLLER-1 osafclmna[27809]: NO Starting to promote this node
to a system controller
May 23 15:32:49 CONTROLLER-1 osafimmnd[27848]: Started
~~~
On standby SC, there's a delay before starting IMMND.
~~~
May 23 15:32:49 CONTROLLER-2 opensafd: Starting OpenSAF Services(5.0.0 - )
(Using TIPC)
May 23 15:32:49 CONTROLLER-2 osafclmna[8636]: Started
... (~1 min)
May 23 15:33:40 CONTROLLER-2 osafclmna[8636]: NO
safNode=SC-2,safCluster=myClmCluster Joined cluster, nodeid=2020f
May 23 15:33:40 CONTROLLER-2 osafimmnd[8687]: Started
~~~
Because of that delay, IMMND on standby SC always misses becoming
loading-client and it has to wait for the next sync.
Compared with older versions of OpenSAF, it's slower to start all nodes
simultaneously.
---
** [tickets:#1845] IMM: Standby syncing is delayed untill payloads join the
cluster**
**Status:** unassigned
**Milestone:** 5.0.1
**Created:** Mon May 23, 2016 10:46 AM UTC by Srikanth R
**Last Updated:** Mon May 23, 2016 10:46 AM UTC
**Owner:** nobody
**Attachments:**
-
[1845.tgz](https://sourceforge.net/p/opensaf/tickets/1845/attachment/1845.tgz)
(10.6 MB; application/x-compressed-tar)
Changeset : 7640
Setup : 4 nodes cluster with PBE of 50k objects.SUSE 11.2 VM
Issue : Standby syncing is delayed with active controller, untill payloads join
the cluster.
Steps :
1. PBE is enabled on the setup and 50k DB is created earlier.
2. Started opensaf on all the nodes simultaneously.
May 23 15:32:49 CONTROLLER-1 osafrded[27818]: NO Requesting ACTIVE role
May 23 15:32:49 CONTROLLER-1 osafrded[27818]: NO RDE role set to Undefined
May 23 15:32:49 CONTROLLER-1 kernel: [10654.360773] TIPC: Established link
<1.1.1:eth0-1.1.2:eth3> on network plane A
May 23 15:32:49 CONTROLLER-1 kernel: [10654.881929] TIPC: Established link
<1.1.1:eth0-1.1.3:eth3> on network plane A
May 23 15:32:50 CONTROLLER-1 kernel: [10655.434543] TIPC: Established link
<1.1.1:eth0-1.1.4:eth3> on network plane A
May 23 15:32:51 CONTROLLER-1 osafimmd[27837]: NO Attached Nodes:3 Accepted
nodes:0 KnownVeteran:0 doReply:1
3. Opensafd on SC-1 started at May 23 15:33:41.
4. Opensafd on PL-3 and PL-4 started at 15:33:42.
5. On SC-2, imm syncing started at 15:33:47 after the active controller and
payloads joined.
May 23 15:33:47 CONTROLLER-1 osafimmd[27837]: NO Successfully announced sync.
New ruling epoch:9
May 23 15:33:47 CONTROLLER-1 osafimmloadd: NO Sync starting
6. At 15:33:57, SC-2 joined the cluster successfully.
Because of this, time taken for standby to join during simultaneous startup
of all nodes have increased by sync time.
Value for IMMSV_NUM_NODES is default (5) and not changed.
---
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.------------------------------------------------------------------------------
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-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
