Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

spirit: error: wait position #343

Closed
DevMasterSoonToBe opened this issue Aug 30, 2024 · 2 comments
Closed

spirit: error: wait position #343

DevMasterSoonToBe opened this issue Aug 30, 2024 · 2 comments

Comments

@DevMasterSoonToBe
Copy link

Hi,

We are trying to resume Spirit from checkpoint after _sentinel is dropped and it does checksum but it fails after a long time with this output:

INFO[80525] migration status: state=checksum checksum-progress=“8a868fff8dc26038018dd6d8aa8f546c”/“8a868fff8fe55566018fe590b55c09ef” binlog-deltas=0 total-time=22h22m6s checksum-time=22h21m55s conns-in-use=5
INFO[80530] finished periodic flush of binary log: total-duration=4.51µs batch-size=1000
INFO[80545] checksum passed
INFO[80545] starting to flush changeset
INFO[80555] closing canal
INFO[80555] syncer is closing...
WARN[80555] releasing metadata lock: spirit_xxxxxxx_xxxxxxx
INFO[80555] kill last connection id 79927
INFO[80555] syncer is closed
spirit: error: wait position (mysql-bin-changelog.033214, 157) too long > 10s

Previously we have deleted sentinel table but it didn't do cutover because spirit was not running. We are thinking it should do cutover after we run spirit again without sentinel table in the database. However it fails with this **spirit: error: wait position (mysql-bin-changelog.033214, 157) too long > 10s** error and could you advise what might be the issue that spirit informs about here?

@morgo
Copy link
Collaborator

morgo commented Aug 30, 2024

I believe this is a duplicate of #337 (fixed)

We introduced this regression about 1 month ago in #332 and then worked around it in #339

The final fix was just merged though with #340

Please check it out and let me know if you are experiencing issues with it.

@morgo
Copy link
Collaborator

morgo commented Sep 27, 2024

I'm going to close this as fixed. Please re-open if you experience otherwise, thanks!

@morgo morgo closed this as completed Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants