By "re-connect", I'm assuming that the ZK session is expired, not disconnected. For details see http://zookeeper.apache.org/doc/trunk/zookeeperProgrammers.html#ch_zkSessions
In that case, the high level consumer is basically dead, and the application should create a new instance of it. On Mon, Feb 15, 2016 at 12:22 PM Joe San <codeintheo...@gmail.com> wrote: > Any ideas as to which property should I set to enable Zookeeper > re-connection? I have the following properties defined for my consumer > (High Level Consumer API). Is this enough for a automatic Zookeeper > re-connect? > > val props = new Properties() > props.put("zookeeper.connect", zookeeper) > props.put("group.id", groupId) > props.put("auto.commit.enabled", "false") > // this timeout is needed so that we do not block on the stream! > props.put("consumer.timeout.ms", "1") > props.put("zookeeper.sync.time.ms", "200") >