Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 2.0-beta-2
-
Fix Version/s: .next
-
Component/s: ns_server, RESTful-APIs
-
Security Level: Public
-
Labels:None
Description
2.0.0-1751-rel
http://qa.hq.northscale.net/job/centos-64-2.0-view-query-extended-tests/70/consoleFull
notice, that bug was filled before:MB-6710: Deleting bucket on a cluster gives error "Some nodes are still deleting bucket"
2012-09-22 17:36:57,643] - [rest_client:96] INFO - existing buckets : []
[2012-09-22 17:36:57,650] - [rest_client:1234] INFO - http://10.2.2.60:8091/pools/default/buckets with param: proxyPort=11211&bucketType=membase&authType=sasl&replicaIndex=1&name=default&saslPassword=&replicaNumber=1&ramQuotaMB=1456
[2012-09-22 17:36:57,658] - [rest_client:582] ERROR - http://10.2.2.60:8091/pools/default/buckets error 503 reason: unknown {"_":"Bucket with given name still exists"}
test was reproduced manually:
andrei ~/repository/testrunner $ curl --user Administrator:password http://10.2.2.60:8091/pools/default/buckets
[]
andrei ~/repository/testrunner $ curlX POST -d "proxyPort=11211&bucketType=membase&authType=sasl&replicaIndex=1&name=default&saslPassword=&replicaNumber=1&ramQuotaMB=1456" --user Administrator:password http://10.2.2.60:8091/pools/default/buckets
{"_":"Bucket with given name still exists"}
I see the same issue with growing vBucket size as inMB-6711, but new bug is related to that API pools/default/buckets/ doesn't correspond to real situation
[root@localhost default]# ls -la
total 5535344
drwxr-xr-x 2 couchbase couchbase 36864 Sep 22 16:09 .
drwxr-xr-x 6 couchbase couchbase 4096 Sep 22 18:42 ..
-rw-r--r-- 1 couchbase couchbase 122971 Sep 22 16:05 0.couch.2
-rw-r--r-- 1 couchbase couchbase 118875 Sep 22 16:09 1000.couch.2
-rw-r--r-- 1 couchbase couchbase 114779 Sep 22 16:09 1001.couch.2
....
-rw-r--r-- 1 couchbase couchbase 5536133166 Sep 23 04:11 33.couch.
..........
http://qa.hq.northscale.net/job/centos-64-2.0-view-query-extended-tests/70/consoleFull
notice, that bug was filled before:
2012-09-22 17:36:57,643] - [rest_client:96] INFO - existing buckets : []
[2012-09-22 17:36:57,650] - [rest_client:1234] INFO - http://10.2.2.60:8091/pools/default/buckets with param: proxyPort=11211&bucketType=membase&authType=sasl&replicaIndex=1&name=default&saslPassword=&replicaNumber=1&ramQuotaMB=1456
[2012-09-22 17:36:57,658] - [rest_client:582] ERROR - http://10.2.2.60:8091/pools/default/buckets error 503 reason: unknown {"_":"Bucket with given name still exists"}
test was reproduced manually:
andrei ~/repository/testrunner $ curl --user Administrator:password http://10.2.2.60:8091/pools/default/buckets
[]
andrei ~/repository/testrunner $ curlX POST -d "proxyPort=11211&bucketType=membase&authType=sasl&replicaIndex=1&name=default&saslPassword=&replicaNumber=1&ramQuotaMB=1456" --user Administrator:password http://10.2.2.60:8091/pools/default/buckets
{"_":"Bucket with given name still exists"}
I see the same issue with growing vBucket size as in
[root@localhost default]# ls -la
total 5535344
drwxr-xr-x 2 couchbase couchbase 36864 Sep 22 16:09 .
drwxr-xr-x 6 couchbase couchbase 4096 Sep 22 18:42 ..
-rw-r--r-- 1 couchbase couchbase 122971 Sep 22 16:05 0.couch.2
-rw-r--r-- 1 couchbase couchbase 118875 Sep 22 16:09 1000.couch.2
-rw-r--r-- 1 couchbase couchbase 114779 Sep 22 16:09 1001.couch.2
....
-rw-r--r-- 1 couchbase couchbase 5536133166 Sep 23 04:11 33.couch.
..........