Skip to content
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

Panic on startup runtime error: slice bounds out of range hh/processor.go:200 #3436

Closed
nathanielc opened this issue Jul 22, 2015 · 0 comments
Assignees

Comments

@nathanielc
Copy link
Contributor

Got this panic on startup running version: 8c715f7
I have the opentsdb plugin and am running 3 servers in cluster mode.

One node crashed and everytime on start up now it panics with this error. Below is the full startup log.

[metastore] 2015/07/22 20:21:31 [INFO] raft: Node at 10.240.50.65:8088 [Follower] entering Follower state
[metastore] 2015/07/22 20:21:31 read local node id: 1
[metastore] 2015/07/22 20:21:32 [WARN] raft: Heartbeat timeout reached, starting election
[metastore] 2015/07/22 20:21:32 [INFO] raft: Node at 10.240.50.65:8088 [Candidate] entering Candidate state
[metastore] 2015/07/22 20:21:32 [DEBUG] raft: Votes needed: 2
[metastore] 2015/07/22 20:21:32 [DEBUG] raft: Vote granted. Tally: 1
[httpd] 2015/07/22 20:21:32 listening on HTTP: [::]:8086
panic: runtime error: slice bounds out of range

goroutine 35 [running]:
github.com/influxdb/influxdb/services/hh.(*Processor).unmarshalWrite(0xc208044660, 0xe93788, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
        /tmp/tmp.92T9jQoUcC/src/github.com/influxdb/influxdb/services/hh/processor.go:200 +0x160
github.com/influxdb/influxdb/services/hh.func·002(0x3, 0xc2080446c0)
        /tmp/tmp.92T9jQoUcC/src/github.com/influxdb/influxdb/services/hh/processor.go:146 +0x20b
created by github.com/influxdb/influxdb/services/hh.(*Processor).Process
        /tmp/tmp.92T9jQoUcC/src/github.com/influxdb/influxdb/services/hh/processor.go:177 +0x1f7

jwilder added a commit that referenced this issue Jul 27, 2015
A short write has occurred and we do not have enough bytes to determine
the size of the payload.  This is corrupted record that we should drop.
Instead of panicing, log the error and advance the queue since the error
at this location is unreoverable currently.

Fixes #3436
@jwilder jwilder self-assigned this Jul 27, 2015
jwilder added a commit that referenced this issue Aug 6, 2015
A short write has occurred and we do not have enough bytes to determine
the size of the payload.  This is corrupted record that we should drop.
Instead of panicing, log the error and advance the queue since the error
at this location is unreoverable currently.

Fixes #3436
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants