Heartbeats are lightweight operations on zookeeper. In the topology, so long heartbeats are happening in a different thread, 1 second interval isn't much of a performance bottleneck.
A contrasting example is zookeeper state update in kafka spout. Now there the interval is directly related to performance because it is a write operation (costly in zookeeper) and it happens in the same thread which generates the tuples. On Sat, Jan 9, 2016 at 6:11 PM, John Yost <[email protected]> wrote: > Hi Everyone, > > During the course of profiling (actually sampling) a worker process with > jvisualvm I noticed the executor and worker zk send threads are always > active. I then checked the heartbeat settings on my topology and noted that > the default executor heartbeat is 1 second. > > Question: is this a potential performance bottleneck? Would it make sense > to bump this up to 5 or 10 seconds? Would like to see what y'all think. > > Thanks > > --John > -- Regards, Abhishek Agarwal
