ns_server should send 302 reply when view query hits node without any active vbuckets

Details

Type: Bug
Status: Closed
Priority: Critical
Resolution: Fixed
Affects Version/s: 2.0
Fix Version/s: 2.0
Component/s: ns_server
Security Level: Public
Labels:
None

Description

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.

Options
- Sort By Name
- Sort By Date
- Ascending
- Descending
- Download All

Attachments

No_active_vbuckets_UI.png

181 kB

16/Oct/12 4:02 AM

Issue Links

blocks

CCBC-169 Handle 30x HTTP response code when chosen node doesn't have active vbuckets

Activity

Ascending order - Click to sort in descending order

Aleksey Kondratenko made changes - 15/Oct/12 6:37 PM

Field	Original Value	New Value
Description	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.	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.

Iryna Mironava made changes - 16/Oct/12 4:02 AM

Comment

[ verified on build 1854
change - http://review.couchbase.org/#/c/21657/

302 is returned. But on UI error is not user-friendly: {"error":{"xhrStatus":"error","errMsg":""}}
attaching screenshot ]

Iryna Mironava made changes - 16/Oct/12 4:02 AM

Attachment

No_active_vbuckets_UI.png [ 15436 ]

Farshid Ghods made changes - 16/Oct/12 8:53 AM