Open msakrejda opened 7 years ago
@TayTay do you know what version of the CLI and the plugin you were using? I've looked at this and the wait should give up after 20 errors. We should probably still handle 404s specially and exit early (e.g., if the relevant database is destroyed mid-copy), but I don't see how we would go into an indefinite retry loop with the current code.
From @taytay (see https://github.com/heroku/cli/issues/545 )
We regularly create and copy Hobby DBs as part of our deploy process. Occasionally, one of these processes will get hung on a
pg:copy
command. Here's the output from the one I just killed:It goes on like that for another 16 hours, so I think it's safe to say it's dead. :) The copy command looks like this:
heroku pg:copy DATABASE $NEW_DB_ATTACHMENT_NAME --app $HEROKU_APP_NAME --confirm $HEROKU_APP_NAME
In short, we're not doing anything odd. I think that the new DB is disappearing out from under the copy command somehow, and after that, it doesn't know how to recover.