---
** [tickets:#621] Cluster startup timer does not stop when the cluster is up
but the SUs are in locked instantiation state**
**Status:** unassigned
**Created:** Tue Nov 12, 2013 09:39 AM UTC by Sirisha Alla
**Last Updated:** Tue Nov 12, 2013 09:39 AM UTC
**Owner:** nobody
The issue is seen on change set 4585 on SLES 4nodes.
The cluster is configured to have 2 nodes SC-1 and SC-2:
Application is configured in 2N redundancy model with a spare SU. The cluster
startup timer is configured to be 60 seconds. SU1 is hosted on SC-1 and SU2 and
SU3 on SC-2. SU1 is in unlocked admin state while SU2 and SU3 are in
locked-instantiation state.
SC-1 and SC-2 are brought up. The cluster has come up. But there are no
assignments to SU1 till the cluster startup timer expiry. Following is the
syslog on SC-1:
Nov 12 14:51:49 SLES-64BIT-SLOT1 osafamfnd[2041]: NO Assigned
'safSi=SC-2N,safApp=OpenSAF' ACTIVE to 'safSu=SC-1,safSg=2N,safApp=OpenSAF'
Nov 12 14:51:49 SLES-64BIT-SLOT1 opensafd: OpenSAF(4.4.M0) services
successfully started
Nov 12 14:51:49 SLES-64BIT-SLOT1 osafamfnd[2041]: NO
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo' Presence State UNINSTANTIATED =>
INSTANTIATING
some thing is spawnd instantiate for
safComp=AmfDemo1,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo
some thing is spawnd instantiate for
safComp=AmfDemo2,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo
Nov 12 14:51:49 SLES-64BIT-SLOT1 osafamfnd[2041]: NO
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo' Presence State INSTANTIATING =>
INSTANTIATED
Nov 12 14:51:54 SLES-64BIT-SLOT1 kernel: [96492.575243] TIPC: Established link
<1.1.1:eth0-1.1.2:eth1> on network plane A
Nov 12 14:51:54 SLES-64BIT-SLOT1 osafimmd[1963]: NO New IMMND process is on
STANDBY Controller at 2020f
Nov 12 14:51:54 SLES-64BIT-SLOT1 osafimmd[1963]: WA IMMND on controller (not
currently coord) requests sync
Nov 12 14:51:54 SLES-64BIT-SLOT1 osafimmd[1963]: NO Node 2020f request sync
sync-pid:17853 epoch:0
Nov 12 14:51:55 SLES-64BIT-SLOT1 osafimmnd[1973]: NO Announce sync, epoch:3
Nov 12 14:51:55 SLES-64BIT-SLOT1 osafimmnd[1973]: NO SERVER STATE:
IMM_SERVER_READY --> IMM_SERVER_SYNC_SERVER
Nov 12 14:51:55 SLES-64BIT-SLOT1 osafimmnd[1973]: NO NODE STATE->
IMM_NODE_R_AVAILABLE
Nov 12 14:51:55 SLES-64BIT-SLOT1 osafimmd[1963]: NO Successfully announced
sync. New ruling epoch:3
Nov 12 14:51:55 SLES-64BIT-SLOT1 osafimmloadd: NO Sync starting
Nov 12 14:51:56 SLES-64BIT-SLOT1 osafimmloadd: IN Synced 341 objects in total
Nov 12 14:51:56 SLES-64BIT-SLOT1 osafimmnd[1973]: NO NODE STATE->
IMM_NODE_FULLY_AVAILABLE 13809
Nov 12 14:51:56 SLES-64BIT-SLOT1 osafimmloadd: NO Sync ending normally
Nov 12 14:51:56 SLES-64BIT-SLOT1 osafimmnd[1973]: NO Epoch set to 3 in ImmModel
Nov 12 14:51:56 SLES-64BIT-SLOT1 osafimmd[1963]: NO ACT: New Epoch for IMMND
process at node 2010f old epoch: 2 new epoch:3
Nov 12 14:51:56 SLES-64BIT-SLOT1 osafimmd[1963]: NO ACT: New Epoch for IMMND
process at node 2020f old epoch: 0 new epoch:3
Nov 12 14:51:56 SLES-64BIT-SLOT1 osafimmnd[1973]: NO Implementer (applier)
connected: 11 (@safLogService) <0, 2020f>
Nov 12 14:51:56 SLES-64BIT-SLOT1 osafimmnd[1973]: NO SERVER STATE:
IMM_SERVER_SYNC_SERVER --> IMM SERVER READY
Nov 12 14:51:56 SLES-64BIT-SLOT1 osafimmnd[1973]: NO Implementer (applier)
connected: 12 (@safAmfService2020f) <0, 2020f>
Nov 12 14:51:56 SLES-64BIT-SLOT1 osafamfd[2031]: NO Node 'SC-2' joined the
cluster
Nov 12 14:51:57 SLES-64BIT-SLOT1 osafimmnd[1973]: NO Implementer (applier)
connected: 13 (@OpenSafImmReplicatorB) <0, 2020f>
Nov 12 14:51:57 SLES-64BIT-SLOT1 osafimmnd[1973]: NO Implementer connected: 14
(MsgQueueService131599) <0, 2020f>
Nov 12 14:52:49 SLES-64BIT-SLOT1 osafamfnd[2041]: NO Assigning
'safSi=AmfDemo,safApp=AmfDemo' ACTIVE to
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo'
Nov 12 14:52:49 SLES-64BIT-SLOT1 osafamfnd[2041]: NO Assigned
'safSi=AmfDemo,safApp=AmfDemo' ACTIVE to
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo'
The same configuration with single node cluster(SU1 in unlocked and SU2 and SU3
in locked-instantiation) works (the timer is stopped and the assignments are
given as soon as SC-1 is up). But if all the SUs in the single node cluster are
in locked instantiation, the timer is being started (inferred from the behavior
of #620).
This issues is reproducible.
---
Sent from sourceforge.net because [email protected] 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.
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
