- **status**: review --> fixed
- **Comment**:
changeset: 6642:3647c1ea307b
tag: tip
user: Neelakanta Reddy <[email protected]>
date: Wed Jul 08 12:01:18 2015 +0530
summary: imm :checkpoint only FEVS header for sync messages [#952]
---
** [tickets:#952] immsv: sync data Mbcsv Check pointing can be optimized**
**Status:** fixed
**Milestone:** 4.7-Tentative
**Created:** Tue Jul 08, 2014 03:31 AM UTC by A V Mahesh (AVM)
**Last Updated:** Wed Jun 24, 2015 07:21 AM UTC
**Owner:** Neelakanta Reddy
On 7/7/2014 9:58 AM, A V Mahesh wrote:
While IMMD broadcasting datasync message (IMMND_EVT_D2ND_GLOB_FEVS_REQ_2)
to IMMNDs additionally the same message (including large sync data) getting
Check pointed to standby director , this means for eachdata`sync FEVS message
(IMMND_EVT_D2ND_GLOB_FEVS_REQ_2) IMMD is sending two messages one to IMMND's as
BCAST and one to peer IMMD as R-BCAST (MBCSV).
Currently in my observation if fault happens when sync is in-progress that sync
gets aborted ,
and the new active is starting a fresh sync. If my understanding is right ,
why we need to Check point IMMND_EVT_D2ND_GLOB_FEVS_REQ_2 message to peer IMMD
including large sync data?
---
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.
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
