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 2019/04/23 21:16:00 UTC

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

     [ https://issues.apache.org/jira/browse/ACCUMULO-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher Tubbs resolved ACCUMULO-3114.
-----------------------------------------
       Resolution: Not A Problem
    Fix Version/s:     (was: 2.0.0)

We can't generally predict how bad/unexpected libraries on the class path will affect other code on the class path. I don't think there's anything we can do for this. If this needs revisiting, please open an issue at https://github.com/apache/accumulo/issues

> 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
>            Priority: Major
>
> 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
(v7.6.3#76005)