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 <[email protected]> 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
