Just my two cents. I'd consider two questions:
* Does it only occur when attempting to remove multiple peer configurations within a short time frame? If so, I think the likelihood of hitting it in practice is quite low. * Is the system recoverable without service disruption? (e.g., by restarting the master server) If the answer to both is yes, then I'd say we can lower the priority. That said, as I was writing this email, I just realized you already submitted a fix. It's a solid refactoring, and the fix aligns well with your observation. Great job as always. Thanks, Junegunn
