- **status**: review --> fixed
- **Comment**:
changeset: 7137:57718c7160cf
branch: opensaf-4.6.x
parent: 7130:07e703f08875
user: Nagendra Kumar<[email protected]>
date: Thu Nov 26 10:57:33 2015 +0530
summary: amfd: act amfd allows cold sync after it reads config [#1603]
changeset: 7138:5d315f7e61f0
branch: opensaf-4.7.x
parent: 7131:792f80693bfe
user: Nagendra Kumar<[email protected]>
date: Thu Nov 26 10:58:01 2015 +0530
summary: amfd: act amfd allows cold sync after it reads config [#1603]
changeset: 7139:916205f52ca6
tag: tip
parent: 7136:1881b5ad6dd8
user: Nagendra Kumar<[email protected]>
date: Thu Nov 26 10:58:11 2015 +0530
summary: amfd: act amfd allows cold sync after it reads config [#1603]
[staging:57718c]
[staging:5d315f]
[staging:916205]
---
** [tickets:#1603] AMF : Cold sync takes 10 seconds if all the nodes in the
cluster are started simultaneously**
**Status:** fixed
**Milestone:** 4.6.2
**Created:** Thu Nov 19, 2015 06:36 AM UTC by Srikanth R
**Last Updated:** Mon Nov 23, 2015 06:40 AM UTC
**Owner:** Nagendra Kumar
**Attachments:**
-
[1603.patch](https://sourceforge.net/p/opensaf/tickets/1603/attachment/1603.patch)
(435 Bytes; text/x-patch)
Changeset : 4.7 GA 7071
Setup : 4 nodes (bare-metal)
Steps :
-> Enabled the 1 PBE with out any load on the cluster and stopped opensaf on
all the nodes.
-> When opensaf is started on all the four nodes parallely, opensafd on the
standby controller is taking more than 10 seconds to join cluster. Opensafd on
the other nodes took similar normal time,as during sequential bringup
..
Nov 19 11:40:40 SYSTEST-CNTLR-2 osafamfd[20951]: Started
...
Nov 19 11:40:52 SYSTEST-CNTLR-2 osafamfd[20951]: NO Cold sync complete!
...
Nov 19 11:40:53 SYSTEST-CNTLR-2 osafamfnd[20965]: NO Assigned
'safSi=SC-2N,safApp=OpenSAF' STANDBY to 'safSu=SC-2,safSg=2N,safApp=OpenSAF'
Nov 19 11:40:53 SYSTEST-CNTLR-2 opensafd: OpenSAF(4.7.M0 - ) services
successfully started
-> Following is the snippet from the osafamfd trace :
Nov 19 11:40:42.874133 osafamfd [20951:mbcsv_pr_evts.c:0278] <<
mbcsv_hdl_dispatch_all
Nov 19 11:40:42.874139 osafamfd [20951:mbcsv_api.c:0435] <<
mbcsv_process_dispatch_request: retval: 1
Nov 19 11:40:49.859697 osafamfd [20951:mbcsv_tmr.c:0250] TR Timer expired. my
role:2, svc_id:10, pwe_hdl:65537, peer_anchor:564114215690274, tmr
type:NCS_MBCSV_TMR_SEND_COLD_SYNC
Nov 19 11:40:49.859813 osafamfd [20951:mbcsv_api.c:0406] >>
mbcsv_process_dispatch_request: Dispatch MBCSV event
Observation : This issue is there in 4.6 version also. Because of the #1334
fix ( AMFD responds to nid only after initialization is completed ), the issue
got visible . Below is the syslog from standby controller with 4.6 version
when opensafd is started on all the nodes parallelly
Apr 22 14:04:54 SLES-SLOT2 osafamfnd[20334]: NO Assigned
'safSi=SC-2N,safApp=OpenSAF' STANDBY to 'safSu=SC-2,safSg=2N,safApp=OpenSAF'
Apr 22 14:04:55 SLES-SLOT2 opensafd: OpenSAF(4.6.FC - ) services successfully
started
Apr 22 14:05:05 SLES-SLOT2 osafamfd[20324]: NO Cold sync complete!
---
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.
------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
