Log servers might not be checked when using locality based exclusion
johscheuer opened this issue · comments
The intention of this issue is to create visibility for the limitation mentioned in #11009. We update the documentation to reflect this limitation, but I think it's good to have an issue to track to fix for this.
TLDR: If a log process is not running (reporting to the worker list), it will be missed by the locality based exclusions and there will be no validation if the mutation of this log process are already persisted. This is only true for the blocking of the exclude command, the actual exclusion is still happening in the background.