sleeping 500ms after 'START SLAVE' #337
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Storyline: #335
Immediately following
START SLAVE
command,gh-ost
sleeps for500ms
to allow the replica the time to connect to its master.Otherwise, if
SHOW SLAVE STATUS
is immediately executed afterSTART SLAVE
, theSlave_IO_thread
can still be inConnecting
state, which is interpreted as "oh replication isn't running".gofmt
(please avoidgoimports
)./build.sh
./test.sh