I'm not sure if it's possible. Scheduling a compaction is an entry in the
metadata table. But once it gets triggered, there are then compactions
scheduled locally for the tserver. You might be able to delete the flag and
bounce all the tservers to stop it, but I can't say for certain.
Sent from my phone, please pardon the typos and brevity.
On May 14, 2013 11:48 PM, "Mike Drob" <[EMAIL PROTECTED]> wrote:
> Somebody (totally not me) accidentally kicked off a full table compaction
> using Accumulo 1.4.3.
> There's a large number of them waiting and the queue is decreasing very
> slowly - what are my options for improving the situation. Ideally, I would
> be able to just cancel everything and then come back with a more precise