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

NPE in raft.removeNode(mcc.msg.NodeID) #2291

Closed
tbg opened this issue Aug 28, 2015 · 3 comments · Fixed by #2334
Closed

NPE in raft.removeNode(mcc.msg.NodeID) #2291

tbg opened this issue Aug 28, 2015 · 3 comments · Fixed by #2334

Comments

@tbg
Copy link
Member

tbg commented Aug 28, 2015

panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x8 pc=0x4671397]

goroutine 4154 [running]:
github.com/coreos/etcd/raft.(*multiNode).run(0xc820463020)
        /Users/tschottdorf/go/src/github.com/coreos/etcd/raft/multinode.go:253 +0x14e7
created by github.com/coreos/etcd/raft.StartMultiNode
        /Users/tschottdorf/go/src/github.com/coreos/etcd/raft/multinode.go:56 +0x30d

offending code:

            case pb.ConfChangeRemoveNode:
                group.raft.removeNode(mcc.msg.NodeID)

in (not raft-pertinent) WIP freshly rebased on top of master at time of writing. Can't reproduce.

@mrtracy
Copy link
Contributor

mrtracy commented Aug 31, 2015

Ben opened a few pull requests against etcd last week for similar NPEs:

etcd-io/etcd#3396
etcd-io/etcd#3404

These all related to configuration changes.

@bdarnell
Copy link
Contributor

bdarnell commented Sep 2, 2015

Probably too late now, but do you have any more information? Which test case was this panic in? Do you have any more of the logs?

I suspect it's a race involving Store.RemoveReplica (in TestReplicateAddAndRemove), which might put this failure in the same category as #1911.

@bdarnell
Copy link
Contributor

bdarnell commented Sep 2, 2015

Just went back to the logs in #1911; this is an exact dupe.

@bdarnell bdarnell closed this as completed Sep 2, 2015
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

Successfully merging a pull request may close this issue.

3 participants