Hi All,
HBase client waits indefinitely for performing any operation. On taking,
jstack we saw all the threads waiting on BoundedCompletionService.take()
call. The hconnection pool's stack is
hconnection-0x58ca857d-shared--pool1-t96" daemon prio=10
tid=0x7f29d4510800 nid=0x84d0 waiting on co
hbase.client.retries.number => 5
zookeeper.recovery.retry => 0
zookeeper.session.timeout => 1000
zookeeper.recovery.retry.intervalmilli => 1
hbase.rpc.timeout => 3.
We changed this config to have fail fast during
any hbase or hadoop deamon failure.
Thanks
Regards
Mukund Murrali
Hi
We still facing this issue. Any one can help us out of this.
Thanks
Regards
Mukund Murrali
Hi
In our case there at that instance when the client thread stalled, there
was a hbase:meta region split happening. So what went wrong? If there is a
split why should hconnection thread stall? Since we changed the client
configuration caused this? I am once again specifying our client related
cha
gt; > Sent from phone. Excuse typos.
> > On Jun 5, 2015 6:00 PM, "mukund murrali" > wrote:
> >
> > > Hi
> > >
> > > In our case there at that instance when the client thread stalled,
> there
> > > was a hbase:meta region spl
o this region would have stalled and hence your client
> application also stalled.
>
> As I said the logs would be important here to know what happened. This
> could be one of a case and could be identified with the logs.
>
> Regards
> Ram
>
> On Sat, Jun 6, 2015 at 1:25 PM, muk
ds at RS doing? Handlers mainly..
> which version oh hbase?
>
> On Tuesday, June 9, 2015, mukund murrali wrote:
> > Hi
> >
> > I wrote a sample program with default client configurations and created a
> > single connection. I spawn client threads > hbase.hconnect
Kindly look into this for full trace of RS.
http://pastebin.com/VS17vVd8
Thanks
On Wed, Jun 10, 2015 at 11:35 AM, Ted Yu wrote:
> Can you pastebin the complete stack trace for the region server ?
>
> Thanks
>
>
>
> > On Jun 9, 2015, at 10:52 PM, mukund murrali
>
It would be great if there is a single timeout configuration from the
client end. All other parameters should fine tune based on that one
parameter. We have modified simple based on trail basis to suit our need.
Also not sure what side effect it would cause configuring those parameters.
On Mon, Ju
gt; http://hadoop-hbase.blogspot.com/2012/09/hbase-client-timeouts.html
>
> Using yet more threads to monitor timeouts of another thread is a bad
> idea, especially when the timeout is configurable in the first place.
>
> -- Lars
> From: mukund murrali
> To: user@hbase.apache.org
&
using.
>
> Can you try hbase 1.1.0 to see if the problem can be reproduced (in cluster
> deployment) ?
>
> Thanks
>
> On Tue, Jun 9, 2015 at 11:42 PM, mukund murrali
> wrote:
>
> > Kindly look into this for full trace of RS.
> > http://pastebin.com/VS17vVd8
&g
Implementation.locateRegionInMeta(ConnectionManager.java:1200)
>
> Will continue digging through the stack traces / logs.
>
> Cheers
>
> On Wed, Jun 17, 2015 at 10:35 PM, mukund murrali >
> wrote:
>
> > Even with 1.1.0 the issue persists. Client side blocking wait still
> happens
>
Does hbase provide time based increment option? Also something like
checkAndIncrement?
Thanks
Regards
Mukund Murrali
ted
> work ?
>
> RateLimiter and its subclasses in hbase codebase are concerned with rpc
> throttling.
>
> Cheers
>
> On Mon, Jun 22, 2015 at 7:06 AM, mukund murrali
> wrote:
>
> > Does hbase provide time based increment option? Also something like
> > chec
quences if an application suddenly
> >> starts to drop connections before a result or timeout occurs too. ;-)
> >>
> >>
> >>> On Jun 16, 2015, at 12:13 AM, lars hofhansl wrote:
> >>>
> >>> Please always tell us which version of HBase you ar
On Mon, Jun 22, 2015 at 11:19 AM, mukund murrali >
> wrote:
>
> > Hi All
> >
> > I have moved this as jira.
> >
> > https://issues.apache.org/jira/browse/HBASE-13942
> >
> > Please post all your opinions there.
> >
> > Thanks
> >
pta wrote:
> Just curious to know, your client is getting stuck while using
> ClientSmallReversedScanner?
> Can you try using normal scanner and see how it goes?
> what's your cluster setup? # of nodes? hardware?
>
> On Sun, Jul 5, 2015 at 10:21 PM, mukund murrali
> wrot
Hi,
We wanted to have deleted data for a week. So we configured
MIN_VERSIONS => 1
KEEP_DELETED_CELLS => TTL
TTL => 1 week.
As per our understanding, after 1 week the deleted data becomes available
for major compaction and should be purged (correct if wrong). Since we have
time series data, we do
Any one help us in this :( Are we missing somewhere in the use case? None
of the deleted cells are undergoing major compaction.
Thanks
On Wed, Aug 5, 2015 at 12:04 PM, mukund murrali
wrote:
> Hi,
>
> We wanted to have deleted data for a week. So we configured
>
> MI
Thanks
On Mon, Aug 10, 2015 at 8:01 PM, Ted Yu wrote:
> What release of hbase are you using ?
>
> Can you pastebin region server log with DEBUG logging ?
>
> I guess you have tried issuing manual command. Did it work ?
>
> Thanks
>
> On Mon, Aug 10, 2015 at 7:02 AM,
? Long.MIN_VALUE
>
> : now - minTimestamp.longValue();
>
> Can you pastebin log from RatioBasedCompactionPolicy in region server log
> after the manual compaction ?
>
> Thanks
>
> On Tue, Aug 11, 2015 at 2:06 AM, mukund murrali
> wrote:
>
> > We are usin
have caused this problem? We are using hbase-1.0.0.
Thanks
Regards
Mukund Murrali
Any update from anyone on this? We are invoking major compaction manually
and we see too many skipping of major compaction since we have MIN_VERSION
to 1.
Thanks
On Tue, Aug 11, 2015 at 5:09 PM, mukund murrali
wrote:
> Yes. We have min version to be 1, hence I suppose there wont be any s
hbck on testnamespace:testtable ?
>
> bq. major compaction was running for a table.
>
> Which table was being compacted ?
>
> Is it possible for you to share the region server log of the new server ?
>
> Cheers
>
> On Thu, Aug 20, 2015 at 4:58 AM, mukund murrali >
> wrot
should work
>
> -Vlad
>
> On Thu, Aug 20, 2015 at 5:04 AM, mukund murrali >
> wrote:
>
> > Any update from anyone on this? We are invoking major compaction manually
> > and we see too many skipping of major compaction since we have
> MIN_VERSION
> > to 1.
> &g
to correct hadoop cluster and started working fine.
On Thu, Aug 20, 2015 at 9:43 PM, mukund murrali
wrote:
> Hi Ted
>
> No didn't run hbck. Once we removed the newly added node things became
> fine. The same table was compacted. The above failed open logs happened in
> ne
Check the hbase-site.xml in the regionserver hosting the namespace. See if
there is anything wrong in hbase.rootdir.
Thanks
On Fri, Sep 11, 2015 at 9:51 AM, Ted Yu wrote:
> From the snippet you posted, it is hard to tell whether DEBUG logging was
> turned on.
>
> If not, please turn on DEBUG lo
not get removed even
after flush?
In other words with VERSIONS =>1 , why should the earlier versions be
stored?
Also with MIN_VERSIONS => 1 and VERSIONS => 1, though the second version
promoted but subsequent flush purged it.
Is this an inconsistency or my understanding is wrong?
Thanks
Regards
Mukund Murrali
Can anyone enlighten why this is happening. This is causing problems in our
production.
On Thu, Oct 15, 2015 at 4:15 PM, mukund murrali
wrote:
> Hi
>
> I am using hbase-1.0. I had two column families C1 and C2.
>
> C1 => 'VERSIONS => 1, MIN_VERSIONS => 0 (def
Ya thanks Ram. With VERSIONS => 1 it means max versions? If yes, why should
the old value be stored when there is a latest version.
Thanks
Regards
Mukund Murrali
On Fri, Oct 16, 2015 at 1:40 PM, ramkrishna vasudevan <
ramkrishna.s.vasude...@gmail.com> wrote:
> With VERSIONS=>1 a
Hi
I am just curious to know why HBase uses NIO (if not wrong) rather than
netty for communication . What are the pros and cons of using Netty over
NIO or NIO over Netty.
Thanks
Regards
Mukund Murrali
Hi Stack
Thanks for enplaning. Yes I am aware of Netty using NIO. Going forward do
we have plans for using Netty or in a better way to put using Netty will be
any help for hbase or hadoop.
Thanks
On Thu, Nov 5, 2015 at 10:53 PM, Stack wrote:
> On Thu, Nov 5, 2015 at 5:42 AM, mukund murr
Any possible solution for this? As the number of clusters are increasing we
are hitting thread limit frequently. Any suggrestions?
Regards,
Mukund Murrali
On Sat, Jul 25, 2015 at 4:39 PM, mukund murrali
wrote:
> Sorry for the delay. No it was not a client scanner call. It happens
>
.
reseek(StoreFileScanner.java:200)
... 19 more
ThanksU
Regards,
Mukund Murrali
thread.
Regards,
Mukund Murrali
On Wed, Jul 5, 2017 at 8:30 PM, Stack wrote:
> (What version of hbase?)
>
> Unfortunately the exception does not print the file name. Can you figure
> which file or region it is? Could try reading content w/ hfile tool to see
> if it complains al
We are again facing the issue for a different region. Any suggestions will
be highly helpful
Thanks
On Thu, 6 Jul 2017 at 11:00 AM, mukund murrali
wrote:
> Hi Stack
>
> We are currently using hbase-1.2.5(Stable). I was not able to read the
> file using HFile tool. It throws the sam
Even we faced this issue recently. Not sure of the cause. And retries are
having things force for this case. Anyone has any idea of why this happens
Regards,
Mukund Murrali
On Fri, Jul 7, 2017 at 10:47 AM, Graceline Abigail Prem Kumar <
pgabigai...@gmail.com> wrote:
> Hi
>
> W
I know the row key. So in what way it will be helpful in analyzing this
issue?
Regards,
Mukund Murrali
On Mon, Jul 10, 2017 at 5:32 AM, Ted Yu wrote:
> Can you find the hfile where this exception happens when doing get / scan ?
>
> Unfortunately the log didn't contain row key.
&
+dev
Regards,
Mukund Murrali
On Mon, Jul 10, 2017 at 1:17 PM, mukund murrali
wrote:
> I know the row key. So in what way it will be helpful in analyzing this
> issue?
>
> Regards,
>
> Mukund Murrali
>
> On Mon, Jul 10, 2017 at 5:32 AM, Ted Yu wrote:
>
>>
this issue please. We are using 1.2.5 stable version
On Mon, 10 Jul 2017 at 7:29 PM, mukund murrali
wrote:
> +dev
>
> Regards,
>
> Mukund Murrali
>
> On Mon, Jul 10, 2017 at 1:17 PM, mukund murrali
> wrote:
>
>> I know the row key. So in what way it will
Hi Mani,
Can you please check if the client thread from which your inserting the
data is being interrupted ? A thread pool shutdown also can cause this.
Regards,
Mukund Murrali
On Wed, Sep 19, 2018 at 8:54 AM Manimekalai K
wrote:
> While putting data in Hbase, using the HTable.put met
41 matches
Mail list logo
