It uploads the file in small (1024*5 bytes) chunks. Does this happen every time (i.e. reproducible)? What is the size of your topology jar?
Can you post the server side message (I want to see the length it output). - Taylor On Mar 18, 2014, at 3:40 PM, Adam Lewis <[email protected]> wrote: > Upon upgrading from 0.9.0.1 to 0.9.1-incubating, I'm exceeding the new thrift > max buffer size (nicely logged on the server side, although the client just > gets a broken pipe stack trace form thrift) with an approx 6 MB message(!). > Increasing the configured limit solves the problem, but I would have thought > the 1MB default should be enough. > > Does the storm submitter encode the entire topology as a single thrift > message? I'm really surprised that the message is coming out so large, my > topology isn't exactly small, but it only has about 20 bolts...does anyone > have any suggestions on how to determine why the message is so large? Is > this within the realm of what others have seen or am I doing something wrong? > > Thanks, > Adam
signature.asc
Description: Message signed with OpenPGP using GPGMail
