-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Self-monitoring panic after inserting data #2421
Comments
Thanks @mark-rushakoff -- I'll take a look. |
Cannot reproduce this. Blew away the data, and started a single brand-new node.
|
@otoolep this is the issue I was having here: #2422 (comment). In my case starting a fresh node (deleting the data dir) fixed the problem but seems like there might be something in there. |
@otoolep the problem just appeared again after restarting the server a couple of times. Seems like the This is how I'm seeing the shards_diag row get's processed:
As you can see in the second line the "path" column is there even though there's no value for that. I don't know how shards are being handled internally but I believe that the problem must be around there. |
@marcosnils -- could you please open a separate ticket for this issue, and include the details above (and anything else that will help me repro this). |
@otoolep found the error in the code I'll send a PR shortly. Seems like an easy fix |
@mark-rushakoff -- I am pretty sure the issue is actually the same after all, as @marcosnils was pointing out. Should be fixed by #2431 |
Confirmed fixed as of 86b9ec5. |
Built from source at 615aabf.
After starting InfluxDB with an empty data directory, running this command:
causes the server to panic:
The text was updated successfully, but these errors were encountered: