Thank you for the response Roland. I will start going through the source code. In the meantime, it will be great if these preliminary questions can be answered.
Q: Is Protocol C a variant of any standard atomic commit protocol (like 2PC/3PC etc.)? Or is it a proprietary algorithm? Q: Let's assume there are 2 disks (D1, D2). Let's assume that D2 is experiencing a fail-recover situation, but D1 has failed after a D2 failure, but before D2 has recovered. What is the behavior of DRBD in such a case? Are all future disk writes blocked until both D1 and D2 are available, and are confirmed to be in sync? Regards, Ravi. On Fri, Sep 8, 2017 at 2:07 AM, Roland Kammerer <[email protected]> wrote: > On Thu, Sep 07, 2017 at 04:08:10PM -0700, Ravi Kiran Chilakapati wrote: > > Hi, > > > > I was wondering where I could find more information on DRBD's Protocol > C? I > > was hoping I could find a resource without resorting to the source code. > > > > I tried the following with no luck. > > 1) asking around on Stackoverflow ( > > https://stackoverflow.com/questions/45998076/an- > explanation-of-drbd-protocol-c > > ) > > 2) scanning the user guide (http://docs.linbit.com/docs/users-guide-9.0/ > ) > > There is no official "user-friendly" documentation besides the UG. So > ask specific questions and we can answer them (and probably add them to > the UG in some high level section) or read the code... > > Regards, rck > _______________________________________________ > drbd-user mailing list > [email protected] > http://lists.linbit.com/mailman/listinfo/drbd-user >
_______________________________________________ drbd-user mailing list [email protected] http://lists.linbit.com/mailman/listinfo/drbd-user
