- **status**: review --> fixed
- **Comment**:
changeset: 6511:9b3ea213edb3
branch: opensaf-4.4.x
parent: 6507:a9f0e7afef52
user: Nagendra Kumar<[email protected]>
date: Tue May 05 17:06:34 2015 +0530
summary: amfd: respond to nid only after initialization is completed [#1334]
changeset: 6512:81e237b5b6cc
branch: opensaf-4.5.x
parent: 6508:aba458b4cb6a
user: Nagendra Kumar<[email protected]>
date: Tue May 05 17:07:04 2015 +0530
summary: amfd: respond to nid only after initialization is completed [#1334]
changeset: 6513:5366987cdf2d
branch: opensaf-4.6.x
parent: 6509:0b2a391068f9
user: Nagendra Kumar<[email protected]>
date: Tue May 05 17:07:13 2015 +0530
summary: amfd: respond to nid only after initialization is completed [#1334]
changeset: 6514:58a11403b3dc
tag: tip
parent: 6510:08382ad144ea
user: Nagendra Kumar<[email protected]>
date: Tue May 05 17:07:21 2015 +0530
summary: amfd: respond to nid only after initialization is completed [#1334]
[staging:9b3ea2]
[staging:81e237]
[staging:536698]
[staging:58a114]
---
** [tickets:#1334] Standby reboots delayed when failover is trigerred during
standby synch is in progress**
**Status:** fixed
**Milestone:** 4.5.2
**Created:** Wed Apr 22, 2015 04:42 PM UTC by Srikanth R
**Last Updated:** Mon Apr 27, 2015 09:25 AM UTC
**Owner:** Nagendra Kumar
Changeset : 6377
Issue : Out of sync (failed over) new active controller should go for immediate
reboot
During failover, if the standby controller is OUT OF SYNC and could not get
promoted to active, amfnd should reboot the node immediately. The node went for
reboot after 180 seconds or so. In this scenario, cold sync could not be
completed.Hence Out of sync.
Apr 22 21:02:45 CONTROLLER-2 osaffmd[5534]: NO Current role: STANDBY
Apr 22 21:02:45 CONTROLLER-2 osaffmd[5534]: Rebooting OpenSAF NodeId = 131343
EE Name = ,
Apr 22 21:02:45 CONTROLLER-2 osaffmd[5534]: NO Controller Failover: Setting
role to ACTIVE
Apr 22 21:02:45 CONTROLLER-2 osafrded[5525]: NO RDE role set to ACTIVE
Apr 22 21:02:45 CONTROLLER-2 osafamfd[5610]: NO FAILOVER StandBy --> Active
Apr 22 21:02:45 CONTROLLER-2 osafamfd[5610]: ER FAILOVER StandBy --> Active
FAILED, Standby OUT OF SYNC
Apr 22 21:02:45 CONTROLLER-2 osafamfd[5610]: ER avd_role_change role change
failure
Apr 22 21:05:43 CONTROLLER-2 osafamfnd[5620]: ER AMF director unexpectedly
crashed
Apr 22 21:05:43 CONTROLLER-2 osafamfnd[5620]: Rebooting OpenSAF NodeId = 131599
EE Name = , Reason: local AVD down(Adest) or both AVD down(Vdest) received,
OwnNodeId = 131599, SupervisionTime = 60
Apr 22 21:05:43 CONTROLLER-2 opensaf_reboot: Rebooting local node; timeout=60
In similar scenario, fmd process rebooted the node when it detected that the
standby is not ready to take active role.
Apr 22 21:58:10 CONTROLLER-1 osaffmd[5516]: Rebooting OpenSAF NodeId = 0 EE
Name = No EE Mapped, Reason: Failover occurred, but this node is not yet ready,
OwnNodeId = 131343, SupervisionTime = 60
---
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.------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
