)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"9b01380871491c6579d9e0da8aff26413523afe7","unresolved":false,"context_lines":[{"line_number":13,"context_line":""},{"line_number":14,"context_line":"The issue being addressed here is that if a compute node is deleted by a host"},{"line_number":15,"context_line":"which thinks it is an orphan, then the compute host that actually owns the node"},{"line_number":16,"context_line":"might not recreate it if the node is already in its resource tracker cache."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"This change fixes the issue by clearing nodes from the resource tracker cache"},{"line_number":19,"context_line":"for which a compute node entry does not exist. Then, when the available"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":5,"id":"1f493fa4_3ab73ad8","line":16,"updated":"2020-04-22 19:55:21.000000000","message":"I\u0027m having a bit of a hard time figuring out exactly what sequence of events has to happen on each compute node such that we\u0027ll miss re-creating the node in the database on the first or second run of the u-a-r periodic.\n\nCould you maybe give a sequence across two nodes with pointers (even if just by name) to the code to help me follow? Doesn\u0027t have to be in the commit message here, but at least a review comment that is findable in the future.\n\nI\u0027m not really asserting that you\u0027re wrong here, but I want to understand the actual sequence so I can convince myself that you\u0027re actually fixing something and also that you\u0027re not just narrowing a window while leaving a race.","commit_id":"6ffcbfa2448c2e5b9fae2d66a7cd2a70ba07ee63"}]}