accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-2119) Ensure compactions don't block table deletion
Date Thu, 02 Jan 2014 16:26:51 GMT


Keith Turner commented on ACCUMULO-2119:

I think major compactions will be interrupted in this case.   {{o.a.a.tserver.Compactor.CompactionEnv.isCompactionEnabled()}}
is called during the compaction loop.  Major compactions create a {{CompactionEnv}} object
that checks if the tablet is closing or if major compactions were disabled.  Minor compactions
always return true for isCompactionEnabled(), this could possibly be changed.

> Ensure compactions don't block table deletion
> ---------------------------------------------
>                 Key: ACCUMULO-2119
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>    Affects Versions: 1.5.0
>            Reporter: Josh Elser
>            Priority: Minor
> I was ingesting some data into an Accumulo instance. My TServer's heap was a little small
-- that, combined with a bug in my code that was writing very large keys, caused a minor compaction
to take a very long time.
> I ultimately wanted to just delete the table and re-run my code with the bug fixed, but,
despite the table trying to be deleted, it looked like that table operation was blocked until
the minc finished. It seems plausible that we could interrupt that compaction, delete that
in-memory map, and unload the tablet so we can delete it.
> It would be nice to interrupt the minor compaction when the table is trying to be deleted
so we can actually delete the table. I'm not positive if the same thing happens with a major
compaction, but I would assume so (if you're compacting a large tablet, you could also have
to wait order of 10's of minutes for your deletion to occur).

This message was sent by Atlassian JIRA

View raw message