hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Rawson <ryano...@gmail.com>
Subject Re: negotiated timeout
Date Fri, 25 Mar 2011 03:48:05 GMT
the HQuorumPeer uses hbase-site.xml/hbase-default.xml to configure ZK,
including the line Patrick pointed out.  You can increase that to
increase the max timeout.

-ryan

On Thu, Mar 24, 2011 at 5:27 PM, Ted Yu <yuzhihong@gmail.com> wrote:
> Seeking more comment.
>
> ---------- Forwarded message ----------
> From: Patrick Hunt <phunt@apache.org>
> Date: Thu, Mar 24, 2011 at 4:15 PM
> Subject: Re: negotiated timeout
> To: Ted Yu <yuzhihong@gmail.com>
> Cc: dev@zookeeper.apache.org, Mahadev Konar <mahadev@apache.org>,
> zookeeper-dev@hadoop.apache.org
>
>
> Ted, you'll need to ask the hbase guys about this if you are not
> running a dedicated zk cluster. I'm not sure how they manage embedded
> zk.
>
> However a quick search of the HBASE code results in:
>
> ./src/main/java/org/apache/hadoop/hbase/zookeeper/HQuorumPeer.java:
>
>   // Set the max session timeout from the provided client-side timeout
>   properties.setProperty("maxSessionTimeout",
>       conf.get("zookeeper.session.timeout", "180000"));
>
> Patrick
>
> On Thu, Mar 24, 2011 at 4:00 PM, Ted Yu <yuzhihong@gmail.com> wrote:
>> Patrick:
>> Do you want me to look at maxSessionTimeout ?
>> Since hbase manages zookeeper, I am not sure I can control this parameter
>> directly.
>>
>> On Thu, Mar 24, 2011 at 3:50 PM, Patrick Hunt <phunt@apache.org> wrote:
>>>
>>>
>>>
> http://zookeeper.apache.org/doc/r3.3.3/zookeeperAdmin.html#sc_advancedConfiguration
>>>
>>> On Thu, Mar 24, 2011 at 3:43 PM, Mahadev Konar <mahadev@apache.org>
> wrote:
>>> > Hi Ted,
>>> >  The session timeout can be changed by the server depending on min/max
>>> > bounds set on the servers. Are you servers configured to have a max
>>> > timeout of 60 seconds? usually the default is 20 * tickTime. Looks
>>> > like your ticktime is 3 seconds?
>>> >
>>> > thanks
>>> > mahadev
>>> >
>>> >
>>> >
>>> > On Thu, Mar 24, 2011 at 3:20 PM, Ted Yu <yuzhihong@gmail.com> wrote:
>>> >> Hi,
>>> >> hbase 0.90.1 uses zookeeper 3.3.2
>>> >> I specified:
>>> >> <property>
>>> >> <name>zookeeper.session.timeout</name>
>>> >> <value>490000</value>
>>> >> </property>
>>> >>
>>> >> In zookeeper log I see:
>>> >> 2011-03-24 19:58:09,499 INFO
> org.apache.zookeeper.server.NIOServerCnxn:
>>> >> Client attempting to establish new session at /10.202.50.111:50325
>>> >> 2011-03-24 19:58:09,499 INFO
> org.apache.zookeeper.server.NIOServerCnxn:
>>> >> Established session 0x12ebb99d686a012 with negotiated timeout 60000
> for
>>> >> client /10.202.50.112:62386
>>> >> 2011-03-24 19:58:09,499 INFO
> org.apache.zookeeper.server.NIOServerCnxn:
>>> >> Client attempting to establish new session at /10.202.50.112:62387
>>> >> 2011-03-24 19:58:09,499 INFO
>>> >> org.apache.zookeeper.server.PrepRequestProcessor: Got user-level
>>> >> KeeperException when processing sessionid:0x12ebb99d686a012
> type:create
>>> >> cxid:0x1 zxid:0xfffffffffffffffe txntype:unknown reqpath:n/a Error
>>> >> Path:/hbase Error:KeeperErrorCode = NodeExists for /hbase
>>> >> 2011-03-24 19:58:09,499 INFO
> org.apache.zookeeper.server.NIOServerCnxn:
>>> >> Established session 0x12ebb99d686a013 with negotiated timeout 60000
> for
>>> >> client /10.202.50.111:50324
>>> >>
>>> >> Can someone tell me how the negotiated timeout of 60000 was computed
?
>>> >>
>>> >> Thanks
>>> >>
>>> >
>>
>>
>

Mime
View raw message