Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

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 Member
 
1 ACCEPTED SOLUTION

avatar
Super Guru

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
Super Guru

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.