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.

Sign up for GitHub

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

Jump to bottom

MariaDB can cause spine to abort prematurely despite error handling #274

Closed
TheWitness opened this issue Jul 5, 2022 · 0 comments
Closed

MariaDB can cause spine to abort prematurely despite error handling #274

TheWitness opened this issue Jul 5, 2022 · 0 comments
Labels
bug resolved
Milestone
v1.2.22

Comments

@TheWitness
Copy link
Member

Describe the bug

From time to time, spine will receive 2013 errors due to various reasons. This almost inevitably leads to a SIGABORT due to some linked list issues in the MariaDB API.

Expected behavior

Spine should increase the read/write timeouts to reduce the likelihood of reconnects having to take place.
@TheWitness TheWitness added the bug label Jul 5, 2022
@TheWitness TheWitness added this to the v1.2.22 milestone Jul 5, 2022
TheWitness added a commit that referenced this issue Jul 5, 2022
@TheWitness
Fixing #273 - Log time and #274 - Reduce SIGABORT's
7937348
@netniV netniV changed the title Spine get's interrupted via 2013 errors which leads to SIGABORTS MariaDB can cause spine to abort prematurely despite error handling Aug 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug resolved
Projects
None yet
Milestone
v1.2.22
Development

No branches or pull requests
1 participant
@TheWitness