Hello!
I've been experiencing a problem with timeouts in the zk gem. When I make a .children call on a very large zk system, I time out after exactly ten seconds.
I'm aware (now, anyway) that the connection timeout established in ZK::Client::Threaded is not the same timeout I'm looking for. I also noted this bit on line 63 of threaded.rb:
# @note The `:timeout` argument here is *not* the session_timeout for the
# connection. rather it is the amount of time we wait for the connection
# to be established. The session timeout exchanged with the server is
# set to 10s by default in the C implemenation, and as of version 0.8.0
# of slyphon-zookeeper has yet to be exposed as an option. That feature
# is planned.
However, I'd like to assume that the session timeout is not what I'm looking for either.
Is the timeout I need to prevent the following trace exposed anywhere?
#<ZK::Exceptions::OperationTimeOut: inputs: {:path=>"/path/to/some/node"}>
inputs: {:path=>"/path/to/some/node"}
/Users/wwboynton/.rvm/gems/ruby-1.9.3-p392/gems/zk-1.8.0/lib/zk/client/base.rb:1068:in `check_rc'
/Users/wwboynton/.rvm/gems/ruby-1.9.3-p392/gems/zk-1.8.0/lib/zk/client/base.rb:1057:in `call_and_check_rc'
/Users/wwboynton/.rvm/gems/ruby-1.9.3-p392/gems/zk-1.8.0/lib/zk/client/threaded.rb:581:in `call_and_check_rc'
/Users/wwboynton/.rvm/gems/ruby-1.9.3-p392/gems/zk-1.8.0/lib/zk/client/base.rb:717:in `block in children'
/Users/wwboynton/.rvm/gems/ruby-1.9.3-p392/gems/zk-1.8.0/lib/zk/event_handler.rb:282:in `setup_watcher!'
/Users/wwboynton/.rvm/gems/ruby-1.9.3-p392/gems/zk-1.8.0/lib/zk/client/base.rb:1100:in `setup_watcher!'
/Users/wwboynton/.rvm/gems/ruby-1.9.3-p392/gems/zk-1.8.0/lib/zk/client/base.rb:716:in `children'
zk.children call results in ^
Thank you!
Hello!
I've been experiencing a problem with timeouts in the zk gem. When I make a
.childrencall on a very large zk system, I time out after exactly ten seconds.I'm aware (now, anyway) that the connection timeout established in
ZK::Client::Threadedis not the same timeout I'm looking for. I also noted this bit on line 63 ofthreaded.rb:However, I'd like to assume that the session timeout is not what I'm looking for either.
Is the timeout I need to prevent the following trace exposed anywhere?
Thank you!