[
https://issues.apache.org/jira/browse/ACCUMULO-4561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201366#comment-16201366
]
Christopher Tubbs commented on ACCUMULO-4561:
---------------------------------------------
That's interesting. The thrift client should have a more sane failure behavior
when the TCP response is not in the expected protocol. Jetty is detecting the
protocol mismatch, and reacting reasonably using the only protocol it knows;
there's no reason Thrift shouldn't behave similarly.
For a client, the response should be to throw an Exception if the protocol
doesn't match. For a server, it should respond with an error message in its
native protocol, like Jetty did with the HTTP 400 error.
This might be something we need to escalate to Thrift upstream developers, if
it's not something already built in to the Thrift client that we're not
handling properly. The next step should be to check to see if our client code
is failing to properly handle a relevant exception coming from the Thrift
library.
> Crash when using ping on a non-existing server
> ----------------------------------------------
>
> Key: ACCUMULO-4561
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4561
> Project: Accumulo
> Issue Type: Bug
> Components: shell
> Affects Versions: 2.0.0
> Reporter: Luis Tavarez
>
> While working on ACCUMULO-4558, I tried running
> {code}ping -ts localhost:9995{code} (localhost:9995 does not have a a tserver
> on my setup.)
> And it caused the shell to exit (crashed) and show the following message.
> {code}#
> # java.lang.OutOfMemoryError: Java heap space
> # -XX:OnOutOfMemoryError="kill -9 %p"
> # Executing /bin/sh -c "kill -9 25561"...
> /home/lmtavar/git/uno/bin/uno: line 44: 25561 Killed
> "$ACCUMULO_HOME"/bin/accumulo shell -u "$ACCUMULO_USER" -p
> "$ACCUMULO_PASSWORD" "${@:2}"
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
