[
https://issues.apache.org/jira/browse/HBASE-22010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16788334#comment-16788334
]
Hudson commented on HBASE-22010:
--------------------------------
Results for branch branch-2.2
[build #94 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/94/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/94//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/94//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/94//JDK8_Nightly_Build_Report_(Hadoop3)/]
(x) {color:red}-1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
-- Something went wrong with this stage, [check relevant console
output|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/94//console].
> docs on upgrade from 2.0,2.1 -> 2.2 renders incorrectly
> -------------------------------------------------------
>
> Key: HBASE-22010
> URL: https://issues.apache.org/jira/browse/HBASE-22010
> Project: HBase
> Issue Type: Bug
> Components: documentation
> Affects Versions: 3.0.0, 2.2.0
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Minor
> Fix For: 3.0.0, 2.2.1
>
> Attachments: HBASE-22010.0.patch
>
>
> heading doesn't work, which also means no linking to it.
> the rendered page has an unrendered bit, e.g.
> {code}
> [[upgrade 2.2]] === Upgrade from 2.0 or 2.1 to 2.2+
> HBase 2.2+ uses a new Procedure form assiging/unassigning/moving Regions. It
> does not process HBase 2.1 and 2.0’s Unassign/Assign Procedure types. Upgrade
> requires that we first drain the Master Procedure Store of old style
> Procedures before starting the new 2.2 Master. So you need to make sure that
> before you kill the old version (2.0 or 2.1) Master, there is no region in
> transition. And once the new version (2.2+) Master is up, you can rolling
> upgrade RegionServers one by one.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
