SERVER-135628ClosedDuplicate

A brief KMIP outage during startup aborts the node instead of being waited out

h2. The problem When a node starts and cannot decrypt its checkpoint because the KMIP server is briefly unavailable, the node aborts. It does so again on every restart, for as long as the outage lasts, instead of becoming a secondary once KMIP answers. The outage need not be long or permanent — the same stall was ridden out successfully in one incident and aborted the node in another, and what separated them was whether the last permitted retry happened to succeed. The abort also names no

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue

No components specified.

Labels
Tags and classification
disagg-availabilitydisagg-encryption