Yup that's exactly what my hunch was. You can try configuring a locality group for your "slow" column families, compact the table and then rerun your scans. They should be fast after you do this. On Oct 5, 2015 11:25 AM, "z11373" <[email protected]> wrote:
> Hi Josh, > I see there are 4 tablet files for that table, and all of them are in range > from 730MB to 860MB in size. > For those column families that have problem, they are in 2 of those 4 > tablets. > They are only a few rows, but for those column families which have no > problem, they have millions of rows. > This makes me thinking if the slowness because it has to find those 'few' > rows among those 'gigantic' rows in that physical tablet file? > > Thanks, > Z > > > > -- > View this message in context: > http://apache-accumulo.1065345.n5.nabble.com/scan-command-hung-tp15286p15320.html > Sent from the Developers mailing list archive at Nabble.com. >
