Hi
I use Hadoop 0.17 and HBase 0.2.0 dev.
i noticed a strange behavior of hbase when i create scanner and call
scanner.iterator().hasNext() - it needs very long time for answer.
It's realy strange ... this happens only for one table. The same test on
other tables gives that very short time is needed for
scanner.iterator().hasNext().
let's see :
Table : index
number of rows : about 65000
scanner from startId and with the PageRowFilter : limit 10
creating HTable : 183 ms
creating filter : 1 ms
creating scanner: 13 ms
Iterator iterator = scanner.iterator() : 0 ms
iterator.hasNext(): 2843 ms
iterator.next(); 1 ms;
for other table : data
Table : index
number of rows : about 65000
scanner from startId and with the PageRowFilter : limit 10
creating HTable : 213 ms
creating filter : 1 ms
creating scanner: 13 ms
Iterator iterator = scanner.iterator() : 1 ms
iterator.hasNext(): 8 ms
iterator.next(); 1 ms;
There is only one difference between table index and data - format of rowId
example rowId for table "data" :
5487987413120499077,4767446346789789789da13dfga-d524-gmlw-354m-hjkjwer42abr
example rowId for table "index" :
ennm,Dvboemepw,userssearch,a,9223372036854775807,9223372036854775807ffffffff-ffff-ffff-ffff-ffffffffffff
Please help me - where is a problem? why is the checking next element so
long - for index table?
is the problem with rowId's format ?
Thanx - Acure