Thanks,
I think we are having the same or similar issue with virus scan/security scan.
However that should not bring down the master, can it??
I am still digging thru the logs.
-S
From: Adam J. Shook
Sent: Wednesday, March 16, 2022 2:46 PM
To: user@accumulo.apache.org
Subject: Re: [External]
This is certainly anecdotal, but we've seen this "ERROR: Read a frame size
of (large number)" before on our Accumulo cluster that would show up at a
regular and predictable frequency. The root cause was due to a routine scan
done by the security team looking for vulnerabilities across the entire
Since that error message is coming from the libthrift library, and not
Accumulo code, we would need a lot more context to even begin helping you
troubleshoot it. For example, the complete stack trace that shows the
Accumulo code that called into the Thrift library, would be extremely
helpful.
Thanks Mike,
After stopping all the services, i just moved /accumulo to /old-accumulo and
then ran
accumulo init --clear-instance-name --instance-name --password
With that plain vanilla accumulo came up after restarting the services.
Plan is to re-create all the tables from /old-accumulo
It is hard to help you without a full explanation of what exactly you are
doing. Was that error in the Master log? What commands did you run exactly
to "re-initialize"? Did you wipe all the data or just run
"--reset-security"?
On Wed, Mar 16, 2022 at 7:14 AM Ligade, Shailesh [USA] <
Well, I re-initialized accumulo but I still see
ERROR: Read a frame size of 1195725856, which is bigger than the maximum
allowable buffer size for ALL connections.
Is there a setting that I can increase to get past it?
-S
From: Ligade, Shailesh [USA]
Sent:
