Couchbase Server

Bucket creation error through REST API

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Incomplete
  • Affects Version/s: 1.8.1
  • Fix Version/s: .next
  • Component/s: RESTful-APIs
  • Security Level: Public
  • Labels:
    None
  • Environment:
    1.8.1-938 Linux

Description

Tried to created a bucket with 3000M quota on a two node cluster thru REST API:

First trial failed with the following return error: ("free" ram showed 0)

ramQuotaMB: 3000, status: False, content: {"errors":{"ramQuotaMB":"RAM quota specified is too large to be provisioned into this cluster."},"summaries":{"ramSummary":{"total":3145728000.0,"otherBuckets":0,"nodesCount":2,"perNodeMegs":3000,"thisAlloc":6291456000.0,"thisUsed":0,"free":-3145728000.0},"hddSummary":{"total":51351605248.0,"otherData":7702740787.0,"otherBuckets":0,"thisUsed":0,"free":43648864461.0}}}, header: {'status': '400', 'content-length': '370', 'server': 'Couchbase Server 1.8.1-938-rel-enterprise', 'pragma': 'no-cache', 'cache-control': 'no-cache', 'date': 'Wed, 12 Sep 2012 17:52:19 GMT', 'content-type': 'application/json'}

Second tried succeeded with the following return msg:

ramQuotaMB: 3000, status: True, content: , header: {'status': '202', 'content-length': '0', 'server': 'Couchbase Server 1.8.1-938-rel-enterprise', 'location': '/pools/default/buckets/default', 'pragma': 'no-cache', 'cache-control': 'no-cache', 'date': 'Wed, 12 Sep 2012 17:52:30 GMT'}



Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Aleksey Kondratenko added a comment -
Sorry for closing this, but I'd need more details. At least diags from that problematic node or reliable way to reproduce.
Show
Aleksey Kondratenko added a comment - Sorry for closing this, but I'd need more details. At least diags from that problematic node or reliable way to reproduce.
Hide
Permalink
Bjoern Martin added a comment -
I had the exact same problem and was wondering why the "ramSummary" was indicating a negative "free" entry. During testing I found out that the default bucket created during installation reserved all remaining free memory (3.8 of 4.0 GB) for itself (200 MB were used by the "beer" example). Deleting that default bucket gave me the breathing room to add more buckets. So if you encounter this problem check whether the sum of max values for the "RAM/Quota Usage" on the "Data Buckets" plus the "ramQuotaMB" you specify times the number of replicas exceeds the total memory within your cluster.
Show
Bjoern Martin added a comment - I had the exact same problem and was wondering why the "ramSummary" was indicating a negative "free" entry. During testing I found out that the default bucket created during installation reserved all remaining free memory (3.8 of 4.0 GB) for itself (200 MB were used by the "beer" example). Deleting that default bucket gave me the breathing room to add more buckets. So if you encounter this problem check whether the sum of max values for the "RAM/Quota Usage" on the "Data Buckets" plus the "ramQuotaMB" you specify times the number of replicas exceeds the total memory within your cluster.
Hide
Permalink
Aleksey Kondratenko added a comment -
Yes, negative ramSummary is used on UI to show how much you're trying to overcommit node quota
Show
Aleksey Kondratenko added a comment - Yes, negative ramSummary is used on UI to show how much you're trying to overcommit node quota

People

  • Assignee:
    Aleksey Kondratenko
    Reporter:
    Ronnie Sun
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: