[ 
https://issues.apache.org/jira/browse/HBASE-19158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411747#comment-16411747
 ] 

stack commented on HBASE-19158:
-------------------------------

Did a pass. Its a great read.

bq. HBCK tool from an earlier release against an HBase 2.0+ cluster will 
destructively alter said cluster in unrecoverable ways.

Footnote or callout that says something like "Unfortunately we are unable to 
distinguish an HBCK client so cannot put in place guards against destructive 
HBCK changes....." .... probably too much for this startup section on reread of 
what I've written here.

bq. As of HBase 2.0, HBCK is a read-only tool that can report the status of 
some non-public system internals. You should not rely on the format nor content 
of these internals to remain consistent across HBase releases.

Ugh. We need HBCK2 and a pointer here to it. Will do in a follow-on.

{{hbase.zookeeper.useMulti}} is removed? On always? Good.

bq. hbase.balancer.tablesOnMaster changed its meaning and related default. See 
the section [[upgrade2.0.regions.on.master]] for details.

What to say here that tables on master is NOT supported in hbase2.

This changed configs section is great.

Yeah, tables on master is just broke in hbase2. AMv2 and regions on master are 
not compatible w/o master refactor.

HBASE-18511 RN has my progress as I figure them incompat. Needs stronger call 
out.  

{code}UPDATE: This is broke. See HBASE-19785. 
UPDATE2: Master carrying Regions does not work reliably, see HBASE-19828. 

See HBASE-19831, the issue to fix regions on Master {code}

I see you have "Downstream users are adviced to leave the defaults in place and 
avoid use of the master-hosting-regions feature." but stronger language?

I'm pretty sure our ops/second on master page has changed in nature. I need to 
figure it and add to this metrics section. 

bq. Server failure. HBase can still read HFiles written in the older version 2 
format.

Need a script that user can run pre-upgrade.

Lets commit this. Can tune with follow-ons. Great start.




> Ref guide needs upgrade update
> ------------------------------
>
>                 Key: HBASE-19158
>                 URL: https://issues.apache.org/jira/browse/HBASE-19158
>             Project: HBase
>          Issue Type: Task
>          Components: documentation
>    Affects Versions: 2.0.0-beta-1
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Blocker
>             Fix For: 2.0.0
>
>         Attachments: HBASE-19158.0.patch, HBASE-19158.1.patch
>
>
> Our ref guide has lots of references in the upgrade section to obsolete 
> versions and no references to the 2.0.0-* releases. We should correct this 
> for beta-1



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to