hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-20273) [DOC] include call out of additional changed config defaults in 2.0 upgrade
Date Thu, 29 Mar 2018 18:51:00 GMT

     [ https://issues.apache.org/jira/browse/HBASE-20273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mike Drob updated HBASE-20273:
------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0
           Status: Resolved  (was: Patch Available)

pushed to master, there was a conflict on branch-2 since it looks like hbase-19158 hasn't
made it there yet.

thanks for review, Ted

> [DOC] include call out of additional changed config defaults in 2.0 upgrade
> ---------------------------------------------------------------------------
>
>                 Key: HBASE-20273
>                 URL: https://issues.apache.org/jira/browse/HBASE-20273
>             Project: HBase
>          Issue Type: Sub-task
>          Components: documentation
>    Affects Versions: 2.0.0
>            Reporter: Sean Busbey
>            Assignee: Mike Drob
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: HBASE-20273.patch
>
>
> Copied from feedback on HBASE-19158 from [~mdrob]:
> {quote}
> Default settings/configuration properties changed/renamed:
> HBASE-19919
> HBASE-19148
> HBASE-18307
> HBASE-17314
> HBASE-15784
> HBASE-15027
> HBASE-14906
> HBASE-14521
> {quote}
> More detail later from [~mdrob]:
> {quote}
> would like to see notes that:
> hbase.master.cleaner.interval changed from 1 min to 10 min
> MasterProcedureConstants.MASTER_PROCEDURE_THREADS defaults to CPU/4 instead of CPU
> hbase.rpc.server.nativetransport renamed to hbase.netty.nativetransport
> hbase.netty.rpc.server.worker.count renamed to base.netty.worker.count
> hbase.hfile.compactions.discharger.interval renamed to hbase.hfile.compaction.discharger.interval
> hbase.hregion.percolumnfamilyflush.size.lower.bound removed at site level, but can still
be applied at table level
> hbase.client.reties.number now counts the total number of retries, not the total number
of tries
> {quote}



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

Mime
View raw message