Erratic behavior of full resync process

[Greg Hudson]

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