[ https://issues.apache.org/jira/browse/ACCUMULO-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860309#comment-13860309 ] 

Josh Elser commented on ACCUMULO-2119:
--------------------------------------

That makes sense. This was a bit of a non-standard case as normally MinC's *shouldn't* be taking that long to complete (it seems very plausible that minc interruption was ignored for that reason), but it would certainly be a nice thing to have so you don't have to restart everything to get the deletion to take effect.

> Ensure compactions don't block table deletion
> ---------------------------------------------
>
>                 Key: ACCUMULO-2119
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2119
>             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
(v6.1.5#6160)