commit | b5b801abc02f820ad4a6ada202270015eafc1ba9 | [log] [tgz] |
---|---|---|
author | ILYA Khlopotov <iilyak@apache.org> | Fri Feb 15 13:01:22 2019 +0000 |
committer | ILYA Khlopotov <iilyak@apache.org> | Mon Feb 18 19:23:02 2019 +0000 |
tree | 1ce63e82ea894a9ffabbee9fd16c559f0ac9722e | |
parent | aa88b1ea824f6ea41d1754a43d317477d39a25ac [diff] |
Reconfigure IOQ on config update
The following are the list of IOQ classes:
One can configure an ioq bypass, which removes an IO class from prioritization, as below:
config:set("ioq.bypass", "view_update", "true")
Note that setting an IOQ bypass can effectively trump all other classes, especially in the case of an interactive bypass v. compaction. This can lead to high disk usage.
The priority for a class can also be set ala:
config:set("ioq", "compaction", "0.3")
Or globally, using snippet/rpc:
s:set_config("ioq", "compaction", "0.314", global) rpc:multicall(config, set, ["ioq", "compaction", "0.217"])
As the interactive class is ‘everything else’ its priority cannot be directly set.