To be entirely honest, I almost never run my migrations via capistrano anymore. I've been burned too many times by issues that come up during a migration, that need manual intervention, so I usually do:
$ cap deploy:update $ ssh to one of the app servers and run the migrations $ cap deploy:restart That doesn't answer your question, though. Probably what needs to happen is that the migrate task should force all connections to close after the migration finishes, so that the next command that runs causes them to open anew. You'd need to monkey patch the migrate task itself to do that, though. - Jamis On Wed, Oct 21, 2009 at 6:44 PM, Mike <[email protected]> wrote: > > We have a long running migration. After the migration finishes on one > box, when Cap starts the next task, the other ssh connections to the > other servers timeout and the deploy fails. > > I have read a number of items on the net and from this group regarding > this issue. However, there seems to be nothing that resolves the > situation or at least nothing specific about what versions of cap and/ > or ruby solve the issue. > > I'm sure that many others must be encountering this problem and I > would like to know if there is a highly recommended way to deal with > this issue, any help is appreciated. > > Mike > > > --~--~---------~--~----~------------~-------~--~----~ * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en -~----------~----~----~----~------~----~------~--~---
