Details
-
Bug
-
Resolution: Duplicate
-
Major
-
Cheshire-Cat
-
Untriaged
-
Centos 64-bit
-
1
-
Unknown
Description
Since build: 7.0.0-4291
Setup: 4 Nodes:
- kv
- kv, query, index, search
- kv, query, index, search
- kv, query, index, search
Issue:
When performing a hard failover on the 1st node (master), and then ejecting the node, the server returns a "Unexpected server error, request logged" 500 error. It appears that the node does indeed get ejected successfully though. Also, this only happens when the node being ejected was the master node.
Steps to reproduce:
On a 4 node cluster as above.
Hard failover the master node:
curl -v -X POST -u Administrator:password <node2>/controller/failOver -d 'otpNode=ns_1@<node1>'
Then try to ejectNode:
curl -v -X POST -u Administrator:password <node2>:8091/controller/ejectNode -d 'otpNode=ns_1@<node1>'
This will return the error message.
I've attached logs from a test run that does this.
Setup of test cluster
172.23.109.23:::kv
172.23.104.143:::kv,index,fts,n1ql
172.23.109.21:::kv,index,fts,n1ql
172.23.109.22:::kv,index,fts,n1ql
Attachments
Issue Links
- duplicates
-
MB-43899 "Unexpected server error, request logged." upon adding a node to the cluster
- Closed