in hdfs, part of the last contact value increases

2016-12-21 Thread ????
Recently, I have increased two disks on a single datanode . I encountered a problem, in hdfs, part of the last contact value increases, resulting in hbase the handler is occupied. The datanode prints the log as follows: 2016-12-21 10:13:50,816 WARN

Re: 答复: [ANNOUNCE] New HBase committer Guanghao Zhang

2016-12-21 Thread Esteban Gutierrez
Congratulations and welcome Guanghao! -- Cloudera, Inc. On Wed, Dec 21, 2016 at 5:29 PM, Honghua Feng 冯宏华 wrote: > Congratulations and welcome Guanghao！ > > 发件人: saint@gmail.com 代表 Stack

答复: [ANNOUNCE] New HBase committer Guanghao Zhang

2016-12-21 Thread Honghua Feng 冯宏华
Congratulations and welcome Guanghao！ 发件人: saint@gmail.com 代表 Stack 发送时间: 2016年12月21日 2:01 收件人: HBase Dev List 抄送: hbase-user 主题: Re: [ANNOUNCE] New HBase committer Guanghao Zhang Welcome Guanghao! St.Ack On

Re: Lease exception

2016-12-21 Thread Rajeshkumar J
I am using hbase version 1.1.1 Also I didn't understand something here. Whenever a scanner.next() is called it needs to return rows(based on caching value) within leasing period or else scanner client will be closed eventually throwing this exception. Correct me as I didn't get the clear

Re: Lease exception

2016-12-21 Thread Ted Yu
Which hbase release are you using ? There is heartbeat support when scanning. Looks like the version you use doesn't have this support. Cheers > On Dec 21, 2016, at 4:02 AM, Rajeshkumar J > wrote: > > Hi, > > Thanks for the reply. I have properties as below

Re: Lease exception

2016-12-21 Thread Richard Startin
If your client caching is set to a large value, you will need to do a long scan occasionally, and the rpc itself will be expensive in terms of IO. So it's worth looking at hbase.client.scanner.caching to see if it is too large. If you're scanning the whole table check you aren't churning the

Re: Lease exception

2016-12-21 Thread Rajeshkumar J
Hi, Thanks for the reply. I have properties as below hbase.regionserver.lease.period 90 hbase.rpc.timeout 90>/value> Correct me If I am wrong. I know hbase.regionserver.lease.period, which says how long a scanner lives between calls to scanner.next(). As

Re: Lease exception

2016-12-21 Thread Richard Startin
It means your lease on a region server has expired during a call to resultscanner.next(). This happens on a slow call to next(). You can either embrace it or "fix" it by making sure hbase.rpc.timeout exceeds hbase.regionserver.lease.period. https://richardstartin.com On 21 Dec 2016, at 11:30,

Lease exception

2016-12-21 Thread Rajeshkumar J
Hi, I have faced below issue in our production cluster org.apache.hadoop.hbase.regionserver.LeaseException: org.apache.hadoop.hbase.regionserver.LeaseException: lease '166881' does not exist at org.apache.hadoop.hbase.regionserver.Leases.removeLease(Leases.java:221) at

Approach: Incremental data load from HBASE

2016-12-21 Thread Chetan Khatri
Hello Guys, I would like to understand different approach for Distributed Incremental load from HBase, Is there any *tool / incubactor tool* which satisfy requirement ? *Approach 1:* Write Kafka Producer and maintain manually column flag for events and ingest it with Linkedin Gobblin to HDFS /