Index maintenance will always be slower. An interesting comparison would be to also update your indexes from the M/R and see whether that performs better.
________________________________ From: Prakash Kadel <[email protected]> To: "[email protected]" <[email protected]> Sent: Sunday, February 17, 2013 5:13 PM Subject: Re: coprocessor enabled put very slow, help please~~~ thank you lars, That is my guess too. I am confused, isnt that something that cannot be controlled. Is this approach of creating some kind of index wrong? Sincerely, Prakash Kadel On Feb 18, 2013, at 10:07 AM, lars hofhansl <[email protected]> wrote: > Presumably the coprocessor issues Puts to another region server in most > cases, that could explain it being (much) slower. > > > > ________________________________ > From: Prakash Kadel <[email protected]> > To: "[email protected]" <[email protected]> > Sent: Sunday, February 17, 2013 4:52 PM > Subject: Re: coprocessor enabled put very slow, help please~~~ > > Forgot to mention. I am using 0.92. > > Sincerely, > Prakash > > On Feb 18, 2013, at 9:48 AM, Prakash Kadel <[email protected]> wrote: > >> hi, >> i am trying to insert few million documents to hbase with mapreduce. To >>enable quick search of docs i want to have some indexes, so i tried to use >>the coprocessors, but they are slowing down my inserts. Arent the >>coprocessors not supposed to increase the latency? >> my settings: >> 3 region servers >> 60 maps >> each map inserts to doc table.(checkAndPut) >> regionobserver coprocessor does a postCheckAndPut and inserts some rows to a >> index table. >> >> >> Sincerely, >> Prakash
