In one of my test case where I was creating contentious objected creation on
bother Active & Standby then triggered fail-over and observed very large
data (size:92808 see below ) in FinilizeSync message , if I Stop Object
creation on both node and give some delay of 5 minits , and then do fail-over
IMMD is sending very small data size:11682 ( see below )
====================================================================================
Sep 30 9:53:25.977339 osafimmd [868:immd_evt.c:0273] T5 immd_evt_proc_fevs_req
send_count:68734 size:60596
Sep 30 9:53:26.072524 osafimmd [868:immd_evt.c:0273] T5 immd_evt_proc_fevs_req
send_count:68735 size:60594 <==========Sync
Sep 30 9:53:26.142643 osafimmd [868:immd_evt.c:0273] T5 immd_evt_proc_fevs_req
send_count:68736 size:50486
.........................................
Sep 30 9:53:26.204038 osafimmd [868:immd_evt.c:0273] T5 immd_evt_proc_fevs_req
send_count:68748 size:628
Sep 30 9:53:26.207858 osafimmd [868:immd_evt.c:0273] T5 immd_evt_proc_fevs_req
send_count:68749 size:16
Sep 30 9:53:26.211459 osafimmd [868:immd_evt.c:0273] T5 immd_evt_proc_fevs_req
send_count:68750 size:1716
Sep 30 9:53:26.215674 osafimmd [868:immd_evt.c:0273] T5 immd_evt_proc_fevs_req
send_count:68751 size:11682 <====== with some delay FinilizeSync =============
====================================================================================
Sep 30 10:05:31.284906 osafimmd [21206:immd_evt.c:0273] T5
immd_evt_proc_fevs_req send_count:78183 size:60560
Sep 30 10:05:31.365129 osafimmd [21206:immd_evt.c:0273] T5
immd_evt_proc_fevs_req send_count:78184 size:60598 <==========Sync
Sep 30 10:05:31.404772 osafimmd [21206:immd_evt.c:0273] T5
immd_evt_proc_fevs_req send_count:78185 size:17820
Sep 30 10:05:31.407538 osafimmd [21206:immd_evt.c:0273] T5
immd_evt_proc_fevs_req send_count:78186 size:16
.....................
Sep 30 10:05:31.473186 osafimmd [21206:immd_evt.c:0273] T5
immd_evt_proc_fevs_req send_count:78198 size:16
Sep 30 10:05:31.475273 osafimmd [21206:immd_evt.c:0273] T5
immd_evt_proc_fevs_req send_count:78199 size:1716
Sep 30 10:05:31.480167 osafimmd [21206:immd_evt.c:0273] T5
immd_evt_proc_fevs_req send_count:78200 size:92808 <=======with out some delay
FinilizeSync============
====================================================================================
---
** [tickets:#952] immsv: sync data Mbcsv Check pointing can be optimized**
**Status:** unassigned
**Milestone:** future
**Created:** Tue Jul 08, 2014 03:31 AM UTC by A V Mahesh (AVM)
**Last Updated:** Thu Oct 02, 2014 01:46 PM UTC
**Owner:** nobody
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.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
