-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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: panic on RangeLookup dispatched to correct range #6000
Comments
Could you save the data? Only that node is ok. Please don't restart (you On Tue, Apr 12, 2016 at 9:45 AM marc [email protected] wrote:
-- Tobias |
yeah, it's still down, but I'm backing up with suffix |
Is this data still available somewhere? |
This looks like a meta2 gap? Closing as dupe of #9265. |
build sha: c382dd7
Beta cluster with photos + block_writer load. Restarted from scratch earlier today.
~1h after a restart, encountered the following:
Full log (from
ec2-52-91-234-29.compute-1.amazonaws.com
):node4.log.parse.txt
The text was updated successfully, but these errors were encountered: