Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

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.

avatar
New Contributor
 
1 ACCEPTED SOLUTION

avatar

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.

View solution in original post

1 REPLY 1

avatar

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.