)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":597,"name":"Pete Zaitcev","email":"zaitcev@kotori.zaitcev.us","username":"zaitcev"},"change_message_id":"32200ede4cb928a48bc212c3d5ebe4c9502a60ce","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"ff3cbfb0_b82430a2","updated":"2023-06-23 19:18:17.000000000","message":"Seems like a good idea in the abstract, but what are the circumstances that prompted this?","commit_id":"fa088eb72d17aa37e72ce479411a48ea70e4d92e"},{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"7c24eecd7c11690db74be1aac570588f4f4ca6c6","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"b5442739_4daaf0fc","updated":"2024-06-27 20:39:50.000000000","message":"Small, low risk","commit_id":"fa088eb72d17aa37e72ce479411a48ea70e4d92e"},{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"a3ae2fa507d3206d1d53db0a5f77a53f95d976ed","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"00035f46_d0e531ca","in_reply_to":"ff3cbfb0_b82430a2","updated":"2023-06-27 17:33:15.000000000","message":"Grasping at straws, trying to figure out why reid_g would need to stop the replicator/reconstructor to clean up some connections in `TIME_WAIT` that were preventing him from being able to restart the object-server. See https://meetings.opendev.org/irclogs/%23openstack-swift/%23openstack-swift.2023-06-22.log.html#t2023-06-22T12:53:53 (some of the convo carries over into the next day)\n\n\u003e I keep running into issues where we stop object and start it again and end up getting messages that some of the ports are already in use (port per device config). The only way I have found to fix it is to reboot the server. Sometimes we get the message after a fresh reboot as the services are starting. It is happening in Ussuri and Yoga.\n\nbut later\n\n\u003e New entries keep popping up from other object-server-replication servers. Each time a new connection appears, that new connection timer starts at 60s\n\n\u003e it looks like all of our dangling time-waits close out if we stop object-replicator and wait.\n\nIt seems especially strange to me since eventlet\u0027s going to [turn on `SO_REUSEPORT` for us](https://github.com/eventlet/eventlet/blob/master/eventlet/convenience.py#L64). I would\u0027ve thought we should be able to re-bind no problem 😕","commit_id":"fa088eb72d17aa37e72ce479411a48ea70e4d92e"}]}