Yes, it's a bit confusing. maxWait controls how long a fetch request will
wait on the broker in the normal case. The issue is that if there is a hard
crash on the broker (host is down), the client may not realize this
immediately since TCP will try very hard to maintain the socket connection.
By setting SocketTimeout, we allow the client to break out sooner in this
case. Typically, SocketTimeout should be set to be at least maxWait or a
bit larger.

It's possible to specify an indefinite long poll by setting maxWait to a
very large value. It's not recommended right now due to


On Tue, Nov 26, 2013 at 3:43 AM, Simon Cooper <
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB