It's very common, when Swift backend machines are doing lots of rebalancing after their weights have been changed, to get a ton of spammy alerts:
17:58:08 <+icinga-wm> PROBLEM - swift-container-server on ms-be2024 is CRITICAL: CHECK_NRPE: Error - Could not connect to 10.192.48.60: Connection reset by peer https://wikitech.wikimedia.org/wiki/Swift 17:58:34 <+icinga-wm> PROBLEM - MD RAID on ms-be2019 is CRITICAL: CHECK_NRPE: Error - Could not connect to 10.192.16.161: Connection reset by peer 17:58:34 <+icinga-wm> PROBLEM - puppet last run on ms-be2019 is CRITICAL: CHECK_NRPE: Error - Could not connect to 10.192.16.161: Connection reset by peer
While the operation of Swift itself doesn't seem to be obviously adversely affected by all the I/O of rebalancing, certainly Icinga NRPEs are sensitive to it.
This is a task to verify the truth of the former part of the above statement, and to minimize the impact of rebalancing upon monitoring
