-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
stability: crash on trace #4786
Comments
Only one stack trace because of changes in 1.6. See On Wed, Mar 2, 2016 at 4:09 PM, marc [email protected] wrote:
|
Without having looked in detail, this is likely trace getting finished after a context timeout, but then still coming out of Raft, so use-after-finish. Had trouble with this before - annoying stuff. |
still happening, somewhat regularly (eg: a few times a day on a 4 node cluster with load):
|
On a running cluster:
oddly, I only have one stack trace.
@tschottdorf: you're probably the most familiar with tracing code.
The relevant line is:
The text was updated successfully, but these errors were encountered: