There is a bug in scanners currently that will be addressed in HBASE-538 which in some circumstances the scanner is not closed and advanced properly. This may be the problem you are seeing. Is the table with the long hasNext time contained in a single region?
--- Jim Kellerman, Senior Engineer; Powerset > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 13, 2008 11:44 PM > To: [email protected] > Subject: Re: long time scanner.iterator().hasNext() > > > > Any chance of your figuring where the time is being spent? Do you > > have the facility to add dumb logging, recompile, restart > cluster, and then > > check? If you want me to send you a patch to get you > going, just say so. > > i have some hypothesis, but it's only my speculation : > > i think that, when i call scanner.iterator().hasNext() it > has to check all rows in the table to find (or not) next > rowId (because hasnext time rise in line correlation with a > table size). Maby problem is in sorting rowId in the table? > > i will try to change rowId format. > > i try checkout latest version of hbase and try to check > the same case today. > > Acure. > > > No virus found in this incoming message. > Checked by AVG. > Version: 7.5.524 / Virus Database: 269.23.16/1432 - Release > Date: 5/14/2008 7:49 AM > > No virus found in this outgoing message. Checked by AVG. Version: 7.5.524 / Virus Database: 269.23.16/1432 - Release Date: 5/14/2008 7:49 AM
