Critical Description
When adding a n1ql node through ns_server, the node itself thinks it's not part of a cluster.
Things work fine once the node is stopped and started again.
This is down to the implementation of MB-20773 - which queries clustering on start up, and the implementation of n1ql clustering.
The issue is that ns_server does not report the n1ql service as being active until the n1ql node has been successfully added - in a way not too dissimilar from MB-22588.
Attachments
| For Gerrit Dashboard: MB-22656 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 74533,3 | MB-22656 n1ql nodes don't determine their own name correctly | master | go-couchbase | Status: MERGED | +2 | +1 |
| 74534,4 | MB-22656 n1ql node may fail to determine their own name | master | query | Status: MERGED | +2 | +1 |
| 81908,3 | MB-22656 fix system:nodes for directly named hosts | master | query | Status: MERGED | +2 | +1 |
| 82042,2 | MB-22656 fix naming test | master | query | Status: MERGED | +2 | +1 |