You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2015/05/22 01:02:17 UTC

[jira] [Commented] (ACCUMULO-3114) Incorrect thrift dependency doesn't kill tserver

    [ https://issues.apache.org/jira/browse/ACCUMULO-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555217#comment-14555217 ] 

Christopher Tubbs commented on ACCUMULO-3114:
---------------------------------------------

I'm not sure there's much we can do about this in the general case... if your classpath is corrupt, there's little you can do to ensure any particular behavior. Perhaps we could detect this particular case, but I'm not sure that it'd be worth it.

> Incorrect thrift dependency doesn't kill tserver
> ------------------------------------------------
>
>                 Key: ACCUMULO-3114
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3114
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>    Affects Versions: 1.5.1, 1.6.0
>            Reporter: Josh Elser
>             Fix For: 1.6.3, 1.8.0, 1.7.1
>
>
> I have a classpath with a MiniAccumuloCluster which resulted in some bad thrift dependencies getting included
> {noformat}
> 2014-09-11 18:05:34,014 ERROR [Thread-11] util.CustomNonBlockingServer (CustomNonBlockingServer.java:run(190)) - run() exiting due to uncaught error
> java.lang.NoSuchMethodError: org.apache.thrift.TProcessorFactory.isAsyncProcessor()Z
> 	at org.apache.accumulo.server.util.CustomNonBlockingServer$SelectAcceptThread.handleAccept(CustomNonBlockingServer.java:253)
> 	at org.apache.accumulo.server.util.CustomNonBlockingServer$SelectAcceptThread.select(CustomNonBlockingServer.java:224)
> 	at org.apache.accumulo.server.util.CustomNonBlockingServer$SelectAcceptThread.run(CustomNonBlockingServer.java:183)
> {noformat}
> Sad part -- the TabletServer didn't actually exit. Need to figure out exactly why. 
> Saw this with 1.7, but I'm guessing it affects everything?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)