| From: | ghudson@mit.edu |
| Subject: | git commit |
Check for unstable ulog in ulog_get_entries
If a process terminates in the middle of a logged database update, it
will release its lock and leave the ulog in the KDB_UNSTABLE state.
kadmind should notice this when it calls ulog_get_entries, but right
now it only checks for the KDB_CORRUPT state (which is never set any
more) and does not recover. Check for any state other than KDB_STABLE
and recover by resetting the ulog and forcing full resyncs to slaves.
https://github.com/krb5/krb5/commit/91ef7d4c3f892b99630422a71780788f2d1c04d7
Author: Greg Hudson <ghudson@mit.edu>
Commit: 91ef7d4c3f892b99630422a71780788f2d1c04d7
Branch: master
src/lib/kdb/kdb_log.c | 10 ++++------
1 files changed, 4 insertions(+), 6 deletions(-)