I just created new releases for four of my projects (nodes 2560103–9), and each time except on the last one I got, after a longer load, a "504 Gateway Timeout" response when trying to save the new release node.
Refreshing the page (and re-sending the POST data) yields the node edit form with an error message that a release node for that version has already been created. (I then just had to wait a few minutes to see them, because they aren't listed on the project page until a tarball is created for them.)
Since this is on specific pages, not "on random requests", I didn't want to reopen #2319567: 504 Gateway Timeout on random requests, but it might of course be related.
Comments
Comment #2
drummI happened to catch a failed release packaging job from one of these. The error was:
Depending on how quickly you made the releases, all of them could have been waiting on the same lock.
Comment #3
drummI believe #2560181: 504 when deleting nodes was the root cause.
node_delete_multiple()
is wrapped in a DB transaction; in the middle of that is when ApacheSolr module sends delete requests, which were slow and timing out, prolonging the DB transactions. Creating nodes hits a lot of the same lockable tables.