gzochi - Tasks: task #14004, Remove lmdb and hdb storage engines
You are not allowed to post comments on this tracker with your current authentication level.
task #14004: Remove lmdb and hdb storage engines
Submitter: | Julian Graham <juliang> | ||
Submitted: | Tue 24 May 2016 03:20:18 AM UTC | ||
Should Start On: | Mon 23 May 2016 04:00:00 AM UTC | Should be Finished on: | Mon 23 May 2016 04:00:00 AM UTC |
Category: | None | Priority: | 5 - Normal |
Status: | Done | Privacy: | Public |
Assigned to: | juliang | Percent Complete: | 100% |
Open/Closed: | Closed | Effort: | 0.00 |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2016-05-30 | juliang | Status | None | Done | |
Percent Complete | 0% | 100% | |||
Open/Closed | Open | Closed |
Powered by Savane 3.13-d3ae.
Corresponding source code
They are, unfortunately, not suitable for use in gzochid, on account of their locking and concurrency models:
LMDB: "Writes are fully serialized; only one write transaction may be active at a time, which guarantees that writers can never deadlock."
HDB: "upscaledb is thread-safe and can be used from multiple threads without problems. However, it is not yet concurrent; it uses a big lock to make sure that only one thread can access the upscaledb environment at a time."