We are observing an intermittent issue while running a storm topology we are observing that supervisors are taking a lots of time downloading the topology jars.need community help to identify the bottleneck in my system.
try increasing nimbus.thrift.max_buffer_size from default 1MB to 2-5M and see if you are able to see expected.nimbus.thrift.max_buffer_size is the maximum buffer size thrift should use when reading messages.
try increasing nimbus.thrift.max_buffer_size from default 1MB to 2-5M and see if you are able to see expected.nimbus.thrift.max_buffer_size is the maximum buffer size thrift should use when reading messages.