Details
-
Bug
-
Resolution: Fixed
-
Major
-
Cheshire-Cat
-
Centos 7 64 bit; CB EE 7.0.0-5247
-
Untriaged
-
Centos 64-bit
-
-
1
-
No
Description
A simple way perhaps to verify this:
1. Create a 2 node cluster - .215(kv) and .217(index)
2. Create a bucket 'testBucket'
3. Create a collection 'pre-qf'
4. Check the manifest
curl -v -u Administrator:password http://172.23.105.215:8091/pools/default/buckets/testBucket/scopes
|
gives
{"uid":"1","scopes":[{"name":"_default","uid":"0","collections":[{"name":"pre-qf","uid":"8","maxTTL":0},{"name":"_default","uid":"0","maxTTL":0}]}]}
|
5. Stop server on .217 and fail it over unsafely
6. On resulting .215 node create a collection 'post-qf'
7. check the manifest
{"uid":"2","scopes":[{"name":"_default","uid":"0","collections":[{"name":"post-qf","uid":"9","maxTTL":0},{"name":"pre-qf","uid":"8","maxTTL":0},{"name":"_default","uid":"0","maxTTL":0}]}]}
|
So UID got only monotonically increased.
If you were to repeat the same with KV service on .217, then step 7 would yeild
{"uid":"1002","scopes":[{"name":"_default","uid":"0","collections":[{"name":"post-qf","uid":"1009","maxTTL":0},{"name":"pre-qf","uid":"8","maxTTL":0},{"name":"_default","uid":"0","maxTTL":0}]}]}
|
here the UID got bumped by 0x1000 as expected.