-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Changed the WAL to call write() on every log message #729
Conversation
jenkins go |
Unit testing passed. |
@wadeliuyi Awesome comments 👍 I'll update the PR |
Unit testing passed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, we don't need a list of buffers. Just one buffer is enough. And the buffer should be a ring buffer. That's means it always keep the latest N logs inside.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well done. Let's go
We moved away from the memory buffered version. In this PR, every log message will be written to the system cache to prevent message loss due to the crash fixed #531
And rebased as well
Unit testing failed. |
jenkins go |
Unit testing passed. |
Unit testing passed. |
Unit testing passed. |
We moved away from the memory buffered version. In this PR, every log message will be written to the system cache to prevent message loss due to the crash fixed vesoft-inc#531
We moved away from the memory buffered version. In this PR, every log message will be written to the system cache to prevent message loss due to the crash
fixed #531