Details
-
Task
-
Resolution: Fixed
-
Major
-
None
Description
The ability to trace the operations on a file will provide a easy way to get a snapshot of changes to the file. This will help with debugging problems which show up after some operation has already occured.
For example if a file corruption is detected when inserting or reading a document, the trace will help determine the operation that touched that part of the file.
We can have a circular buffer which contains the trace of the last N operations and provide an API to dump the trace file. When the upper layer encounters an error, the API can be used to get a trace file.
Attachments
For Gerrit Dashboard: MB-32341 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
104471,4 | MB-32341: Couchstore-Trace operations on a file | spock | kv_engine | Status: ABANDONED | -1 | -1 |
104472,15 | MB-32341: Couchstore-Trace operations on a file | spock | couchstore | Status: ABANDONED | +2 | +1 |
105369,1 | MB-32341: Couchstore-Trace operations on a file | spock | kv_engine | Status: ABANDONED | 0 | -1 |
106418,3 | MB-33400: Special build | 5.1.1-sb1 | couchstore | Status: MERGED | +2 | +1 |
106419,2 | MB-33400: Special build | 5.1.1-sb1 | kv_engine | Status: MERGED | +2 | +1 |
113456,2 | MB-32341: Temporarily lock couchstore in Alice | master | manifest | Status: MERGED | +2 | +1 |
114031,2 | MB-32341: Couchstore-Trace operations on a file | alice | kv_engine | Status: ABANDONED | -2 | -1 |