when the Sync happens the following are the events are broad-casted by IMMD :
1. class create at the time of sync, IMMND_EVT_A2ND_CLASS_CREATE is
broad-casted.IMMD sets IMMND_EVT_D2ND_GLOB_FEVS_REQ for mbcsv check-pointing
and broadcasting
2. when searchInit is called for syncing objects of the class then,
IMMD_EVT_ND2D_SYNC_FEVS_BASE will be broadcasted.
IMMD sets IMMND_EVT_D2ND_GLOB_FEVS_REQ for mbcsv check-pointing and broadcasting
3. For each object the sync process calls immsv_sync.immsv_sync sends a batch
of the message equivalent to IMMSV_DEFAULT_MAX_SYNC_BATCH_SIZE(which will be
58931 bytes). The event sent is IMMND_EVT_A2ND_OBJ_SYNC_2.
IMMD uses IMMND_EVT_D2ND_GLOB_FEVS_REQ_2 for mbcsv check-pointing and
broadcasting.
>From buffering perspective the first and second event types(discussed above)
>will have less message buffer and can be ignored when the performance is
>considered. where as the third event mentioned above will have a maximum
>buffer size, and will have performance impacts. Because of which sync is
>delayed.
The solution is, when check-pointing to standby IMMD for
IMMND_EVT_D2ND_GLOB_FEVS_REQ_2, the fevs message buffer will be set to NULL and
message size will be set to 0. so, that the MBCSV check-pointing happens only
for header.
---
** [tickets:#952] immsv: sync data Mbcsv Check pointing can be optimized**
**Status:** assigned
**Milestone:** future
**Created:** Tue Jul 08, 2014 03:31 AM UTC by A V Mahesh (AVM)
**Last Updated:** Thu Jun 04, 2015 09:18 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.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
