accumulo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Elser <josh.el...@gmail.com>
Subject Re: why a frame size is too bigger
Date Thu, 19 Mar 2015 02:00:15 GMT
This list is, and has always been, self-(un)subscribe.

http://accumulo.apache.org/mailing_list.html

user-unsubscribe@accumulo.apache.org

Carney, Patti wrote:
> I have asked several times to be taken off this list.
>
> Please remove me.
>
> *From:*Sean Busbey [mailto:busbey@cloudera.com]
> *Sent:* Wednesday, March 18, 2015 9:40 AM
> *To:* Accumulo User List
> *Subject:* Re: why a frame size is too bigger
>
> Both of those numbers indicate the other side of the RPC asked for a
> *very* large frame. The negative value is due to Java only having signed
> types, so numbers with the highest bits set are read as negative.
>
> Usually these requests are because something that isn't an Accumulo
> client connects to the port, commonly automated security scanners.
>
> Are they showing up when you're attempting to use normal Accumulo clients?
>
> On Wed, Mar 18, 2015 at 3:20 AM, Lu.Qin <luq.java@gmail.com
> <mailto:luq.java@gmail.com>> wrote:
>
> Hi,All
>
> I see a log in Recent Logs like this :
>
> Read a frame size of 1330664521, which is bigger than the maximum allowable buffer size
for ALL connections.
>
> or
>
> Read an invalid frame size of -1811886609. Are you using TFramedTransport on the client
side?
>
>
>
>
>
> How can I config the maximum allowable buffer size ?
>
> and Why the size is small then zero?
>
>
>
> Thanks.
>
>
>
> --
>
> Sean
>
> Notice: This e-mail message, together with any attachments, contains
> information of Merck & Co., Inc. (2000 Galloping Hill Road, Kenilworth,
> New Jersey, USA 07033), and/or its affiliates Direct contact information
> for affiliates is available at
> http://www.merck.com/contact/contacts.html) that may be confidential,
> proprietary copyrighted and/or legally privileged. It is intended solely
> for the use of the individual or entity named on this message. If you are
> not the intended recipient, and have received this message in error,
> please notify us immediately by reply e-mail and then delete it from
> your system.
>

Mime
View raw message