[37094] in Kerberos
Re: Erratic behavior of full resync process
daemon@ATHENA.MIT.EDU (Greg Hudson)
Wed Jun 17 11:15:37 2015
Message-ID: <55818EC9.9080406@mit.edu>
Date: Wed, 17 Jun 2015 11:14:17 -0400
From: Greg Hudson <ghudson@mit.edu>
MIME-Version: 1.0
To: "Leonard J. Peirce" <leonard.peirce+kerberos@wmich.edu>, kerberos@mit.edu
In-Reply-To: <55817590.4050106@wmich.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
On 06/17/2015 09:26 AM, Leonard J. Peirce wrote:
> The cause of kprop hanging was the MTU setting on our CentOS VMs.
Thanks, that is good to know.
> Unrelated to this I did notice something interesting. After reloading
> the database with kdb5_util kadmind naturally forces a full resync of our
> slave. Immediately after the full resync any update will cause our master
> to force *another* full resync of our slave. After this second full
> resync incremental propagation takes over.
This will be improved in 1.14:
http://krbdev.mit.edu/rt/Ticket/Display.html?id=8164
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
