Couchbase Server

default bucket cannot be created on port 11211, must specify a different port

Details

Description

[root@ip-10-127-157-49 ~]# /opt/membase/bin/cli/membase bucket-create -c 127.0.0.1 -u Administrator -p password --bucket=default --bucket-type=membase --bucket-port=11211 --bucket-ramsize=200 --bucket-replica=1
ERROR: unable to bucket-create (400) Bad Request
ERROR: command: bucket-create: 127.0.0.1:8091, 2
[root@ip-10-127-157-49 ~]# /opt/membase/bin/cli/membase bucket-create -c 127.0.0.1 -u Administrator -p password --bucket=default --bucket-type=membase --bucket-port=11212 --bucket-ramsize=200 --bucket-replica=1
SUCCESS: bucket-create

The default bucket however ends up on port 11211.

This is how is should work:
1. --bucket=default --bucket-type=membase --bucket-port=11211 --bucket-ramsize=200 --bucket-replica=1
Success
2. --bucket=default --bucket-type=membase --bucket-ramsize=200 --bucket-replica=1
Success
3. --bucket=default --bucket-type=membase --bucket-port=11212 --bucket-ramsize=200 --bucket-replica=1
Error: default bucket must be on 11211
4. --bucket=default --bucket-type=membase --bucket-port=11211 --bucket-password="password"--bucket-ramsize=200 --bucket-replica=1
Error: default bucket cannot have a password

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Perry Krug added a comment -
A Pivotal Tracker story has been created for this Issue: http://www.pivotaltracker.com/story/show/9309593
Show
Perry Krug added a comment - A Pivotal Tracker story has been created for this Issue: http://www.pivotaltracker.com/story/show/9309593
Hide
Permalink
Aleksey Kondratenko added a comment -
likely CLI a issue
Show
Aleksey Kondratenko added a comment - likely CLI a issue
Hide
Permalink
Mike Wiederhold added a comment -
This is not a cli issue. I have produced it with multiple clients as well as curl. This is a bug in ns server.
Show
Mike Wiederhold added a comment - This is not a cli issue. I have produced it with multiple clients as well as curl. This is a bug in ns server.
Hide
Permalink
Perry Krug added a comment -
Perry Krug deleted the linked story in Pivotal Tracker
Show
Perry Krug added a comment - Perry Krug deleted the linked story in Pivotal Tracker
Hide
Permalink
Perry Krug added a comment -
A Pivotal Tracker story has been created for this Issue: http://www.pivotaltracker.com/story/show/14344671
Show
Perry Krug added a comment - A Pivotal Tracker story has been created for this Issue: http://www.pivotaltracker.com/story/show/14344671
Hide
Permalink
Aleksey Kondratenko added a comment -
My guess is that --bucket-port parameter means that bucket requires per-port moxi (even if port is 11211). We need to verify that and either fix it in CLI or handle in ns_server.
Show
Aleksey Kondratenko added a comment - My guess is that --bucket-port parameter means that bucket requires per-port moxi (even if port is 11211). We need to verify that and either fix it in CLI or handle in ns_server.
Hide
Permalink
Steve Yen added a comment -
Workaroudn thought... I looked through some other test scripts that were creating default buckets on 11211, and noticed that they were not specifying the --bucket-port parameter, so the system must be defaulting to 11211 when --bucket-port is unspecified.

./bin/membase bucket-create -c 127.0.0.1 \
    -u Administrator -p password \
    --bucket=default --bucket-type=membase --bucket-password= \
    --bucket-ramsize=$ram_quota --bucket-replica=$replica_count
Show
Steve Yen added a comment - Workaroudn thought... I looked through some other test scripts that were creating default buckets on 11211, and noticed that they were not specifying the --bucket-port parameter, so the system must be defaulting to 11211 when --bucket-port is unspecified. ./bin/membase bucket-create -c 127.0.0.1 \     -u Administrator -p password \     --bucket=default --bucket-type=membase --bucket-password= \     --bucket-ramsize=$ram_quota --bucket-replica=$replica_count
Hide
Permalink
Perry Krug added a comment -
Thanks Steve...we've got a few workarounds.

This issue is still confusing for customers and considering it doesn't seem like a huge fix, I would request that it get resolved soon.
Show
Perry Krug added a comment - Thanks Steve...we've got a few workarounds. This issue is still confusing for customers and considering it doesn't seem like a huge fix, I would request that it get resolved soon.
Hide
Permalink
Farshid Ghods added a comment -
Steve, is this a cli fix or a ns_server one ?
Show
Farshid Ghods added a comment - Steve, is this a cli fix or a ns_server one ?
Hide
Permalink
Mike Wiederhold added a comment -
This is an ns_server fix. At one point I was going to fix it and from reading the ns_server code verified that this was a bug in ns_server.
Show
Mike Wiederhold added a comment - This is an ns_server fix. At one point I was going to fix it and from reading the ns_server code verified that this was a bug in ns_server.
Hide
Permalink
Aleksey Kondratenko added a comment -
Let me elaborate a bit on what ns_server does.

There are two authentication types (mirrored by radio-buttons on UI). There's password auth type (where password may be empty) and there's auth type of "none", where you need to specify new port for per-port-moxi. So you either pass password and set auth_type to sasl or you pass port and set auth_type to none.

When bucket name is "default" it forcibly makes it of type sasl_auth and empty password. Because any other option for default bucket makes no sense. We can change that, but I don't think it needs changing.

Now on our CLI. When somebody passes --bucket-port (why not just --port, btw) it apparently sends auth_type = none and sends port. When somebody passes --bucket-password it apparently sends auth_type = sasl. That logic is fine, but "default" is essentially separate auth_type. When creating bucket named default it should not accept non-empty password and --bucket-port (or only accept and ignore --bucket-port=11211).
Show
Aleksey Kondratenko added a comment - Let me elaborate a bit on what ns_server does. There are two authentication types (mirrored by radio-buttons on UI). There's password auth type (where password may be empty) and there's auth type of "none", where you need to specify new port for per-port-moxi. So you either pass password and set auth_type to sasl or you pass port and set auth_type to none. When bucket name is "default" it forcibly makes it of type sasl_auth and empty password. Because any other option for default bucket makes no sense. We can change that, but I don't think it needs changing. Now on our CLI. When somebody passes --bucket-port (why not just --port, btw) it apparently sends auth_type = none and sends port. When somebody passes --bucket-password it apparently sends auth_type = sasl. That logic is fine, but "default" is essentially separate auth_type. When creating bucket named default it should not accept non-empty password and --bucket-port (or only accept and ignore --bucket-port=11211).
Hide
Permalink
Aleksey Kondratenko added a comment -
Well we can make requested validations part of ns_server. I just thought it makes more sense in client-side, but maybe I was wrong.
Show
Aleksey Kondratenko added a comment - Well we can make requested validations part of ns_server. I just thought it makes more sense in client-side, but maybe I was wrong.
Hide
Permalink
Farshid Ghods added a comment -
no it makes sense to take care of this in the client side.
the server side logic is very clear for buckets with the name default . we just need to make sure what you described is also documented in the REST doc page.
Show
Farshid Ghods added a comment - no it makes sense to take care of this in the client side. the server side logic is very clear for buckets with the name default . we just need to make sure what you described is also documented in the REST doc page.
Hide
Permalink
Farshid Ghods added a comment -
a7244de Bin Cui, MB-3300 default bucket cannot be created on port 11211
Show
Farshid Ghods added a comment - a7244de Bin Cui, MB-3300 default bucket cannot be created on port 11211

People

  • Assignee:
    Bin Cui
    Reporter:
    Mike Wiederhold
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: