I can't find this in the docs, but IIRC the merge command can take a start/end range for what to merge. So the best option might be to try it on a smaller slice and see what happens. At a guess, queries won't block but indexing will.
Mike On Mon, Jan 16, 2017 at 5:23 PM, Dickson, Matt MR < [email protected]> wrote: > *UNOFFICIAL* > That looks like a great option. Before using it, whats the cost/impact > of running this on a massive table in a system with other large bulk > ingests/queries running? In the past when I have used that (which was in > 2013 so things may have changed) all ingests were blocked and it took days > to complete. > > With 1.07T tablets to work on this may take some time? > > > ------------------------------ > *From:* Mike Drob [mailto:[email protected]] > *Sent:* Tuesday, 17 January 2017 09:37 > *To:* [email protected] > *Subject:* Re: Merging smaller/empty tablets [SEC=UNOFFICIAL] > > http://accumulo.apache.org/1.8/accumulo_user_manual.html#_merging_tablets > > In order to merge small tablets, you can ask Accumulo to merge sections of > a table smaller than a given size. > > root@myinstance> merge -t myTable -s 100M > > > > On Mon, Jan 16, 2017 at 4:31 PM, Dickson, Matt MR < > [email protected]> wrote: > >> *UNOFFICIAL* >> I have a table that has evolved to have 1.07T tablets and I fairly >> confident a large portion of these are now empty or very small. I'd like >> to merge smaller tablets and delete empty tablets, is there a smart way to >> do this? >> >> My thought was to query the metadata table for all tablets under a >> certain size for the table and then merge these tablets. >> >> Is the first number in thevalue the size of the tablet, ie >> >> > scan -b 1xk -e 1xk\xff -c file >> 1xk;34234 file:hdfs//name/accumulo/tables/1xk/t-er23423/M423432.rf [] >> *213134*,234234 >> >> Also, are there any side effects of this that I need to be aware of when >> doing this on a massive table? >> >> Thanks in advance, >> Matt >> > >
