[MB-5684] max number of buckets should be set to a default value but configurable using a RESTful API (max set to 10 by default) Created: 25/Jun/12  Updated: 10/Jan/13  Resolved: 11/Oct/12

Status: Closed
Project: Couchbase Server
Component/s: RESTful-APIs
Affects Version/s: None
Fix Version/s: 2.0
Security Level: Public

Type: Bug Priority: Major
Reporter: Farshid Ghods (Inactive) Assignee: Sriram Melkote
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

placeholder bug to limit max number of "supported" buckets that customer can create in a couchbase cluster

default to be determined based on system testing

Comment by Dipti Borkar [ 11/Oct/12 ]
on gerrit.

We need to change this to 10 buckets not 6.
Comment by Sriram Melkote [ 11/Oct/12 ]
Buckets now limited to 10 by default. Limit is configurable using the max_bucket_count setting.
Comment by Aleksey Kondratenko [ 11/Oct/12 ]
Comment by Dipti Borkar [ 11/Oct/12 ]
thank you !
Comment by kzeller [ 31/Oct/12 ]
Added to RN and REST chapter:

 By default the maximum number of buckets recommended for a Couchbase Cluster is ten. This is a safety mechanism to ensure that a cluster does not have resource and CPU overuse due to too many buckets. This limit is configurable using the REST-API.
 The Couchbase REST-API has changed to enable you to change the default maximum number of buckets used in a Couchbase cluster. The maximum allowed buckets in this request is 128, however the suggested maximum number of buckets is ten per cluster. The following illustrates the endpoint and parameters used:

shell> curl -X -u admin:password -d maxBucketCount=6 http://ip_address:8091/internalSettings

 For this request you need to provide administrative credentials for the cluster. The following HTTP request will be sent:

About to connect() to port 8091 (#0)
Connected to ( port 8091 (#0)
Server auth using Basic with user 'Administrator'
POST /internalSettings HTTP/1.1

 If Couchbase Server successfully changes the bucket limit for the cluster, you will get a HTTP 200 response:

HTTP/1.1 200 OK
Server: Couchbase Server 2.0.0r_501_gb614829
Pragma: no-cache
Date: Wed, 31 Oct 2012 21:21:48 GMT
Content-Type: application/json
Content-Length: 2
Cache-Control: no-cache

 If you provide an invalid number, such as 0, a negative number, or an amount over 128 buckets, you will get this error message:

 ["Unexpected server error, request logged."]
Generated at Tue Oct 21 19:45:22 CDT 2014 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.