Ccb outcome (commit/abort) is synced.
This should not be very litle data compared with all the rest.
It is used to redundantly verify the outcome of CCBs.
The nightmre scenario for me would be some state missmatch within the IMMNDs
that resultet
in a CCB getting derailed (and aborted) at one IMMND but not at others.
Such an error, if it impated CCBs, would at least be caught sooner or later by
this check.
/AndersBj
________________________________
From: A V Mahesh (AVM) [mailto:[email protected]]
Sent: den 2 oktober 2014 15:43
To: [email protected]
Subject: [tickets] [opensaf:tickets] #952 immsv: sync data Mbcsv Check pointing
can be optimized
We also can reduced some overflow by optimizing in FinilizeSync message,
while debugging #1036 I observed ,in some sinario FinilizeSync is containing
Committed CCB data , I this which is not required to be sent/sync to peer IMMD
& IMMND as part of FinilizeSync message
________________________________
[tickets:#952]<http://sourceforge.net/p/opensaf/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: Wed Jul 16, 2014 04:16 AM 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/<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
