-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
TSM1: panic: runtime error: index out of range #4513
Comments
I can reproduce. Working on a fix. |
Fixed by #4504 |
Hi, I'm sorry, i still have this issue with last nightly (and fresh install without previous data) : https://gist.github.com/Issif/5bb1763d6f0d4c21cb80 |
@jwilder -- any ideas? I am re-opening the issue, but let me know if this is another issue and we can track it there. |
This panic is caused by writing |
Fixed by #4587 |
Started with #4365 (comment)
Hi,
I still have this issue, with
version 0.9.5-nightly-66a31ee, branch master, commit 66a31ee, built '2015-10-20T04:00:43+0000'
My configuration : https://gist.github.com/Issif/0893c15e2cd75156d694
Error logs : https://gist.github.com/Issif/f9b77a2f2aab812696b2
And a tree in shard directory :
.
└── [4.0K Oct 20 10:18] default
├── [4.0K Oct 20 10:18] 1
│ ├── [ 18M Oct 20 10:18] 0000001.tsm1
│ ├── [ 45K Oct 20 10:18] 0000002.tsm1
│ ├── [5.9K Oct 20 10:18] 0000003.tsm1
│ ├── [ 36K Oct 20 10:18] 0000004.tsm1
│ ├── [ 0 Oct 20 10:18] 0000004.tsm1.check
│ ├── [2.1M Oct 20 10:18] _00007.wal
│ ├── [2.2M Oct 20 10:18] _00008.wal
│ ├── [2.0M Oct 20 10:18] _00009.wal
│ ├── [2.2M Oct 20 10:18] _00010.wal
│ ├── [2.2M Oct 20 10:18] _00011.wal
│ ├── [1.6M Oct 20 10:18] _00012.wal
│ ├── [2.1M Oct 20 10:18] _00013.wal
│ ├── [1.7M Oct 20 10:18] _00014.wal
│ ├── [ 988 Oct 20 10:18] fields
│ ├── [ 14M Oct 20 10:18] ids
│ └── [ 12M Oct 20 10:18] series
└── [4.0K Oct 20 10:18] 3
├── [5.5K Oct 20 10:18] 0000001.tsm1
├── [ 200 Oct 20 10:18] fields
├── [3.0K Oct 20 10:18] ids
└── [2.7K Oct 20 10:18] series
It crashes after few seconds each time (started with no data again).
cc @jwilder @Issif
The text was updated successfully, but these errors were encountered: