I thnk this could be done fairly easily with an iterator. An iterator
configured for major compaction could rate limit data.
On Thu, Feb 28, 2013 at 8:27 AM, Denis de...@camfex.cz wrote:
Hi.
Major compaction loads hard disks very hard, even with
tserver.compaction.major.concurrent.max=1
Can you open a ticket for this? We could post the iterator as a patch
to that ticket. Then people could use that patch.
On Thu, Feb 28, 2013 at 8:27 AM, Denis de...@camfex.cz wrote:
Hi.
Major compaction loads hard disks very hard, even with
tserver.compaction.major.concurrent.max=1
Hi, Keith
Thanks for the hint to use iterator for that.
Although this approach can help in my case, it may be tricky to use it
in other cases, because (as far as I understood), with iterator one
can throttle the uncompressed data and actual throttling of the hard
disk operations would depend on
On Thu, Feb 28, 2013 at 10:03 AM, Denis de...@camfex.cz wrote:
Hi, Keith
Thanks for the hint to use iterator for that.
Although this approach can help in my case, it may be tricky to use it
in other cases, because (as far as I understood), with iterator one
can throttle the uncompressed
