[33508] in Kerberos
Re: Database locking during kprops, MIT 1.8
daemon@ATHENA.MIT.EDU (Greg Hudson)
Thu Jun 23 10:12:21 2011
From: Greg Hudson <ghudson@mit.edu>
To: John Devitofranceschi <jdvf@optonline.net>
In-Reply-To: <9655DCF6-A5CD-43D3-ACEB-C203D1DB5E49@optonline.net>
Date: Thu, 23 Jun 2011 10:12:10 -0400
Message-ID: <1308838330.19355.39.camel@t410>
Mime-Version: 1.0
Cc: Jeremy Hunt <jeremyh@optimation.com.au>,
"kerberos@mit.edu" <kerberos@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
On Wed, 2011-06-22 at 18:01 -0400, John Devitofranceschi wrote:
> I was wondering if there was any more clarity to be had around 'issue
> 3' here.
Issue 3 is about the install guide's proviso that:
* The "call out to `kprop'" mechanism is a bit fragile; if the
`kprop' propagation fails to connect for some reason, the process
on the slave may hang waiting for it, and will need to be
restarted.
After investigation, I believe this proviso is outdated. In December
2008, Ken committed some changes from Shawn Emery to add a timer to the
loop which waits for a kprop connection. So the slave should eventually
return to the iprop main loop if the master fails to connect for a full
dump. (The slave will then probably try to initiate a new full dump.)
Those changes should have landed in 1.7. I will update our install
guide to remove the proviso.
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
