Github user ctubbsii commented on a diff in the pull request:
https://github.com/apache/accumulo-testing/pull/3#discussion_r98796795
--- Diff: core/src/main/java/org/apache/accumulo/testing/core/TestEnv.java
---
@@ -96,15 +97,22 @@ public String getPid() {
}
Possibly general.server.message.size.max ? Docs say default is 1G, but that
doesn't seem right to me.
https://accumulo.apache.org/1.8/accumulo_user_manual.html#_general_server_message_size_max
On Tue, Jan 31, 2017 at 6:07 PM Josh Elser wrote:
> The maximum frame size is
The maximum frame size is being validated by the Thrift Proxy server, not
your client. This is to prevent clients from performing a denial of service
attack against the (shared) service.
There should be a configuration property to control this, but I don't know
what it is off the top of my head
We have C++ client talking to Accumulo server via Thrift, so there are
Accumulo proxy/thrift instances running on the server. The client got
exception, and upon investigation on Accumulo thrift server, this error line
is found:
2017-01-31 18:00:11,806
Github user keith-turner commented on a diff in the pull request:
https://github.com/apache/accumulo/pull/204#discussion_r98688065
--- Diff:
core/src/main/java/org/apache/accumulo/core/client/impl/TableOperationsImpl.java
---
@@ -1208,11 +1207,20 @@ public void online(String