More of the log and the version of HBase involved please. Thanks. St.Ack
On Wed, Nov 13, 2013 at 1:07 AM, jingych <[email protected]> wrote: > Thanks, esteban! > > I'v tried. But it did not work. > > I first load the customer hbase-site.xml, and then try to check the hbase > server. > So my code is like this: > <code> > conf.setInt("hbase.client.retries.number", 1); > conf.setInt("hbase.client.pause", 5); > conf.setInt("ipc.socket.timeout", 5000); > conf.setInt("hbase.rpc.timeout", 5000); > </code> > > The log printing: Sleeping 4000ms before retry #2... > > If the zookeeper's quarum is the wrong address, the process will take very > long time. > > > > > 井玉成 > > 基础软件事业部 > 东软集团股份有限公司 > 手机：13889491801 > 电话：0411-84835702 > > 大连市甘井子区黄浦路901号 D1座217室 > Postcode：116085 > Email：[email protected] > > From: Esteban Gutierrez > Date: 2013-11-13 11:12 > To: [email protected]; jingych > Subject: Re: HBaseAdmin#checkHBaseAvailable COST ABOUT 1 MINUTE TO CHECK A > DEAD(OR NOT EXISTS) HBASE MASTER > jingych, > > The behavior is driven by the number of retries > (hbase.client.retries.number), the length of the pause between retries > (hbase.client.pause) and the timeout to establish a connection > (ipc.socket.timeout) and the time to get some data back from HBase > (hbase.rpc.timeout). Lowering the rpc timeout and the ipc socket timeout > should help you to fail fast the operation when the HBase Master is not > responsive. > > cheers, > esteban. > > > > > -- > Cloudera, Inc. > > > > On Tue, Nov 12, 2013 at 6:49 PM, jingych <[email protected]> wrote: > > > HI, > > > > I wonder is there any way to limit the "HBaseAdmin#checkHBaseAvailable" > > method time cost. > > > > As i use the "HBaseAdmin#checkHBaseAvailable" method to test if the hbase > > master is connectable. > > But if the target master is dead or not exists at all, this method will > > cost 1 minute to wait the result. > > > > > > > > > > jingych > > 2013-11-13 > > > > > --------------------------------------------------------------------------------------------------- > > Confidentiality Notice: The information contained in this e-mail and any > > accompanying attachment(s) > > is intended only for the use of the intended recipient and may be > > confidential and/or privileged of > > Neusoft Corporation, its subsidiaries and/or its affiliates. If any > reader > > of this communication is > > not the intended recipient, unauthorized use, forwarding, printing, > > storing, disclosure or copying > > is strictly prohibited, and may be unlawful.If you have received this > > communication in error,please > > immediately notify the sender by return e-mail, and delete the original > > message and all copies from > > your system. Thank you. > > > > > --------------------------------------------------------------------------------------------------- > > > > --------------------------------------------------------------------------------------------------- > Confidentiality Notice: The information contained in this e-mail and any > accompanying attachment(s) > is intended only for the use of the intended recipient and may be > confidential and/or privileged of > Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader > of this communication is > not the intended recipient, unauthorized use, forwarding, printing, > storing, disclosure or copying > is strictly prohibited, and may be unlawful.If you have received this > communication in error,please > immediately notify the sender by return e-mail, and delete the original > message and all copies from > your system. Thank you. > > --------------------------------------------------------------------------------------------------- >
