[
https://issues.apache.org/jira/browse/HBASE-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514881#comment-14514881
]
Nick Dimiduk commented on HBASE-13339:
--------------------------------------
[~lhofhansl]:
bq. If we force a Hadoop upgrade with a minor version of HBase we force folks
to go through the Hadoop upgrade process (need to check whether 2.5->2.6 needs
this).
Not sure why you say Hadoop 2.5.x to 2.6.x is a "major" upgrade of Hadoop.
Looks like a minor update to me, according to the [compatibility
report|http://people.apache.org/~ndimiduk/release-2.5.1_release-2.6.0_compat_report.html].
The points of "major incompatibility" are on {{Unstable}} and {{Evolving}}
classes and methods. Further, it's a minor update of HBase, so a minor update
of our dependencies should be acceptable. Hmm, looks like that's not what we
allow in the compatibility matrix in our book.
bq. If we want to turn 1.1 into 2.0, the current branch-1 becomes effective
branch-2
I hope we can avoid this. I don't think 1.1 is that different from 1.0, but let
me look deeper into this
[report|http://people.apache.org/~ndimiduk/1.0.0_branch-1.1_compat_report.html]
as well.
[~eclark]:
bq. The abstract fear of maybe having some incompatibility that users would
have to deal with doesn't seem to me to justify staying behind when there are
bug fixes and new features.
I think the above compat report says our users should be okay with the version
bump. You see something I don't?
bq. It's not just not recommended. It's that the client that we're shipping by
default is un-able to handle any timeouts.
Is that somehow because of how we package/ship our client jar or from a client
application depending on hadoop trasnitively? Should be that if hadoop-2.6.0 is
on the client, the client will pick up this version from the runtime.
[~apurtell]:
bq. Anecdotally I hear 2.6 is an unstable release
Would be nice to have some references for this claim. The only one so far was
identified after I bumped the and HBASE-13574 / HDFS-8270 was identified.
> Update default Hadoop version to 2.6.0
> --------------------------------------
>
> Key: HBASE-13339
> URL: https://issues.apache.org/jira/browse/HBASE-13339
> Project: HBase
> Issue Type: Bug
> Components: build
> Affects Versions: 2.0.0, 1.1.0
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Priority: Blocker
> Fix For: 2.0.0, 1.1.0, 1.2.0
>
> Attachments: HBASE-13339-v1.patch, HBASE-13339.patch
>
>
> Current default Hadoop version is getting a little long in the tooth. We
> should update to the latest version. The latest version is backwards
> compatible with 2.5.1's dfs and mr so this should be painless.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
