HBase cluster crashed on-the-hour

I found hbase clutser crashed on-the-hour HBase master running log as follows "2015-07-14 14:41:49,832 DEBUG [master:10.240.131.18:6.oldLogCleaner] master.ReplicationLogCleaner: Didn't find this log in ZK, deleting: 10-241-125-46%2C60020%2C1436841063572.1436851865226 2015-07-14 14:45:49,822 DE

Can I tell when the client actually connected and ready to go?

I posted this question on Stack Overflow a while ago but got no responses. From SO: I am using HBase 1.1.0 and create HBase client connections like this: try { Configuration config = HBase

Re: Hbase Bulk Load - Unknown Host Exception

Hi Vineet, Have you looked into /etc/nsswitch.conf and /etc/resolv.conf if across all hosts are consistent? I've seen intermittent issues with MR jobs when the 'hosts:' entry in /etc/nsswitch.conf points to dns first and there is no nscd daemon running or the DNS server is flakey and the host name

Re: splits and merge

Hi Ted, Jean Marc, Thank you guys for your answer. I think Jean Marc spotted the issue, although we do slightly different. Let's say we have regions A and B. We split both A into A1 and A2 and B into B1 and B2. Then we merge A2 and B1. Note that A and B are adjacent and so A1 with A2, A2 with B

Re: Regionservers going down during compaction

We're running with fine 31g heap (31 to be able to make use of compressed oops) after a lot of tuning. Maybe your pattern is different...? Or... Since it is ParNew on a 1GB only small gen taking that much time... Maybe you ran into this: http://www.evanjones.ca/jvm-mmap-pause.html? -- Lars

Re: splits and merge

Hi Ivan, For #1, let's consider regions A, B, C and D all in server S. If you merge A and B togher and C and D togher, still in S, you will have A' and C' regions only on S. Now, if you try to merge again A' and C' into a new bigger region, this will fail silently until A' and C' are major comp

Re: Performance of co-processor and observer while fetching data from other RS

I think this is a duplicate post. Please avoid posting same questions. Please use previous thread where I replied. Sent from my iPhone > On Jul 14, 2015, at 11:17 PM, Chandrashekhar Kotekar > wrote: > > Hi, > > REST APIs of my project make 2-3 calls to different tables in HBase. These > cal

Re: splits and merge

bq. that some times merge just does not work. Can you identify under what scenario the merge doesn't work (through closer inspection of the region server log - assuming you have DEBUG logging turned on) ? bq. Are there minimum requirements for two regions to be merged? If the two adjacent region

REST API with joins

Let's assume we have an HBase table and also have a secondary index lookup table; for example, email_address is the key in emails, where in the member table the key is member_id. We would like to retrieve the member f...@bar.com, but effectively process it like a join in SQL getting the member_id

Performance of co-processor and observer while fetching data from other RS

Hi, REST APIs of my project make 2-3 calls to different tables in HBase. These calls are taking 10s of milli seconds to finish. I would like to know 1) If moving business logic to HBase co-processors and/or observer will improve performance? Idea is like to pass all the related information to H

Hbase Bulk Load - Unknown Host Exception

Hi All, I am facing a strange issue, I am running a Hbase Bulk Load to load a Hfile to my hbase table, while running the same I am landing into the same issue over and over again. java.io.IOException: BulkLoad encountered an unrecoverable problem at org.apache.hadoop.hbase.mapreduce.LoadIncrement

splits and merge

Hi, We are using Hbase 0.98.6 and Hadoop 2.5.0 - cdh 5.3.5. We have a couple of questions regarding splits and merge: 1) Since both split and merge are async invocations on the client side, we have a naîve workaround to make it synchronous that is to look at the RS Info Server via an HttpClient

Re: HBase co-processor performance

Using coprocessor to make calls to other Tables or remote Regions is an ANTI-PATTERN. It will create cyclic dependency between RS in your cluster. Coprocessors should be strictly used for operation on local Regions. Search mailing archives for more detailed discussion on this topic. How about deno