Details
-
Bug
-
Resolution: Fixed
-
Minor
-
4.6.0
-
None
-
Triaged
-
No
Description
While modifying the existing setWithMeta tests to support the new format described here I ran a test case which:
- single node cluster
- create a bucket with timestamp conflict resolution
- sets a key
- gets the meta data for that key - the CAS is 48 bits of timestamp and 16 bits logical counter with is 0
- increment the CAS by 1
- call setWithMeta with extras as 4 byte options, 4 byte flags, 4 bytes expiration, 8 bytes req seq no of 123, and 8 bytes of the CAS
- the command is rejected with invalid arguments - Wireshark capture is attached
The test runner command is:
./testrunner -i one-node.ini -t epengine.opschangecas.OpsChangeCasTests.test_cas_setMeta_lower
|
I will reassign this to Jim one I check in the needed test runner changes.
Attachments
For Gerrit Dashboard: MB-21891 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
70676,3 | MB-21891: Move options to correct offset | master | ep-engine | Status: MERGED | +2 | +1 |