c9042db619
Summary: Range Locking supports Lock Escalation. Lock Escalation is invoked when lock memory is nearly exhausted and it reduced the amount of memory used by joining adjacent locks. Bridging the gap between certain locks has adverse effects. For example, in MyRocks it is not a good idea to bridge the gap between locks in different indexes, as that get the lock to cover large portions of indexes, or even entire indexes. Resolve this by introducing Escalation Barrier. The escalation process will call the user-provided barrier callback function: bool(const Endpoint& a, const Endpoint& b) If the function returns true, there's a barrier between a and b and Lock Escalation will not try to bridge the gap between a and b. Pull Request resolved: https://github.com/facebook/rocksdb/pull/9290 Reviewed By: akankshamahajan15 Differential Revision: D33486753 Pulled By: riversand963 fbshipit-source-id: f97910b67aba0579ea1d35f523ca6863d3dd018e |
||
|---|---|---|
| .. | ||
| ft | ||
| locktree | ||
| portability | ||
| util | ||
| COPYING.AGPLv3 | ||
| COPYING.APACHEv2 | ||
| COPYING.GPLv2 | ||
| db.h | ||
| README | ||
| standalone_port.cc | ||
The files in this directory originally come from https://github.com/percona/PerconaFT/. This directory only includes the "locktree" part of PerconaFT, and its dependencies. The following modifications were made: - Make locktree usable outside of PerconaFT library - Add shared read-only lock support The files named *_subst.* are substitutes of the PerconaFT's files, they contain replacements of PerconaFT's functionality.