[
https://issues.apache.org/jira/browse/HBASE-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980273#action_12980273
]
Bill Graham commented on HBASE-3436:
------------------------------------
I'm don't recall running mvn install, but I do see this jar in my maven repos:
~/.m2/repository/org/apache/hadoop/hadoop-core/0.20-append-r1042285/hadoop-core-0.20-append-r1042285.jar
Which is the same one that is packaged the HBase lib/ dir. What I recall is
doing the following:
1. Downloading the HBase tar and extracting it
2. Modifying some configs and running it from by home dir
3. Copying the distro with custom configs to /var/opt/habase, where we now run
it.
I'm not sure how the append jar got to my maven repo, but maybe I ran some
target within HBase that put it there? I suspect my target/cached_classpath.txt
file came along for the ride in step 3 above.
Either way, I've deleted the cached_classpath file and I can no longer
reproduce, meaning I can't manage to get the maven jars into my classpath when
starting/stoping the master. This is a good thing.
Feel free to mark this issue as invalid if it seems like something I might have
done. We should try to make this maven/classpath functionality more obvious
though, since I was hung up on this for a long time. Maybe better log messaging
that these classes are being inserted into the cp would help.
> HBase start scripts should not include maven repos jars if they exist in lib
> ----------------------------------------------------------------------------
>
> Key: HBASE-3436
> URL: https://issues.apache.org/jira/browse/HBASE-3436
> Project: HBase
> Issue Type: Bug
> Reporter: Bill Graham
> Priority: Critical
> Fix For: 0.90.1
>
>
> When starting the master, the jars of the users maven repos get injected into
> the classpath as a convenience to developers. This can cause quite a
> debugging headache when hadoop jars don't match what's on the cluster.
> We should change the start scripts to not do this if the jars exist in the
> lib dir. Or better yet, we would only include maven repos jars if an optional
> param exists in hbase-env.sh.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
