It might be to do with the way you've installed Drill.

If you've built and deployed Drill, odds are that the client will be different. 
With the RPM installation, however, the installer has symlinks to make the 
mapr-client libraries required by Drill be pointing to the libraries available 
in /opt/mapr/lib/ 

I don't know the exact details of what all gets symlinked, but this step should 
have ensured that you don't see mismatch between the versions.

That said... Support would be better equipped to help you with this. 

-----Original Message-----
From: John Omernik [mailto:[email protected]] 
Sent: Thursday, February 08, 2018 1:38 PM
To: user <[email protected]>
Subject: MapR Drill 1.12 Mismatch between Native and Library Versions

I am running MapR's 1.12 drill on a node that only has posix client installed 
(and thus has a MapR client from that).

I've recently had to work with MapR Support to get a fix to posix, and that 
fixed one issue, but now when I try to start a drill bit, I get this error.
The fix was a small patch that only updated the posix library... I guess I am 
confused why I am seeing one "non-patched" version (in the java library) and 
one "patched" version in the native library and why I can't start drill. I was 
debating where to post this, MapR community or here, but it's only Drill I 
having an issue... any thoughts?

John












2018-02-08 15:20:54,3305 ERROR JniCommon
fs/client/fileclient/cc/jni_MapRClient.cc:687 Thread: 71 Mismatch found for 
java and native libraries java build version 6.0.0.20171109191718.GA, native 
build version 6.0.0.20171229015939.GA java patch vserion $Id: mapr-version: 
6.0.0.20171109191718.GA e892229b271c98c75ccb, native patch version $Id: 
mapr-version:
6.0.0.20171229015939.GA bd8dae73f45572194c89
2018-02-08 15:20:54,3305 ERROR JniCommon
fs/client/fileclient/cc/jni_MapRClient.cc:704 Thread: 71 Client initialization 
failed.
Exception in thread "main"
org.apache.drill.exec.exception.DrillbitStartupException: Failure while 
initializing values in Drillbit.

Reply via email to