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

bug: Issue1090.test occasionally fails to run #1234

Closed
2 of 3 tasks
konghaiya opened this issue Jan 17, 2023 · 0 comments · Fixed by #1314
Closed
2 of 3 tasks

bug: Issue1090.test occasionally fails to run #1234

konghaiya opened this issue Jan 17, 2023 · 0 comments · Fixed by #1314
Assignees
Labels
A-bug Something isn't working B-master-replica master/replica sync, replay B-storage data type, data storage, insert,update,delete, transactions prio: low Low priority

Comments

@konghaiya
Copy link
Collaborator

Have you read the Contributing Guidelines on issues?

Please confirm if bug report does NOT exists already ?

  • I confirm there is no existing issue for this

Describe the problem

There is a problem in the method of waiting for the master/slave synchronization to complete, which leads to the data not being synchronized, and then proceed to the next step

Expected behavior

Use the correct method to determine whether the slave database is synchronized

How To Reproduce

No response

Environment

No response

Are you interested in submitting a PR to solve the problem?

  • Yes, I will!
@konghaiya konghaiya added the A-bug Something isn't working label Jan 17, 2023
@wisehead wisehead added this to the stonedb_5.7_v1.0.3 milestone Jan 18, 2023
@wisehead wisehead added the B-master-replica master/replica sync, replay label Jan 18, 2023
@konghaiya konghaiya added the prio: low Low priority label Jan 28, 2023
@hustjieke hustjieke added the B-storage data type, data storage, insert,update,delete, transactions label Jan 30, 2023
konghaiya added a commit to konghaiya/stonedb that referenced this issue Feb 16, 2023
Cause of the problem:
There is a problem in the method of waiting for the master/slave synchronization to complete,
which leads to the data not being synchronized, and then proceed to the next step

Modify scheme:
Use the correct method to determine whether the slave database is synchronized
konghaiya added a commit to konghaiya/stonedb that referenced this issue Feb 16, 2023
Cause of the problem:
There is a problem in the method of waiting for the master/slave synchronization to complete,
which leads to the data not being synchronized, and then proceed to the next step

Modify scheme:
Use the correct method to determine whether the slave database is synchronized
konghaiya added a commit to konghaiya/stonedb that referenced this issue Feb 16, 2023
Cause of the problem:
There is a problem in the method of waiting for the master/slave synchronization to complete,
which leads to the data not being synchronized, and then proceed to the next step

Modify scheme:
Use the correct method to determine whether the slave database is synchronized
@mergify mergify bot closed this as completed in #1314 Feb 16, 2023
mergify bot pushed a commit that referenced this issue Feb 16, 2023
Cause of the problem:
There is a problem in the method of waiting for the master/slave synchronization to complete,
which leads to the data not being synchronized, and then proceed to the next step

Modify scheme:
Use the correct method to determine whether the slave database is synchronized
mergify bot pushed a commit that referenced this issue Feb 27, 2023
Cause of the problem:
There is a problem in the method of waiting for the master/slave synchronization to complete,
which leads to the data not being synchronized, and then proceed to the next step

Modify scheme:
Use the correct method to determine whether the slave database is synchronized
konghaiya added a commit to konghaiya/stonedb that referenced this issue Mar 7, 2023
Cause of the problem:
There is a problem in the method of waiting for the master/slave synchronization to complete,
which leads to the data not being synchronized, and then proceed to the next step

Modify scheme:
Use the correct method to determine whether the slave database is synchronized
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-bug Something isn't working B-master-replica master/replica sync, replay B-storage data type, data storage, insert,update,delete, transactions prio: low Low priority
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants