[
https://issues.apache.org/jira/browse/HBASE-29461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Geiszler updated HBASE-29461:
-----------------------------------
Status: Patch Available (was: In Progress)
> Alphabetize the list of variables that can be dynamically configured
> --------------------------------------------------------------------
>
> Key: HBASE-29461
> URL: https://issues.apache.org/jira/browse/HBASE-29461
> Project: HBase
> Issue Type: Improvement
> Components: documentation
> Reporter: Kevin Geiszler
> Assignee: Kevin Geiszler
> Priority: Trivial
> Labels: pull-request-available
>
> The [Dynamic Configuration|https://hbase.apache.org/book.html#dyn_config]
> section of the HBase documentation has a list of variables that can be
> configured dynamically. It would be easier to find a variable in this list
> if the list were alphabetized. Yes, Command/CTRL + F can be used for
> searching, but the user may end up having the search bring them to a
> different part of the document before _maybe_ seeing the variable in the
> Dynamic Configuration list. The list is currently as follows:
>
> {code:java}
> | hbase.ipc.server.fallback-to-simple-auth-allowed
> | hbase.cleaner.scan.dir.concurrent.size
> | hbase.coprocessor.master.classes
> | hbase.coprocessor.region.classes
> | hbase.coprocessor.regionserver.classes
> | hbase.coprocessor.user.region.classes
> | hbase.regionserver.thread.compaction.large
> | hbase.regionserver.thread.compaction.small
> | hbase.regionserver.thread.split
> | hbase.regionserver.throughput.controller
> | hbase.regionserver.thread.hfilecleaner.throttle
> | hbase.regionserver.hfilecleaner.large.queue.size
> | hbase.regionserver.hfilecleaner.small.queue.size
> | hbase.regionserver.hfilecleaner.large.thread.count
> | hbase.regionserver.hfilecleaner.small.thread.count
> | hbase.regionserver.hfilecleaner.thread.timeout.msec
> | hbase.regionserver.hfilecleaner.thread.check.interval.msec
> | hbase.regionserver.flush.throughput.controller
> | hbase.hstore.compaction.max.size
> | hbase.hstore.compaction.max.size.offpeak
> | hbase.hstore.compaction.min.size
> | hbase.hstore.compaction.min
> | hbase.hstore.compaction.max
> | hbase.hstore.compaction.ratio
> | hbase.hstore.compaction.ratio.offpeak
> | hbase.regionserver.thread.compaction.throttle
> | hbase.hregion.majorcompaction
> | hbase.hregion.majorcompaction.jitter
> | hbase.hstore.min.locality.to.skip.major.compact
> | hbase.hstore.compaction.date.tiered.max.storefile.age.millis
> | hbase.hstore.compaction.date.tiered.incoming.window.min
> | hbase.hstore.compaction.date.tiered.window.policy.class
> | hbase.hstore.compaction.date.tiered.single.output.for.minor.compaction
> | hbase.hstore.compaction.date.tiered.window.factory.class
> | hbase.offpeak.start.hour
> | hbase.offpeak.end.hour
> | hbase.oldwals.cleaner.thread.size
> | hbase.oldwals.cleaner.thread.timeout.msec
> | hbase.oldwals.cleaner.thread.check.interval.msec
> | hbase.procedure.worker.keep.alive.time.msec
> | hbase.procedure.worker.add.stuck.percentage
> | hbase.procedure.worker.monitor.interval.msec
> | hbase.procedure.worker.stuck.threshold.msec
> | hbase.regions.slop
> | hbase.regions.overallSlop
> | hbase.balancer.tablesOnMaster
> | hbase.balancer.tablesOnMaster.systemTablesOnly
> | hbase.util.ip.to.rack.determiner
> | hbase.ipc.server.max.callqueue.length
> | hbase.ipc.server.priority.max.callqueue.length
> | hbase.ipc.server.callqueue.type
> | hbase.ipc.server.callqueue.codel.target.delay
> | hbase.ipc.server.callqueue.codel.interval
> | hbase.ipc.server.callqueue.codel.lifo.threshold
> | hbase.master.balancer.stochastic.maxSteps
> | hbase.master.balancer.stochastic.stepsPerRegion
> | hbase.master.balancer.stochastic.maxRunningTime
> | hbase.master.balancer.stochastic.runMaxSteps
> | hbase.master.balancer.stochastic.numRegionLoadsToRemember
> | hbase.master.loadbalance.bytable
> | hbase.master.balancer.stochastic.minCostNeedBalance
> | hbase.master.balancer.stochastic.localityCost
> | hbase.master.balancer.stochastic.rackLocalityCost
> | hbase.master.balancer.stochastic.readRequestCost
> | hbase.master.balancer.stochastic.writeRequestCost
> | hbase.master.balancer.stochastic.memstoreSizeCost
> | hbase.master.balancer.stochastic.storefileSizeCost
> | hbase.master.balancer.stochastic.regionReplicaHostCostKey
> | hbase.master.balancer.stochastic.regionReplicaRackCostKey
> | hbase.master.balancer.stochastic.regionCountCost
> | hbase.master.balancer.stochastic.primaryRegionCountCost
> | hbase.master.balancer.stochastic.moveCost
> | hbase.master.balancer.stochastic.moveCost.offpeak
> | hbase.master.balancer.stochastic.maxMovePercent
> | hbase.master.balancer.stochastic.tableSkewCost
> | hbase.master.regions.recovery.check.interval
> | hbase.regions.recovery.store.file.ref.count
> | hbase.rsgroup.fallback.enable {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
