You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by GitBox <gi...@apache.org> on 2019/04/16 14:33:47 UTC

[GitHub] [accumulo] keith-turner commented on issue #1050: Allow multiple tablet merges to occur at once.

keith-turner commented on issue #1050: Allow multiple tablet merges to occur at once.
URL: https://github.com/apache/accumulo/issues/1050#issuecomment-483687565
 
 
   Chop compactions are part of the problem but not all of the problem.   Below are some other behaviors that can make this process slow.
   
    * All tablets in the merge range need to have any in memory data minor compacted and then unloaded.  If tablets are actively being written to that could slow this down a bit.
    * The FATE operation that does merge locks the table.   This prevents two merge operations on different ranges of a table from running concurrently.  
    * The shell command that does size based merges only does one range at a time.
   
   Some possible way to improve this are :
   
    * The merge operation could run chop compaction before starting the merge fate operation OR no-chop merges could be implemented.
    * A range could be added to FATE table locks.  So instead of locking an entire table, a range of a table could be locked OR a merge API that takes a list of ranges could be added.
    * The shell command that does size based merges could submit multiple ranges concurrently.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services