A Pull Request should be associated with an Issue.
We wish to have discussions in Issues. A single issue may be targeted by multiple PRs.
If you're offering a new feature or fixing anything, we'd like to know beforehand in Issues,
and potentially we'll be able to point development in a particular direction.
This PR increases the startSlavePostWaitMilliseconds as we are seeing an error when running gh-ost in some cloud environments that the Slave_IO_Running is Connecting rather than Yes as expected.
We found this old PR that described the issue we're having https://github.com/github/gh-ost/pull/337 - as a first step we are increasing by doubling the value. If this test is successful, then we'll look into making this something that could be configured.
In case this PR introduced Go code changes:
[ ] contributed code is using same conventions as original code
[ ] script/cibuild returns with no formatting errors, build errors or unit test errors.
A Pull Request should be associated with an Issue.
Related issue:
Description
This PR increases the
startSlavePostWaitMillisecondsas we are seeing an error when runninggh-ostin some cloud environments that theSlave_IO_RunningisConnectingrather thanYesas expected.We found this old PR that described the issue we're having https://github.com/github/gh-ost/pull/337 - as a first step we are increasing by doubling the value. If this test is successful, then we'll look into making this something that could be configured.
script/cibuildreturns with no formatting errors, build errors or unit test errors.