This is something I've only seen a handful of times when writing/running tests that stop and restart tservers. After the tserver is restarted, there is a thread (typically running in the master) which is trying to read a table. As such, the thread will continue to poll until the tserver comes up.
Very infrequently, the client gets a ThriftSecurityException with a code of DEFAULT_SECURITY_ERROR and a message of Unknown security exception. There is no additional information in the client log (from the thrift call inside the batchscanner), and the tserver contains no error messages at all.
The error that the client saw.
The interesting part is that when the client saw this message, the new TabletServer was already started, and the old tabletserver appears to have been dead for 20s. So, the client in the master had been polling for 20s getting a ConnectException (connection refused) which is expected. I don't know why we got this exception after a length of time.
The infrequency in which I see this makes me wonder if the random ports in the new tabletserver are somehow re-grabbing the old tserver's thrift client service port and something is unexpectedly being interpreted as this ThriftSecurityException? That's the only thing that seems remotely possible to me.
- Time Spent:
Commit ff01c68606b32a49b757fee3f5ace18b1ca30809 in accumulo's branch refs/heads/master from [~elserj]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=ff01c68 ]
ACCUMULO-2964Try to avoid the exception before tserver actually starts.