@James: that was incredible. Thank you. On Wed, Apr 26, 2017 at 9:53 PM, James Cheng <wushuja...@gmail.com> wrote:
> Ramya, Todd, Jiefu, David, > > Sorry to drag up an ancient thread. I was looking for something in my > email archives, and ran across this, and I might have solved part of these > mysteries. > > I ran across this post that talked about seeing weirdly large allocations > when incorrect requests are accidentally sent to a port expecting a binary > protocol. https://rachelbythebay.com/w/2016/02/21/malloc/ > > I took those finding and applied them to the weird big numbers you were > seeing. > > Ramya, Jiefu, about your allocation of 1347375956: > 1347375956 converted to hex is 504F5354 > 504F5354 converted to ascii is the letters "POST" > So, someone sent a POST request to your Kafka broker by accident! > > David, about your allocation of 1550939497: > 1550939497 converted to hex is 5C717569 > 5C717569 converted to ascii is "\qui" > Maybe that's the beginning of the word "\quit"? Is there some protocol > that uses the word "\quit"? Like IRC or SMTP or IMAP something? I'm not > sure. > > Anyway, thought you might find that interesting! > > -James > > > > > > On Dec 12, 2016, at 9:39 AM, Todd Palino <tpal...@gmail.com> wrote: > > > > Are you actually getting requests that are 1.3 GB in size, or is > something > > else happening, like someone trying to make HTTP requests against the > Kafka > > broker port? > > > > -Todd > > > > > > On Mon, Dec 12, 2016 at 4:19 AM, Ramya Ramamurthy < > > ramyaramamur...@teledna.com> wrote: > > > >> We have got exactly the same problem. > >> nvalid receive (size = 1347375956 larger than 104857600). > >> > >> When trying to increase the size, Java Out of Memory Exception. > >> Did you find a work around for the same ?? > >> > >> Thanks. > >> > > > > > > On Tue, Jul 14, 2015 at 11:18 AM, JIEFU GONG <jg...@berkeley.edu <mailto: > jg...@berkeley.edu>> wrote: > > > @Gwen > > I am having a very very similar issue where I am attempting to send a > > rather small message and it's blowing up on me (my specific error is: > > Invalid receive (size = 1347375956 larger than 104857600)). I tried to > > change the relevant settings but it seems that this particular request is > > of 1340 mbs (and davids will be 1500 mb) and attempting to change the > > setting will give you another error saying there is not enough memory in > > the java heap. Any insight here? > > > > > > > -- > > *Todd Palino* > > Staff Site Reliability Engineer > > Data Infrastructure Streaming > > > > > > > > linkedin.com/in/toddpalino > >
