You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by Venkatesh <vr...@aol.com> on 2011/04/20 15:03:43 UTC
java.lang.IndexOutOfBoundsException
Using hbase-0.90.2..(sigh..) Any tip? thanks
java.lang.IndexOutOfBoundsException: Index: 4, Size: 3
at java.util.ArrayList.RangeCheck(ArrayList.java:547)
at java.util.ArrayList.remove(ArrayList.java:387)
at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchOfPuts(HConnectionManager.java:1257)
at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:822)
at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:678)
at org.apache.hadoop.hbase.client.HTable.put(HTable.java:663)
Re: java.lang.IndexOutOfBoundsException
Posted by Jean-Daniel Cryans <jd...@apache.org>.
Are you sharing a single HTable between multiple threads that do puts?
J-D
On Wed, Apr 20, 2011 at 6:03 AM, Venkatesh <vr...@aol.com> wrote:
>
> Using hbase-0.90.2..(sigh..) Any tip? thanks
>
>
> java.lang.IndexOutOfBoundsException: Index: 4, Size: 3
> at java.util.ArrayList.RangeCheck(ArrayList.java:547)
> at java.util.ArrayList.remove(ArrayList.java:387)
> at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchOfPuts(HConnectionManager.java:1257)
> at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:822)
> at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:678)
> at org.apache.hadoop.hbase.client.HTable.put(HTable.java:663)
>
>
>
>
Re: java.lang.IndexOutOfBoundsException
Posted by Venkatesh <vr...@aol.com>.
Thanks..we have the same exact code that process 700 million puts per day in 0.20.6
from a tomcat servlet (each thread creates new HTable, does 1 put & closes)
..in 0.90.2..we changed just the API whose signature changed (mainly HTable)..it crawls
..each/most requests taking well over 2 sec..we can't keep up with even 1/10 th of
production load.
everything in the cluster is identical 20 node cluster..
That is impressive performance..from async..Thanks for the tip..i'll give it a try (assuming
it would work with 0.90.2)
-----Original Message-----
From: tsuna <ts...@gmail.com>
To: user@hbase.apache.org
Sent: Wed, Apr 20, 2011 4:30 pm
Subject: Re: java.lang.IndexOutOfBoundsException
On Wed, Apr 20, 2011 at 10:04 AM, Venkatesh <vr...@aol.com> wrote:
> On 0.90.2, do you all think using HTablePool would help with performance
problem?
What performance problems are you seeing?
BTW, if you want a thread-safe client that's highly scalable for
high-throughput, multi-threaded applications, look at asynchbase:
http://github.com/stumbleupon/asynchbase
OpenTSDB uses it and I'm able to push 200000 edits per second to 3
RegionServers.
--
Benoit "tsuna" Sigoure
Software Engineer @ www.StumbleUpon.com
Re: java.lang.IndexOutOfBoundsException
Posted by tsuna <ts...@gmail.com>.
On Wed, Apr 20, 2011 at 10:04 AM, Venkatesh <vr...@aol.com> wrote:
> On 0.90.2, do you all think using HTablePool would help with performance problem?
What performance problems are you seeing?
BTW, if you want a thread-safe client that's highly scalable for
high-throughput, multi-threaded applications, look at asynchbase:
http://github.com/stumbleupon/asynchbase
OpenTSDB uses it and I'm able to push 200000 edits per second to 3
RegionServers.
--
Benoit "tsuna" Sigoure
Software Engineer @ www.StumbleUpon.com
Re: java.lang.IndexOutOfBoundsException
Posted by Venkatesh <vr...@aol.com>.
sorry..yeah..that's dumb of me..clearly i'm not thinking anything..just frustrated with upgrade
thx
-----Original Message-----
From: Ted Yu <yu...@gmail.com>
To: user@hbase.apache.org
Sent: Wed, Apr 20, 2011 1:24 pm
Subject: Re: java.lang.IndexOutOfBoundsException
I meant specifying Integer.MAX_VALUE as maxSize along with config.
On Wed, Apr 20, 2011 at 10:17 AM, Venkatesh <vr...@aol.com> wrote:
> If I use default ..i can't share/pass my HBaseConfiguration object..atleast
> i don't see a constructor/setter..
> that would go against previous suggestion
>
>
>
>
>
>
>
>
>
>
> -----Original Message-----
> From: Ted Yu <yu...@gmail.com>
> To: user@hbase.apache.org
> Sent: Wed, Apr 20, 2011 1:08 pm
> Subject: Re: java.lang.IndexOutOfBoundsException
>
>
> When using HTablePool, try not to define maxSize yourself - use the
> default.
>
>
>
> On Wed, Apr 20, 2011 at 10:04 AM, Venkatesh <vr...@aol.com> wrote:
>
>
>
> >
>
> > Yeah you & J-D both hit it..
>
> > I knew it's bad..I was trying anything & everything to solve the
> incredibly
>
> > long latency
>
> > with hbase puts on 0.90.2..
>
> > I get ok/better response with batch put..& this was quick & dirty way to
>
> > accumulate puts by sharing
>
> > same HTable instance
>
> > Thanks for letting me know..this exception is due to sharing of HTable..
>
> >
>
> > I've to go back to to 0.20.6 since our system is down too long..(starting
>
> > with empty table)
>
> >
>
> > On 0.90.2, do you all think using HTablePool would help with performance
>
> > problem?
>
> > thx
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > -----Original Message-----
>
> > From: Ted Yu <yu...@gmail.com>
>
> > To: user@hbase.apache.org
>
> > Sent: Wed, Apr 20, 2011 12:27 pm
>
> > Subject: Re: java.lang.IndexOutOfBoundsException
>
> >
>
> >
>
> > I think HConnectionManager can catch IndexOutOfBoundsException and
>
> > translate
>
> >
>
> > into a more user-friendly message, informing user about thread-safety.
>
> >
>
> >
>
> >
>
> > On Wed, Apr 20, 2011 at 9:11 AM, Ted Yu <yu...@gmail.com> wrote:
>
> >
>
> >
>
> >
>
> > > I have seen this before.
>
> >
>
> > > HTable isn't thread-safe.
>
> >
>
> > >
>
> >
>
> > > Please describe your usage.
>
> >
>
> > >
>
> >
>
> > > Thanks
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > On Wed, Apr 20, 2011 at 6:03 AM, Venkatesh <vr...@aol.com>
>
> > wrote:
>
> >
>
> > >
>
> >
>
> > >>
>
> >
>
> > >> Using hbase-0.90.2..(sigh..) Any tip? thanks
>
> >
>
> > >>
>
> >
>
> > >>
>
> >
>
> > >> java.lang.IndexOutOfBoundsException: Index: 4, Size: 3
>
> >
>
> > >> at java.util.ArrayList.RangeCheck(ArrayList.java:547)
>
> >
>
> > >> at java.util.ArrayList.remove(ArrayList.java:387)
>
> >
>
> > >> at
>
> >
>
> > >>
>
> >
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchOfPuts(HConnectionManager.java:1257)
>
> >
>
> > >> at
>
> > org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:822)
>
> >
>
> > >> at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:678)
>
> >
>
> > >> at org.apache.hadoop.hbase.client.HTable.put(HTable.java:663)
>
> >
>
> > >>
>
> >
>
> > >>
>
> >
>
> > >>
>
> >
>
> > >>
>
> >
>
> > >
>
> >
>
> >
>
> >
>
> >
>
>
>
>
Re: java.lang.IndexOutOfBoundsException
Posted by Ted Yu <yu...@gmail.com>.
I meant specifying Integer.MAX_VALUE as maxSize along with config.
On Wed, Apr 20, 2011 at 10:17 AM, Venkatesh <vr...@aol.com> wrote:
> If I use default ..i can't share/pass my HBaseConfiguration object..atleast
> i don't see a constructor/setter..
> that would go against previous suggestion
>
>
>
>
>
>
>
>
>
>
> -----Original Message-----
> From: Ted Yu <yu...@gmail.com>
> To: user@hbase.apache.org
> Sent: Wed, Apr 20, 2011 1:08 pm
> Subject: Re: java.lang.IndexOutOfBoundsException
>
>
> When using HTablePool, try not to define maxSize yourself - use the
> default.
>
>
>
> On Wed, Apr 20, 2011 at 10:04 AM, Venkatesh <vr...@aol.com> wrote:
>
>
>
> >
>
> > Yeah you & J-D both hit it..
>
> > I knew it's bad..I was trying anything & everything to solve the
> incredibly
>
> > long latency
>
> > with hbase puts on 0.90.2..
>
> > I get ok/better response with batch put..& this was quick & dirty way to
>
> > accumulate puts by sharing
>
> > same HTable instance
>
> > Thanks for letting me know..this exception is due to sharing of HTable..
>
> >
>
> > I've to go back to to 0.20.6 since our system is down too long..(starting
>
> > with empty table)
>
> >
>
> > On 0.90.2, do you all think using HTablePool would help with performance
>
> > problem?
>
> > thx
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > -----Original Message-----
>
> > From: Ted Yu <yu...@gmail.com>
>
> > To: user@hbase.apache.org
>
> > Sent: Wed, Apr 20, 2011 12:27 pm
>
> > Subject: Re: java.lang.IndexOutOfBoundsException
>
> >
>
> >
>
> > I think HConnectionManager can catch IndexOutOfBoundsException and
>
> > translate
>
> >
>
> > into a more user-friendly message, informing user about thread-safety.
>
> >
>
> >
>
> >
>
> > On Wed, Apr 20, 2011 at 9:11 AM, Ted Yu <yu...@gmail.com> wrote:
>
> >
>
> >
>
> >
>
> > > I have seen this before.
>
> >
>
> > > HTable isn't thread-safe.
>
> >
>
> > >
>
> >
>
> > > Please describe your usage.
>
> >
>
> > >
>
> >
>
> > > Thanks
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > On Wed, Apr 20, 2011 at 6:03 AM, Venkatesh <vr...@aol.com>
>
> > wrote:
>
> >
>
> > >
>
> >
>
> > >>
>
> >
>
> > >> Using hbase-0.90.2..(sigh..) Any tip? thanks
>
> >
>
> > >>
>
> >
>
> > >>
>
> >
>
> > >> java.lang.IndexOutOfBoundsException: Index: 4, Size: 3
>
> >
>
> > >> at java.util.ArrayList.RangeCheck(ArrayList.java:547)
>
> >
>
> > >> at java.util.ArrayList.remove(ArrayList.java:387)
>
> >
>
> > >> at
>
> >
>
> > >>
>
> >
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchOfPuts(HConnectionManager.java:1257)
>
> >
>
> > >> at
>
> > org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:822)
>
> >
>
> > >> at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:678)
>
> >
>
> > >> at org.apache.hadoop.hbase.client.HTable.put(HTable.java:663)
>
> >
>
> > >>
>
> >
>
> > >>
>
> >
>
> > >>
>
> >
>
> > >>
>
> >
>
> > >
>
> >
>
> >
>
> >
>
> >
>
>
>
>
Re: java.lang.IndexOutOfBoundsException
Posted by Venkatesh <vr...@aol.com>.
If I use default ..i can't share/pass my HBaseConfiguration object..atleast i don't see a constructor/setter..
that would go against previous suggestion
-----Original Message-----
From: Ted Yu <yu...@gmail.com>
To: user@hbase.apache.org
Sent: Wed, Apr 20, 2011 1:08 pm
Subject: Re: java.lang.IndexOutOfBoundsException
When using HTablePool, try not to define maxSize yourself - use the default.
On Wed, Apr 20, 2011 at 10:04 AM, Venkatesh <vr...@aol.com> wrote:
>
> Yeah you & J-D both hit it..
> I knew it's bad..I was trying anything & everything to solve the incredibly
> long latency
> with hbase puts on 0.90.2..
> I get ok/better response with batch put..& this was quick & dirty way to
> accumulate puts by sharing
> same HTable instance
> Thanks for letting me know..this exception is due to sharing of HTable..
>
> I've to go back to to 0.20.6 since our system is down too long..(starting
> with empty table)
>
> On 0.90.2, do you all think using HTablePool would help with performance
> problem?
> thx
>
>
>
>
>
>
>
>
> -----Original Message-----
> From: Ted Yu <yu...@gmail.com>
> To: user@hbase.apache.org
> Sent: Wed, Apr 20, 2011 12:27 pm
> Subject: Re: java.lang.IndexOutOfBoundsException
>
>
> I think HConnectionManager can catch IndexOutOfBoundsException and
> translate
>
> into a more user-friendly message, informing user about thread-safety.
>
>
>
> On Wed, Apr 20, 2011 at 9:11 AM, Ted Yu <yu...@gmail.com> wrote:
>
>
>
> > I have seen this before.
>
> > HTable isn't thread-safe.
>
> >
>
> > Please describe your usage.
>
> >
>
> > Thanks
>
> >
>
> >
>
> > On Wed, Apr 20, 2011 at 6:03 AM, Venkatesh <vr...@aol.com>
> wrote:
>
> >
>
> >>
>
> >> Using hbase-0.90.2..(sigh..) Any tip? thanks
>
> >>
>
> >>
>
> >> java.lang.IndexOutOfBoundsException: Index: 4, Size: 3
>
> >> at java.util.ArrayList.RangeCheck(ArrayList.java:547)
>
> >> at java.util.ArrayList.remove(ArrayList.java:387)
>
> >> at
>
> >>
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchOfPuts(HConnectionManager.java:1257)
>
> >> at
> org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:822)
>
> >> at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:678)
>
> >> at org.apache.hadoop.hbase.client.HTable.put(HTable.java:663)
>
> >>
>
> >>
>
> >>
>
> >>
>
> >
>
>
>
>
Re: java.lang.IndexOutOfBoundsException
Posted by Ted Yu <yu...@gmail.com>.
When using HTablePool, try not to define maxSize yourself - use the default.
On Wed, Apr 20, 2011 at 10:04 AM, Venkatesh <vr...@aol.com> wrote:
>
> Yeah you & J-D both hit it..
> I knew it's bad..I was trying anything & everything to solve the incredibly
> long latency
> with hbase puts on 0.90.2..
> I get ok/better response with batch put..& this was quick & dirty way to
> accumulate puts by sharing
> same HTable instance
> Thanks for letting me know..this exception is due to sharing of HTable..
>
> I've to go back to to 0.20.6 since our system is down too long..(starting
> with empty table)
>
> On 0.90.2, do you all think using HTablePool would help with performance
> problem?
> thx
>
>
>
>
>
>
>
>
> -----Original Message-----
> From: Ted Yu <yu...@gmail.com>
> To: user@hbase.apache.org
> Sent: Wed, Apr 20, 2011 12:27 pm
> Subject: Re: java.lang.IndexOutOfBoundsException
>
>
> I think HConnectionManager can catch IndexOutOfBoundsException and
> translate
>
> into a more user-friendly message, informing user about thread-safety.
>
>
>
> On Wed, Apr 20, 2011 at 9:11 AM, Ted Yu <yu...@gmail.com> wrote:
>
>
>
> > I have seen this before.
>
> > HTable isn't thread-safe.
>
> >
>
> > Please describe your usage.
>
> >
>
> > Thanks
>
> >
>
> >
>
> > On Wed, Apr 20, 2011 at 6:03 AM, Venkatesh <vr...@aol.com>
> wrote:
>
> >
>
> >>
>
> >> Using hbase-0.90.2..(sigh..) Any tip? thanks
>
> >>
>
> >>
>
> >> java.lang.IndexOutOfBoundsException: Index: 4, Size: 3
>
> >> at java.util.ArrayList.RangeCheck(ArrayList.java:547)
>
> >> at java.util.ArrayList.remove(ArrayList.java:387)
>
> >> at
>
> >>
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchOfPuts(HConnectionManager.java:1257)
>
> >> at
> org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:822)
>
> >> at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:678)
>
> >> at org.apache.hadoop.hbase.client.HTable.put(HTable.java:663)
>
> >>
>
> >>
>
> >>
>
> >>
>
> >
>
>
>
>
RE: HTable not thread safe
Posted by Peter Haidinyak <ph...@local.com>.
Thanks, I'll do that. I need to redesign my client to be multi-threaded so it's a good time to look at it.
-Pete
-----Original Message-----
From: tsuna [mailto:tsunanet@gmail.com]
Sent: Wednesday, April 20, 2011 1:28 PM
To: user@hbase.apache.org
Subject: Re: HTable not thread safe
On Wed, Apr 20, 2011 at 10:12 AM, Peter Haidinyak <ph...@local.com> wrote:
> Sorry, my bad, I assumed each thread would have its own Table instance not using a shared instance.
Yeah you'd need to use one HTable instance per thread.
<plug>Alternatively, you can look at asynchbase, an alternative HBase
client that's fully asynchronous and non-blocking and written from the
ground-up to be thread safe. It performs much better than HTable for
high-throughput low-latency multi-threaded applications:
github.com/stumbleupon/asynchbase </plug>
--
Benoit "tsuna" Sigoure
Software Engineer @ www.StumbleUpon.com
Re: HTable not thread safe
Posted by tsuna <ts...@gmail.com>.
On Wed, Apr 20, 2011 at 10:12 AM, Peter Haidinyak <ph...@local.com> wrote:
> Sorry, my bad, I assumed each thread would have its own Table instance not using a shared instance.
Yeah you'd need to use one HTable instance per thread.
<plug>Alternatively, you can look at asynchbase, an alternative HBase
client that's fully asynchronous and non-blocking and written from the
ground-up to be thread safe. It performs much better than HTable for
high-throughput low-latency multi-threaded applications:
github.com/stumbleupon/asynchbase </plug>
--
Benoit "tsuna" Sigoure
Software Engineer @ www.StumbleUpon.com
RE: HTable not thread safe
Posted by Peter Haidinyak <ph...@local.com>.
Sorry, my bad, I assumed each thread would have its own Table instance not using a shared instance.
Thanks
-Pete
-----Original Message-----
From: Ted Yu [mailto:yuzhihong@gmail.com]
Sent: Wednesday, April 20, 2011 10:10 AM
To: user@hbase.apache.org
Subject: Re: HTable not thread safe
Each thread should maintain its own HTable instance.
On Wed, Apr 20, 2011 at 10:08 AM, Peter Haidinyak <ph...@local.com>wrote:
> If the HTable is not thread safe how would one use multiple threads to
> read/write to a table?
>
> Thanks
>
> -Pete
>
Re: HTable not thread safe
Posted by Ted Yu <yu...@gmail.com>.
Each thread should maintain its own HTable instance.
On Wed, Apr 20, 2011 at 10:08 AM, Peter Haidinyak <ph...@local.com>wrote:
> If the HTable is not thread safe how would one use multiple threads to
> read/write to a table?
>
> Thanks
>
> -Pete
>
HTable not thread safe
Posted by Peter Haidinyak <ph...@local.com>.
If the HTable is not thread safe how would one use multiple threads to read/write to a table?
Thanks
-Pete
Re: java.lang.IndexOutOfBoundsException
Posted by Venkatesh <vr...@aol.com>.
Yeah you & J-D both hit it..
I knew it's bad..I was trying anything & everything to solve the incredibly long latency
with hbase puts on 0.90.2..
I get ok/better response with batch put..& this was quick & dirty way to accumulate puts by sharing
same HTable instance
Thanks for letting me know..this exception is due to sharing of HTable..
I've to go back to to 0.20.6 since our system is down too long..(starting with empty table)
On 0.90.2, do you all think using HTablePool would help with performance problem?
thx
-----Original Message-----
From: Ted Yu <yu...@gmail.com>
To: user@hbase.apache.org
Sent: Wed, Apr 20, 2011 12:27 pm
Subject: Re: java.lang.IndexOutOfBoundsException
I think HConnectionManager can catch IndexOutOfBoundsException and translate
into a more user-friendly message, informing user about thread-safety.
On Wed, Apr 20, 2011 at 9:11 AM, Ted Yu <yu...@gmail.com> wrote:
> I have seen this before.
> HTable isn't thread-safe.
>
> Please describe your usage.
>
> Thanks
>
>
> On Wed, Apr 20, 2011 at 6:03 AM, Venkatesh <vr...@aol.com> wrote:
>
>>
>> Using hbase-0.90.2..(sigh..) Any tip? thanks
>>
>>
>> java.lang.IndexOutOfBoundsException: Index: 4, Size: 3
>> at java.util.ArrayList.RangeCheck(ArrayList.java:547)
>> at java.util.ArrayList.remove(ArrayList.java:387)
>> at
>> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchOfPuts(HConnectionManager.java:1257)
>> at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:822)
>> at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:678)
>> at org.apache.hadoop.hbase.client.HTable.put(HTable.java:663)
>>
>>
>>
>>
>
Re: java.lang.IndexOutOfBoundsException
Posted by Ted Yu <yu...@gmail.com>.
I think HConnectionManager can catch IndexOutOfBoundsException and translate
into a more user-friendly message, informing user about thread-safety.
On Wed, Apr 20, 2011 at 9:11 AM, Ted Yu <yu...@gmail.com> wrote:
> I have seen this before.
> HTable isn't thread-safe.
>
> Please describe your usage.
>
> Thanks
>
>
> On Wed, Apr 20, 2011 at 6:03 AM, Venkatesh <vr...@aol.com> wrote:
>
>>
>> Using hbase-0.90.2..(sigh..) Any tip? thanks
>>
>>
>> java.lang.IndexOutOfBoundsException: Index: 4, Size: 3
>> at java.util.ArrayList.RangeCheck(ArrayList.java:547)
>> at java.util.ArrayList.remove(ArrayList.java:387)
>> at
>> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchOfPuts(HConnectionManager.java:1257)
>> at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:822)
>> at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:678)
>> at org.apache.hadoop.hbase.client.HTable.put(HTable.java:663)
>>
>>
>>
>>
>
Re: java.lang.IndexOutOfBoundsException
Posted by Ted Yu <yu...@gmail.com>.
I have seen this before.
HTable isn't thread-safe.
Please describe your usage.
Thanks
On Wed, Apr 20, 2011 at 6:03 AM, Venkatesh <vr...@aol.com> wrote:
>
> Using hbase-0.90.2..(sigh..) Any tip? thanks
>
>
> java.lang.IndexOutOfBoundsException: Index: 4, Size: 3
> at java.util.ArrayList.RangeCheck(ArrayList.java:547)
> at java.util.ArrayList.remove(ArrayList.java:387)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchOfPuts(HConnectionManager.java:1257)
> at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:822)
> at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:678)
> at org.apache.hadoop.hbase.client.HTable.put(HTable.java:663)
>
>
>
>