So already, you have given me some things to work with. Knowing that there may links to jars/3rdparty was very helpful. In opening that folder on drill-1.12.0 I found there were no links/files related to mapr. In my drill-1.10.0 version (both of them from MapR) there were three files, maprfs, maprdb, and mapr-hbase.
So I added only those three files from /opt/mapr/lib to $DRILL_CLASSPATH in my drill_env.sh. This allowed drill to start without that same error. Now, I am being a little different. Instead of "installing" drill via RPMs, I download the RPMs (and I did this for both 1.10 and 1.12 from MapR) The difference I think is in 1.10 there was a "drill" package and now in 1.12, there is a drill-internal package. Perhaps the drill in 1.10 moved some things around better. For what ever reason that changed (I think it changed in 1.11, but I was having cluster issues during that). That said, I have a drill bit running, but it's not starting it's web service. I am going to go reverse engineer what the RPM actually does. In my case, for 1.10 and every version previous, I just took the mapr RPM, unpacked it, and grabbed the drill directory and it worked great. This is obviously no longer the case, and I will have to dig deeper. On Thu, Feb 8, 2018 at 4:01 PM, Abhishek Girish <[email protected]> wrote: > Can you also share the contents of (1) MapR build version on the cluster > nodes (cat /opt/mapr/MapRBuildVersion) (2) Drill RPM version installed (rpm > -qa |grep -i mapr-drill) > > And also verify if the maprfs and maprdb jars inside > $DRILL_HOME/jars/3rdparty are links to the corresponding jars in > /opt/mapr/lib? > > On Thu, Feb 8, 2018 at 1:50 PM, Kunal Khatua <[email protected]> wrote: > > > 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. > > >
