[MB-6922] ns_server should send 302 reply when view query hits node without any active vbuckets

Dependency — Tue, 15 Jan 2013 02:27:59 -0600

Client's would like to cache list of bucket's nodes. Currently when node is rebalanced out there's period of time when it doesn't have any active vbuckets left. Our view merger cannot deal with that so we currently return 404.

But SDK folks would like us to handle it similarly to not-my-vbucket at memcached level. And they want to send back 302 with some random node with vbuckets in Location.

update: I think I wasn't clear enough. 404 is hard to interpret from client perspective. It may mean 'no such ddoc exist' or 'no such bucket exists' or currently 'you cannot query this node'. 302 instead of 404 for such condition would be much clearer signal to client.

Couchbase

[MB-6922] ns_server should send 302 reply when view query hits node without any active vbuckets