hbase最新版本配置属性

1. 说明

hbase的配置属性大全
hbase版本基于 hbase-3.0.0-alpha-4

<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!--
/*** Licensed to the Apache Software Foundation (ASF) under one* or more contributor license agreements.  See the NOTICE file* distributed with this work for additional information* regarding copyright ownership.  The ASF licenses this file* to you under the Apache License, Version 2.0 (the* "License"); you may not use this file except in compliance* with the License.  You may obtain a copy of the License at**     http://www.apache.org/licenses/LICENSE-2.0** Unless required by applicable law or agreed to in writing, software* distributed under the License is distributed on an "AS IS" BASIS,* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.* See the License for the specific language governing permissions and* limitations under the License.*/
--><!--
OVERVIEWThe important configs. are listed near the top.  You should change
at least the setting for hbase.tmp.dir.  Other settings will change
dependent on whether you are running hbase in standalone mode or
distributed.  See the hbase reference guide for requirements and
guidance making configuration.This file does not contain all possible configurations.  The file would be
much larger if it carried everything. The absent configurations will only be
found through source code reading.  The idea is that such configurations are
exotic and only those who would go to the trouble of reading a particular
section in the code would be knowledgeable or invested enough in ever wanting
to alter such configurations, so we do not list them here.  Listing all
possible configurations would overwhelm and obscure the important.
--><configuration><!--Configs you will likely change are listed here at the top of the file.--><property ><name>hbase.tmp.dir</name><value>${java.io.tmpdir}/hbase-${user.name}</value><description>Temporary directory on the local filesystem.Change this setting to point to a location more permanentthan '/tmp', the usual resolve for java.io.tmpdir, as the'/tmp' directory is cleared on machine restart.</description></property><property ><name>hbase.rootdir</name><value>${hbase.tmp.dir}/hbase</value><description>The directory shared by region servers and intowhich HBase persists.  The URL should be 'fully-qualified'to include the filesystem scheme.  For example, to specify theHDFS directory '/hbase' where the HDFS instance's namenode isrunning at namenode.example.org on port 9000, set this value to:hdfs://namenode.example.org:9000/hbase.  By default, we writeto whatever ${hbase.tmp.dir} is set too -- usually /tmp --so change this configuration or else all data will be lost onmachine restart.</description></property><property ><name>hbase.cluster.distributed</name><value>false</value><description>The mode the cluster will be in. Possible values arefalse for standalone mode and true for distributed mode.  Iffalse, startup will run all HBase and ZooKeeper daemons togetherin the one JVM.</description></property><property><name>hbase.zookeeper.quorum</name><!--Ideally we should be using a hostname here instead of IP address. Please refer tohttps://issues.apache.org/jira/browse/HBASE-23764 for why we switched to IP address. Should bechanged once we fix the underlying ZK issue.--><value>127.0.0.1</value><description>Comma separated list of servers in the ZooKeeper ensemble(This config. should have been named hbase.zookeeper.ensemble).For example, "host1.mydomain.com,host2.mydomain.com,host3.mydomain.com".By default this is set to localhost for local and pseudo-distributed modesof operation. For a fully-distributed setup, this should be set to a fulllist of ZooKeeper ensemble servers. If HBASE_MANAGES_ZK is set in hbase-env.shthis is the list of servers which hbase will start/stop ZooKeeper on aspart of cluster start/stop.  Client-side, we will take this list ofensemble members and put it together with the hbase.zookeeper.property.clientPortconfig. and pass it into zookeeper constructor as the connectStringparameter.</description></property><!--The above are the important configurations for getting hbase upand running --><property><name>zookeeper.recovery.retry.maxsleeptime</name><value>60000</value><description>Max sleep time before retry zookeeper operations in milliseconds,a max time is needed here so that sleep time won't grow unboundedly</description></property><property><name>hbase.local.dir</name><value>${hbase.tmp.dir}/local/</value><description>Directory on the local filesystem to be usedas a local storage.</description></property><!--Master configurations--><property ><name>hbase.master.port</name><value>16000</value><description>The port the HBase Master should bind to.</description></property><property><name>hbase.master.info.port</name><value>16010</value><description>The port for the HBase Master web UI.Set to -1 if you do not want a UI instance run.</description></property><property><name>hbase.master.info.bindAddress</name><value>0.0.0.0</value><description>The bind address for the HBase Master web UI</description></property><property><name>hbase.master.logcleaner.plugins</name><value>org.apache.hadoop.hbase.master.cleaner.TimeToLiveLogCleaner,org.apache.hadoop.hbase.master.cleaner.TimeToLiveProcedureWALCleaner,org.apache.hadoop.hbase.master.cleaner.TimeToLiveMasterLocalStoreWALCleaner</value><description>A comma-separated list of BaseLogCleanerDelegate invoked bythe LogsCleaner service. These WAL cleaners are called in order,so put the cleaner that prunes the most files in front. Toimplement your own BaseLogCleanerDelegate, just put it in HBase's classpathand add the fully qualified class name here. Always add the abovedefault log cleaners in the list.</description></property><property><name>hbase.master.logcleaner.ttl</name><value>600000</value><description>How long a WAL remain in the archive ({hbase.rootdir}/oldWALs) directory,after which it will be cleaned by a Master thread. The value is in milliseconds.</description></property><property><name>hbase.master.hfilecleaner.plugins</name><value>org.apache.hadoop.hbase.master.cleaner.TimeToLiveHFileCleaner,org.apache.hadoop.hbase.master.cleaner.TimeToLiveMasterLocalStoreHFileCleaner</value><description>A comma-separated list of BaseHFileCleanerDelegate invoked bythe HFileCleaner service. These HFiles cleaners are called in order,so put the cleaner that prunes the most files in front. Toimplement your own BaseHFileCleanerDelegate, just put it in HBase's classpathand add the fully qualified class name here. Always add the abovedefault hfile cleaners in the list as they will be overwritten inhbase-site.xml.</description></property><property><name>hbase.master.infoserver.redirect</name><value>true</value><description>Whether or not the Master listens to the Master webUI port (hbase.master.info.port) and redirects requests to the webUI server shared by the Master and RegionServer. Config. makessense when Master is serving Regions (not the default).</description></property><property><name>hbase.master.fileSplitTimeout</name><value>600000</value><description>Splitting a region, how long to wait on the file-splittingstep before aborting the attempt. Default: 600000. This setting usedto be known as hbase.regionserver.fileSplitTimeout in hbase-1.x.Split is now run master-side hence the rename (If a'hbase.master.fileSplitTimeout' setting found, will use it toprime the current 'hbase.master.fileSplitTimeout'Configuration.</description></property><!--RegionServer configurations--><property><name>hbase.regionserver.port</name><value>16020</value><description>The port the HBase RegionServer binds to.</description></property><property><name>hbase.regionserver.info.port</name><value>16030</value><description>The port for the HBase RegionServer web UISet to -1 if you do not want the RegionServer UI to run.</description></property><property><name>hbase.regionserver.info.bindAddress</name><value>0.0.0.0</value><description>The address for the HBase RegionServer web UI</description></property><property><name>hbase.regionserver.info.port.auto</name><value>false</value><description>Whether or not the Master or RegionServerUI should search for a port to bind to. Enables automatic portsearch if hbase.regionserver.info.port is already in use.Useful for testing, turned off by default.</description></property><property><name>hbase.regionserver.handler.count</name><value>30</value><description>Count of RPC Listener instances spun up on RegionServers.Same property is used by the Master for count of master handlers.Too many handlers can be counter-productive. Make it a multiple ofCPU count. If mostly read-only, handlers count close to cpu countdoes well. Start with twice the CPU count and tune from there.</description></property><property><name>hbase.ipc.server.callqueue.handler.factor</name><value>0.1</value><description>Factor to determine the number of call queues.A value of 0 means a single queue shared between all the handlers.A value of 1 means that each handler has its own queue.</description></property><property><name>hbase.ipc.server.callqueue.read.ratio</name><value>0</value><description>Split the call queues into read and write queues.The specified interval (which should be between 0.0 and 1.0)will be multiplied by the number of call queues.A value of 0 indicate to not split the call queues, meaning that both read and writerequests will be pushed to the same set of queues.A value lower than 0.5 means that there will be less read queues than write queues.A value of 0.5 means there will be the same number of read and write queues.A value greater than 0.5 means that there will be more read queues than write queues.A value of 1.0 means that all the queues except one are used to dispatch read requests.Example: Given the total number of call queues being 10a read.ratio of 0 means that: the 10 queues will contain both read/write requests.a read.ratio of 0.3 means that: 3 queues will contain only read requestsand 7 queues will contain only write requests.a read.ratio of 0.5 means that: 5 queues will contain only read requestsand 5 queues will contain only write requests.a read.ratio of 0.8 means that: 8 queues will contain only read requestsand 2 queues will contain only write requests.a read.ratio of 1 means that: 9 queues will contain only read requestsand 1 queues will contain only write requests.</description></property><property><name>hbase.ipc.server.callqueue.scan.ratio</name><value>0</value><description>Given the number of read call queues, calculated from the total numberof call queues multiplied by the callqueue.read.ratio, the scan.ratio propertywill split the read call queues into small-read and long-read queues.A value lower than 0.5 means that there will be less long-read queues than short-read queues.A value of 0.5 means that there will be the same number of short-read and long-read queues.A value greater than 0.5 means that there will be more long-read queues than short-read queuesA value of 0 or 1 indicate to use the same set of queues for gets and scans.Example: Given the total number of read call queues being 8a scan.ratio of 0 or 1 means that: 8 queues will contain both long and short read requests.a scan.ratio of 0.3 means that: 2 queues will contain only long-read requestsand 6 queues will contain only short-read requests.a scan.ratio of 0.5 means that: 4 queues will contain only long-read requestsand 4 queues will contain only short-read requests.a scan.ratio of 0.8 means that: 6 queues will contain only long-read requestsand 2 queues will contain only short-read requests.</description></property><property><name>hbase.regionserver.msginterval</name><value>3000</value><description>Interval between messages from the RegionServer to Masterin milliseconds.</description></property><property><name>hbase.regionserver.logroll.period</name><value>3600000</value><description>Period at which we will roll the commit log regardlessof how many edits it has.</description></property><property><name>hbase.regionserver.logroll.errors.tolerated</name><value>2</value><description>The number of consecutive WAL close errors we will allowbefore triggering a server abort.  A setting of 0 will cause theregion server to abort if closing the current WAL writer fails duringlog rolling.  Even a small value (2 or 3) will allow a region serverto ride over transient HDFS errors.</description></property><property><name>hbase.regionserver.global.memstore.size</name><value></value><description>Maximum size of all memstores in a region server before newupdates are blocked and flushes are forced. Defaults to 40% of heap (0.4).Updates are blocked and flushes are forced until size of all memstoresin a region server hits hbase.regionserver.global.memstore.size.lower.limit.The default value in this configuration has been intentionally left empty in order tohonor the old hbase.regionserver.global.memstore.upperLimit property if present.</description></property><property><name>hbase.regionserver.global.memstore.size.lower.limit</name><value></value><description>Maximum size of all memstores in a region server before flushesare forced. Defaults to 95% of hbase.regionserver.global.memstore.size(0.95). A 100% value for this value causes the minimum possible flushingto occur when updates are blocked due to memstore limiting. The defaultvalue in this configuration has been intentionally left empty in order tohonor the old hbase.regionserver.global.memstore.lowerLimit property ifpresent.</description></property><property><name>hbase.systemtables.compacting.memstore.type</name><value>NONE</value><description>Determines the type of memstore to be used for system tables likeMETA, namespace tables etc. By default NONE is the type and hence we use thedefault memstore for all the system tables. If we need to use compactingmemstore for system tables then set this property to BASIC/EAGER</description></property><property><name>hbase.regionserver.optionalcacheflushinterval</name><value>3600000</value><description>Maximum amount of time an edit lives in memory before being automatically flushed.Default 1 hour. Set it to 0 to disable automatic flushing.</description></property><property><name>hbase.regionserver.dns.interface</name><value>default</value><description>The name of the Network Interface from which a region servershould report its IP address.</description></property><property><name>hbase.regionserver.dns.nameserver</name><value>default</value><description>The host name or IP address of the name server (DNS)which a region server should use to determine the host name used by themaster for communication and display purposes.</description></property><property><name>hbase.regionserver.region.split.policy</name><value>org.apache.hadoop.hbase.regionserver.SteppingSplitPolicy</value><description>A split policy determines when a region should be split. The variousother split policies that are available currently are BusyRegionSplitPolicy,ConstantSizeRegionSplitPolicy, DisabledRegionSplitPolicy,DelimitedKeyPrefixRegionSplitPolicy, KeyPrefixRegionSplitPolicy, andSteppingSplitPolicy. DisabledRegionSplitPolicy blocks manual region splitting.</description></property><property><name>hbase.regionserver.regionSplitLimit</name><value>1000</value><description>Limit for the number of regions after which no more region splittingshould take place. This is not hard limit for the number of regionsbut acts as a guideline for the regionserver to stop splitting aftera certain limit. Default is set to 1000.</description></property><!--ZooKeeper configuration--><property><name>zookeeper.session.timeout</name><value>90000</value><description>ZooKeeper session timeout in milliseconds. It is used in two different ways.First, this value is used in the ZK client that HBase uses to connect to the ensemble.It is also used by HBase when it starts a ZK server and it is passed as the 'maxSessionTimeout'.See https://zookeeper.apache.org/doc/current/zookeeperProgrammers.html#ch_zkSessions.For example, if an HBase region server connects to a ZK ensemble that's also managedby HBase, then the session timeout will be the one specified by this configuration.But, a region server that connects to an ensemble managed with a different configurationwill be subjected that ensemble's maxSessionTimeout. So, even though HBase might proposeusing 90 seconds, the ensemble can have a max timeout lower than this and it will takeprecedence. The current default maxSessionTimeout that ZK ships with is 40 seconds, which is lower thanHBase's.</description></property><property><name>zookeeper.znode.parent</name><value>/hbase</value><description>Root ZNode for HBase in ZooKeeper. All of HBase's ZooKeeperfiles that are configured with a relative path will go under this node.By default, all of HBase's ZooKeeper file paths are configured with arelative path, so they will all go under this directory unless changed.</description></property><property><name>zookeeper.znode.acl.parent</name><value>acl</value><description>Root ZNode for access control lists.</description></property><property><name>hbase.zookeeper.dns.interface</name><value>default</value><description>The name of the Network Interface from which a ZooKeeper servershould report its IP address.</description></property><property><name>hbase.zookeeper.dns.nameserver</name><value>default</value><description>The host name or IP address of the name server (DNS)which a ZooKeeper server should use to determine the host name used by themaster for communication and display purposes.</description></property><!--The following three properties are used together to create the list ofhost:peer_port:leader_port quorum servers for ZooKeeper.--><property><name>hbase.zookeeper.peerport</name><value>2888</value><description>Port used by ZooKeeper peers to talk to each other.See https://zookeeper.apache.org/doc/r3.4.10/zookeeperStarted.html#sc_RunningReplicatedZooKeeperfor more information.</description></property><property><name>hbase.zookeeper.leaderport</name><value>3888</value><description>Port used by ZooKeeper for leader election.See https://zookeeper.apache.org/doc/r3.4.10/zookeeperStarted.html#sc_RunningReplicatedZooKeeperfor more information.</description></property><!-- End of properties used to generate ZooKeeper host:port quorum list. --><!--Beginning of properties that are directly mapped from ZooKeeper's zoo.cfg.All properties with an "hbase.zookeeper.property." prefix are converted forZooKeeper's configuration. Hence, if you want to add an option from zoo.cfg,e.g.  "initLimit=10" you would append the following to your configuration:<property><name>hbase.zookeeper.property.initLimit</name><value>10</value></property>--><property><name>hbase.zookeeper.property.initLimit</name><value>10</value><description>Property from ZooKeeper's config zoo.cfg.The number of ticks that the initial synchronization phase can take.</description></property><property><name>hbase.zookeeper.property.syncLimit</name><value>5</value><description>Property from ZooKeeper's config zoo.cfg.The number of ticks that can pass between sending a request and getting anacknowledgment.</description></property><property><name>hbase.zookeeper.property.dataDir</name><value>${hbase.tmp.dir}/zookeeper</value><description>Property from ZooKeeper's config zoo.cfg.The directory where the snapshot is stored.</description></property><property><name>hbase.zookeeper.property.clientPort</name><value>2181</value><description>Property from ZooKeeper's config zoo.cfg.The port at which the clients will connect.</description></property><property><name>hbase.zookeeper.property.maxClientCnxns</name><value>300</value><description>Property from ZooKeeper's config zoo.cfg.Limit on number of concurrent connections (at the socket level) that asingle client, identified by IP address, may make to a single member ofthe ZooKeeper ensemble. Set high to avoid zk connection issues runningstandalone and pseudo-distributed.</description></property><!-- End of properties that are directly mapped from ZooKeeper's zoo.cfg --><!--Client configurations--><property><name>hbase.client.write.buffer</name><value>2097152</value><description>Default size of the BufferedMutator write buffer in bytes.A bigger buffer takes more memory -- on both the client and serverside since server instantiates the passed write buffer to processit -- but a larger buffer size reduces the number of RPCs made.For an estimate of server-side memory-used, evaluatehbase.client.write.buffer * hbase.regionserver.handler.count</description></property><property><name>hbase.client.pause</name><value>100</value><description>General client pause value.  Used mostly as value to waitbefore running a retry of a failed get, region lookup, etc.See hbase.client.retries.number for description of how we backoff fromthis initial pause amount and how this pause works w/ retries.</description></property><property><name>hbase.client.pause.server.overloaded</name><value></value><description>Pause time when encountering an exception indicating aserver is overloaded, CallQueueTooBigException or CallDroppedException.Set this property to a higher value than hbase.client.pause if youobserve frequent CallQueueTooBigException or CallDroppedException from the sameRegionServer and the call queue there keeps filling up. This config used to becalled hbase.client.pause.cqtbe, which has been deprecated as of 2.5.0.</description></property><property><name>hbase.client.retries.number</name><value>15</value><description>Maximum retries.  Used as maximum for all retryableoperations such as the getting of a cell's value, starting a row update,etc.  Retry interval is a rough function based on hbase.client.pause.  Atfirst we retry at this interval but then with backoff, we pretty quickly reachretrying every ten seconds.  See HConstants#RETRY_BACKOFF for how the backupramps up.  Change this setting and hbase.client.pause to suit your workload.</description></property><property><name>hbase.client.max.total.tasks</name><value>100</value><description>The maximum number of concurrent mutation tasks a single HTable instance willsend to the cluster.</description></property><property><name>hbase.client.max.perserver.tasks</name><value>2</value><description>The maximum number of concurrent mutation tasks a single HTable instance willsend to a single region server.</description></property><property><name>hbase.client.max.perregion.tasks</name><value>1</value><description>The maximum number of concurrent mutation tasks the client willmaintain to a single Region. That is, if there is alreadyhbase.client.max.perregion.tasks writes in progress for this region, new putswon't be sent to this region until some writes finishes.</description></property><property><name>hbase.client.perserver.requests.threshold</name><value>2147483647</value><description>The max number of concurrent pending requests for one server in all client threads(process level). Exceeding requests will be thrown ServerTooBusyException immediately to preventuser's threads being occupied and blocked by only one slow region server. If you use a fixnumber of threads to access HBase in a synchronous way, set this to a suitable value which isrelated to the number of threads will help you. Seehttps://issues.apache.org/jira/browse/HBASE-16388 for details.</description></property><property><name>hbase.client.scanner.caching</name><value>2147483647</value><description>Number of rows that we try to fetch when calling nexton a scanner if it is not served from (local, client) memory. This configurationworks together with hbase.client.scanner.max.result.size to try and use thenetwork efficiently. The default value is Integer.MAX_VALUE by default so thatthe network will fill the chunk size defined by hbase.client.scanner.max.result.sizerather than be limited by a particular number of rows since the size of rows variestable to table. If you know ahead of time that you will not require more than a certainnumber of rows from a scan, this configuration should be set to that row limit viaScan#setCaching. Higher caching values will enable faster scanners but will eat up morememory and some calls of next may take longer and longer times when the cache is empty.Do not set this value such that the time between invocations is greater than the scannertimeout; i.e. hbase.client.scanner.timeout.period</description></property><property><name>hbase.client.keyvalue.maxsize</name><value>10485760</value><description>Specifies the combined maximum allowed size of a KeyValueinstance. This is to set an upper boundary for a single entry saved in astorage file. Since they cannot be split it helps avoiding that a regioncannot be split any further because the data is too large. It seems wiseto set this to a fraction of the maximum region size. Setting it to zeroor less disables the check.</description></property><property><name>hbase.server.keyvalue.maxsize</name><value>10485760</value><description>Maximum allowed size of an individual cell, inclusive of value and all keycomponents. A value of 0 or less disables the check.The default value is 10MB.This is a safety setting to protect the server from OOM situations.</description></property><property><name>hbase.client.scanner.timeout.period</name><value>60000</value><description>Client scanner lease period in milliseconds.</description></property><property><name>hbase.client.localityCheck.threadPoolSize</name><value>2</value></property><!--Miscellaneous configuration--><property><name>hbase.bulkload.retries.number</name><value>10</value><description>Maximum retries.  This is maximum number of iterationsto atomic bulk loads are attempted in the face of splitting operations0 means never give up.</description></property><property><name>hbase.compaction.after.bulkload.enable</name><value>false</value><description>Request Compaction after bulkload immediately.If bulkload is continuous, the triggered compactions may increase load,bring about performance side effect.</description></property><property><name>hbase.master.balancer.maxRitPercent</name><value>1.0</value><description>The max percent of regions in transition when balancing.The default value is 1.0. So there are no balancer throttling. If set this config to 0.01,It means that there are at most 1% regions in transition when balancing.Then the cluster's availability is at least 99% when balancing.</description></property><property><name>hbase.balancer.period</name><value>300000</value><description>Period at which the region balancer runs in the Master, inmilliseconds.</description></property><property><name>hbase.master.oldwals.dir.updater.period</name><value>300000</value><description>Period at which the oldWALs directory size calculator/updater will run in theMaster, in milliseconds.</description></property><property><name>hbase.regions.slop</name><value>0.2</value><description>The load balancer can trigger for several reasons. This value controls one ofthose reasons. Run the balancer if any regionserver has a region count outside the range ofaverage +/- (average * slop) regions.If the value of slop is negative, disable sloppiness checks. The balancer can still run forother reasons, but sloppiness will not be one of them.If the value of slop is 0, run the balancer if any server has a region count more than 1from the average.If the value of slop is 100, run the balancer if any server has a region count greater than101 times the average.The default value of this parameter is 0.2, which runs the balancer if any server has a regioncount less than 80% of the average, or greater than 120% of the average.Note that for the default StochasticLoadBalancer, this does not guarantee any balancingactions will be taken, but only that the balancer will attempt to run.</description></property><property><name>hbase.normalizer.period</name><value>300000</value><description>Period at which the region normalizer runs in the Master, inmilliseconds.</description></property><property><name>hbase.normalizer.split.enabled</name><value>true</value><description>Whether to split a region as part of normalization.</description></property><property><name>hbase.normalizer.merge.enabled</name><value>true</value><description>Whether to merge a region as part of normalization.</description></property><property><name>hbase.normalizer.merge.min.region.count</name><value>3</value><description>The minimum number of regions in a table to consider it for mergenormalization.</description></property><property><name>hbase.normalizer.merge.min_region_age.days</name><value>3</value><description>The minimum age for a region to be considered for a merge, in days.</description></property><property><name>hbase.normalizer.merge.min_region_size.mb</name><value>1</value><description>The minimum size for a region to be considered for a merge, in wholeMBs.</description></property><property><name>hbase.normalizer.merge.merge_request_max_number_of_regions</name><value>100</value><description>The maximum number of region count in a merge request for mergenormalization.</description></property><property><name>hbase.table.normalization.enabled</name><value>false</value><description>This config is used to set default behaviour of normalizer at table level.To override this at table level one can set NORMALIZATION_ENABLED at table descriptor leveland that property will be honored</description></property><property><name>hbase.server.thread.wakefrequency</name><value>10000</value><description>In master side, this config is the period used for FS related behaviors:checking if hdfs is out of safe mode, setting or checking hbase.version file,setting or checking hbase.id file. Using default value should be fine.In regionserver side, this config is used in several places: flushing check interval,compaction check interval, wal rolling check interval. Specially, admin can tuneflushing and compaction check interval by hbase.regionserver.flush.check.periodand hbase.regionserver.compaction.check.period. (in milliseconds)</description></property><property><name>hbase.regionserver.flush.check.period</name><value>${hbase.server.thread.wakefrequency}</value><description>It determines the flushing check period of PeriodicFlusher in regionserver.If unset, it uses hbase.server.thread.wakefrequency as default value.(in milliseconds)</description></property><property><name>hbase.regionserver.compaction.check.period</name><value>${hbase.server.thread.wakefrequency}</value><description>It determines the compaction check period of CompactionChecker in regionserver.If unset, it uses hbase.server.thread.wakefrequency as default value.(in milliseconds)</description></property><property><name>hbase.server.versionfile.writeattempts</name><value>3</value><description>How many times to retry attempting to write a version filebefore just aborting. Each attempt is separated by thehbase.server.thread.wakefrequency milliseconds.</description></property><property><name>hbase.hregion.memstore.flush.size</name><value>134217728</value><description>Memstore will be flushed to disk if size of the memstoreexceeds this number of bytes.  Value is checked by a thread that runsevery hbase.server.thread.wakefrequency.</description></property><property><name>hbase.hregion.percolumnfamilyflush.size.lower.bound.min</name><value>16777216</value><description>If FlushLargeStoresPolicy is used and there are multiple column families,then every time that we hit the total memstore limit, we find out all thecolumn families whose memstores exceed a "lower bound" and only flush themwhile retaining the others in memory. The "lower bound" will be"hbase.hregion.memstore.flush.size / column_family_number" by defaultunless value of this property is larger than that. If none of the familieshave their memstore size more than lower bound, all the memstores will beflushed (just as usual).</description></property><property><name>hbase.hregion.preclose.flush.size</name><value>5242880</value><description>If the memstores in a region are this size or larger when we goto close, run a "pre-flush" to clear out memstores before we put upthe region closed flag and take the region offline.  On close,a flush is run under the close flag to empty memory.  Duringthis time the region is offline and we are not taking on any writes.If the memstore content is large, this flush could take a long time tocomplete.  The preflush is meant to clean out the bulk of the memstorebefore putting up the close flag and taking the region offline so theflush that runs under the close flag has little to do.</description></property><property><name>hbase.hregion.memstore.block.multiplier</name><value>4</value><description>Block updates if memstore has hbase.hregion.memstore.block.multipliertimes hbase.hregion.memstore.flush.size bytes.  Useful preventingrunaway memstore during spikes in update traffic.  Without anupper-bound, memstore fills such that when it flushes theresultant flush files take a long time to compact or split, orworse, we OOME.</description></property><property><name>hbase.hregion.memstore.mslab.enabled</name><value>true</value><description>Enables the MemStore-Local Allocation Buffer,a feature which works to prevent heap fragmentation underheavy write loads. This can reduce the frequency of stop-the-worldGC pauses on large heaps.</description></property><property><name>hbase.hregion.memstore.mslab.chunksize</name><value>2097152</value><description>The maximum byte size of a chunk in the MemStoreLAB. Unit: bytes</description></property><property><name>hbase.regionserver.offheap.global.memstore.size</name><value>0</value><description>The amount of off-heap memory all MemStores in a RegionServer may use.A value of 0 means that no off-heap memory will be used and all chunks in MSLABwill be HeapByteBuffer, otherwise the non-zero value means how many megabyte ofoff-heap memory will be used for chunks in MSLAB and all chunks in MSLAB will beDirectByteBuffer. Unit: megabytes.</description></property><property><name>hbase.hregion.memstore.mslab.max.allocation</name><value>262144</value><description>The maximal size of one allocation in the MemStoreLAB, if the desired bytesize exceed this threshold then it will be just allocated from JVM heap rather than MemStoreLAB.</description></property><property><name>hbase.hregion.max.filesize</name><value>10737418240</value><description>Maximum file size. If the sum of the sizes of a region's HFiles hasgrown to exceed this value, the region is split in two. There are two choices ofhow this option works, the first is when any store's size exceed the thresholdthen split, and the other is overall region's size exceed the threshold then split,it can be configed by hbase.hregion.split.overallfiles.</description></property><property><name>hbase.hregion.split.overallfiles</name><value>true</value><description>If we should sum overall region files size when check to split.</description></property><property><name>hbase.hregion.majorcompaction</name><value>604800000</value><description>Time between major compactions, expressed in milliseconds. Set to 0 to disabletime-based automatic major compactions. User-requested and size-based major compactions willstill run. This value is multiplied by hbase.hregion.majorcompaction.jitter to causecompaction to start at a somewhat-random time during a given window of time. The default valueis 7 days, expressed in milliseconds. If major compactions are causing disruption in yourenvironment, you can configure them to run at off-peak times for your deployment, or disabletime-based major compactions by setting this parameter to 0, and run major compactions in acron job or by another external mechanism.</description></property><property><name>hbase.hregion.majorcompaction.jitter</name><value>0.50</value><description>A multiplier applied to hbase.hregion.majorcompaction to cause compaction to occura given amount of time either side of hbase.hregion.majorcompaction. The smaller the number,the closer the compactions will happen to the hbase.hregion.majorcompactioninterval.</description></property><property><name>hbase.hstore.compactionThreshold</name><value>3</value><description> If more than or equal to this number of StoreFiles exist in any one Store(one StoreFile is written per flush of MemStore), a compaction is run to rewrite allStoreFiles into a single StoreFile. Larger values delay compaction, but when compaction doesoccur, it takes longer to complete.</description></property><property><name>hbase.regionserver.compaction.enabled</name><value>true</value><description>Enable/disable compactions on by setting true/false.We can further switch compactions dynamically with thecompaction_switch shell command.</description></property><property><name>hbase.hstore.flusher.count</name><value>2</value><description> The number of flush threads. With fewer threads, the MemStore flushes will bequeued. With more threads, the flushes will be executed in parallel, increasing the load onHDFS, and potentially causing more compactions. </description></property><property><name>hbase.hstore.blockingStoreFiles</name><value>16</value><description> If more than this number of StoreFiles exist in any one Store (one StoreFileis written per flush of MemStore), updates are blocked for this region until a compaction iscompleted, or until hbase.hstore.blockingWaitTime has been exceeded.</description></property><property><name>hbase.hstore.blockingWaitTime</name><value>90000</value><description> The time for which a region will block updates after reaching the StoreFile limitdefined by hbase.hstore.blockingStoreFiles. After this time has elapsed, the region will stopblocking updates even if a compaction has not been completed.</description></property><property><name>hbase.hstore.compaction.min</name><value></value><description>The minimum number of StoreFiles which must be eligible for compaction beforecompaction can run. The goal of tuning hbase.hstore.compaction.min is to avoid ending up withtoo many tiny StoreFiles to compact. Setting this value to 2 would cause a minor compactioneach time you have two StoreFiles in a Store, and this is probably not appropriate. If youset this value too high, all the other values will need to be adjusted accordingly. For mostcases, the default value is appropriate  (empty value here, results in 3 by code logic). Inprevious versions of HBase, the parameter hbase.hstore.compaction.min was namedhbase.hstore.compactionThreshold.</description></property><property><name>hbase.hstore.compaction.max</name><value>10</value><description>The maximum number of StoreFiles which will be selected for a single minorcompaction, regardless of the number of eligible StoreFiles. Effectively, the value ofhbase.hstore.compaction.max controls the length of time it takes a single compaction tocomplete. Setting it larger means that more StoreFiles are included in a compaction. For mostcases, the default value is appropriate.</description></property><property><name>hbase.hstore.compaction.min.size</name><value>134217728</value><description>A StoreFile (or a selection of StoreFiles, when using ExploringCompactionPolicy)smaller than this size will always be eligible for minor compaction.HFiles this size or larger are evaluated by hbase.hstore.compaction.ratio to determine ifthey are eligible. Because this limit represents the "automatic include" limit for allStoreFiles smaller than this value, this value may need to be reduced in write-heavyenvironments where many StoreFiles in the 1-2 MB range are being flushed, because everyStoreFile will be targeted for compaction and the resulting StoreFiles may still be under theminimum size and require further compaction. If this parameter is lowered, the ratio check istriggered more quickly. This addressed some issues seen in earlier versions of HBase butchanging this parameter is no longer necessary in most situations. Default: 128 MB expressedin bytes.</description></property><property><name>hbase.hstore.compaction.max.size</name><value>9223372036854775807</value><description>A StoreFile (or a selection of StoreFiles, when using ExploringCompactionPolicy)larger than this size will be excluded from compaction. The effect ofraising hbase.hstore.compaction.max.size is fewer, larger StoreFiles that do not getcompacted often. If you feel that compaction is happening too often without much benefit, youcan try raising this value. Default: the value of LONG.MAX_VALUE, expressed in bytes.</description></property><property><name>hbase.hstore.compaction.ratio</name><value>1.2F</value><description>For minor compaction, this ratio is used to determine whether a given StoreFilewhich is larger than hbase.hstore.compaction.min.size is eligible for compaction. Itseffect is to limit compaction of large StoreFiles. The value of hbase.hstore.compaction.ratiois expressed as a floating-point decimal. A large ratio, such as 10, will produce a singlegiant StoreFile. Conversely, a low value, such as .25, will produce behavior similar to theBigTable compaction algorithm, producing four StoreFiles. A moderate value of between 1.0 and1.4 is recommended. When tuning this value, you are balancing write costs with read costs.Raising the value (to something like 1.4) will have more write costs, because you willcompact larger StoreFiles. However, during reads, HBase will need to seek through fewerStoreFiles to accomplish the read. Consider this approach if you cannot take advantage ofBloom filters. Otherwise, you can lower this value to something like 1.0 to reduce thebackground cost of writes, and use Bloom filters to control the number of StoreFiles touchedduring reads. For most cases, the default value is appropriate.</description></property><property><name>hbase.hstore.compaction.ratio.offpeak</name><value>5.0F</value><description>Allows you to set a different (by default, more aggressive) ratio for determiningwhether larger StoreFiles are included in compactions during off-peak hours. Works in thesame way as hbase.hstore.compaction.ratio. Only applies if hbase.offpeak.start.hour andhbase.offpeak.end.hour are also enabled.</description></property><property><name>hbase.hstore.time.to.purge.deletes</name><value>0</value><description>The amount of time to delay purging of delete markers with future timestamps. Ifunset, or set to 0, all delete markers, including those with future timestamps, are purgedduring the next major compaction. Otherwise, a delete marker is kept until the major compactionwhich occurs after the marker's timestamp plus the value of this setting, in milliseconds.</description></property><property><name>hbase.offpeak.start.hour</name><value>-1</value><description>The start of off-peak hours, expressed as an integer between 0 and 23, inclusive.Set to -1 to disable off-peak.</description></property><property><name>hbase.offpeak.end.hour</name><value>-1</value><description>The end of off-peak hours, expressed as an integer between 0 and 23, inclusive. Setto -1 to disable off-peak.</description></property><property><name>hbase.regionserver.thread.compaction.throttle</name><value>2684354560</value><description>There are two different thread pools for compactions, one for large compactions andthe other for small compactions. This helps to keep compaction of lean tables (such ashbase:meta) fast. If a compaction is larger than this threshold, itgoes into the large compaction pool. In most cases, the default value is appropriate. Default:2 x hbase.hstore.compaction.max x hbase.hregion.memstore.flush.size (which defaults to 128MB).The value field assumes that the value of hbase.hregion.memstore.flush.size is unchanged fromthe default.</description></property><property><name>hbase.regionserver.majorcompaction.pagecache.drop</name><value>true</value><description>Specifies whether to drop pages read/written into the system page cache bymajor compactions. Setting it to true helps prevent major compactions frompolluting the page cache, which is almost always required, especially for clusterswith low/moderate memory to storage ratio.</description></property><property><name>hbase.regionserver.minorcompaction.pagecache.drop</name><value>true</value><description>Specifies whether to drop pages read/written into the system page cache byminor compactions. Setting it to true helps prevent minor compactions frompolluting the page cache, which is most beneficial on clusters with lowmemory to storage ratio or very write heavy clusters. You may want to set it tofalse under moderate to low write workload when bulk of the reads areon the most recently written data.</description></property><property><name>hbase.hstore.compaction.kv.max</name><value>10</value><description>The maximum number of KeyValues to read and then write in a batch when flushing orcompacting. Set this lower if you have big KeyValues and problems with Out Of MemoryExceptions Set this higher if you have wide, small rows. </description></property><property><name>hbase.storescanner.parallel.seek.enable</name><value>false</value><description>Enables StoreFileScanner parallel-seeking in StoreScanner,a feature which can reduce response latency under special conditions.</description></property><property><name>hbase.storescanner.parallel.seek.threads</name><value>10</value><description>The default thread pool size if parallel-seeking feature enabled.</description></property><property><name>hfile.block.cache.policy</name><value>LRU</value><description>The eviction policy for the L1 block cache (LRU or TinyLFU).</description></property><property><name>hfile.block.cache.size</name><value>0.4</value><description>Percentage of maximum heap (-Xmx setting) to allocate to block cacheused by a StoreFile. Default of 0.4 means allocate 40%.Set to 0 to disable but it's not recommended; you need at leastenough cache to hold the storefile indices.</description></property><property><name>hfile.block.index.cacheonwrite</name><value>false</value><description>This allows to put non-root multi-level index blocks into the blockcache at the time the index is being written.</description></property><property><name>hfile.index.block.max.size</name><value>131072</value><description>When the size of a leaf-level, intermediate-level, or root-levelindex block in a multi-level block index grows to this size, theblock is written out and a new block is started.</description></property><property><name>hbase.bucketcache.ioengine</name><value></value><description>Where to store the contents of the bucketcache. One of: offheap,file, files, mmap or pmem. If a file or files, set it to file(s):PATH_TO_FILE.mmap means the content will be in an mmaped file. Use mmap:PATH_TO_FILE. 'pmem'is bucket cache over a file on the persistent memory device.Use pmem:PATH_TO_FILE.See http://hbase.apache.org/book.html#offheap.blockcache for more information.</description></property><property><name>hbase.hstore.compaction.throughput.lower.bound</name><value>52428800</value><description>The target lower bound on aggregate compaction throughput, in bytes/sec. Allowsyou to tune the minimum available compaction throughput when thePressureAwareCompactionThroughputController throughput controller is active. (It is active bydefault.)</description></property><property><name>hbase.hstore.compaction.throughput.higher.bound</name><value>104857600</value><description>The target upper bound on aggregate compaction throughput, in bytes/sec. Allowsyou to control aggregate compaction throughput demand when thePressureAwareCompactionThroughputController throughput controller is active. (It is active bydefault.) The maximum throughput will be tuned between the lower and upper bounds whencompaction pressure is within the range [0.0, 1.0]. If compaction pressure is 1.0 or greaterthe higher bound will be ignored until pressure returns to the normal range.</description></property><property><name>hbase.bucketcache.size</name><value></value><description>It is the total capacity in megabytes of BucketCache. Default: 0.0</description></property><property><name>hbase.bucketcache.bucket.sizes</name><value></value><description>A comma-separated list of sizes for buckets for the bucketcache.Can be multiple sizes. List block sizes in order from smallest to largest.The sizes you use will depend on your data access patterns.Must be a multiple of 256 else you will run into'java.io.IOException: Invalid HFile block magic' when you go to read from cache.If you specify no values here, then you pick up the default bucketsizes setin code (See BucketAllocator#DEFAULT_BUCKET_SIZES).</description></property><property><name>hfile.format.version</name><value>3</value><description>The HFile format version to use for new files.Version 3 adds support for tags in hfiles (See http://hbase.apache.org/book.html#hbase.tags).Also see the configuration 'hbase.replication.rpc.codec'.</description></property><property><name>hfile.block.bloom.cacheonwrite</name><value>false</value><description>Enables cache-on-write for inline blocks of a compound Bloom filter.</description></property><property><name>io.storefile.bloom.block.size</name><value>131072</value><description>The size in bytes of a single block ("chunk") of a compound Bloomfilter. This size is approximate, because Bloom blocks can only beinserted at data block boundaries, and the number of keys per datablock varies.</description></property><property><name>hbase.rs.cacheblocksonwrite</name><value>false</value><description>Whether an HFile block should be added to the block cache when theblock is finished.</description></property><property><name>hbase.rpc.timeout</name><value>60000</value><description>This is for the RPC layer to define how long (millisecond) HBase client applicationstake for a remote call to time out. It uses pings to check connectionsbut will eventually throw a TimeoutException.</description></property><property><name>hbase.client.operation.timeout</name><value>1200000</value><description>Operation timeout is a top-level restriction (millisecond) that makes sure ablocking operation in Table will not be blocked more than this. In each operation, if rpcrequest fails because of timeout or other reason, it will retry until success or throwRetriesExhaustedException. But if the total time being blocking reach the operation timeoutbefore retries exhausted, it will break early and throw SocketTimeoutException.</description></property><property><name>hbase.cells.scanned.per.heartbeat.check</name><value>10000</value><description>The number of cells scanned in between heartbeat checks. Heartbeatchecks occur during the processing of scans to determine whether or not theserver should stop scanning in order to send back a heartbeat message to theclient. Heartbeat messages are used to keep the client-server connection aliveduring long running scans. Small values mean that the heartbeat checks willoccur more often and thus will provide a tighter bound on the execution time ofthe scan. Larger values mean that the heartbeat checks occur less frequently</description></property><property><name>hbase.rpc.shortoperation.timeout</name><value>10000</value><description>This is another version of "hbase.rpc.timeout". For those RPC operationwithin cluster, we rely on this configuration to set a short timeout limitationfor short operation. For example, short rpc timeout for region server's tryingto report to active master can benefit quicker master failover process.</description></property><property><name>hbase.ipc.client.tcpnodelay</name><value>true</value><description>Set no delay on rpc socket connections.  Seehttp://docs.oracle.com/javase/1.5.0/docs/api/java/net/Socket.html#getTcpNoDelay()</description></property><property><name>hbase.unsafe.regionserver.hostname</name><value></value><description>This config is for experts: don't set its value unless you really know what you are doing.When set to a non-empty value, this represents the (external facing) hostname for the underlying server.See https://issues.apache.org/jira/browse/HBASE-12954 for details.</description></property><property><name>hbase.unsafe.regionserver.hostname.disable.master.reversedns</name><value>false</value><description>This config is for experts: don't set its value unless you really know what you are doing.When set to true, regionserver will use the current node hostname for the servername and HMaster willskip reverse DNS lookup and use the hostname sent by regionserver instead. Note that this config andhbase.unsafe.regionserver.hostname are mutually exclusive. See https://issues.apache.org/jira/browse/HBASE-18226for more details.</description></property><!-- The following properties configure authentication information forHBase processes when using Kerberos security.  There are no defaultvalues, included here for documentation purposes --><property><name>hbase.master.keytab.file</name><value></value><description>Full path to the kerberos keytab file to use for logging inthe configured HMaster server principal.</description></property><property><name>hbase.master.kerberos.principal</name><value></value><description>Ex. "hbase/_HOST@EXAMPLE.COM".  The kerberos principal namethat should be used to run the HMaster process.  The principal name shouldbe in the form: user/hostname@DOMAIN.  If "_HOST" is used as the hostnameportion, it will be replaced with the actual hostname of the runninginstance.</description></property><property><name>hbase.regionserver.keytab.file</name><value></value><description>Full path to the kerberos keytab file to use for logging inthe configured HRegionServer server principal.</description></property><property><name>hbase.regionserver.kerberos.principal</name><value></value><description>Ex. "hbase/_HOST@EXAMPLE.COM".  The kerberos principal namethat should be used to run the HRegionServer process.  The principal nameshould be in the form: user/hostname@DOMAIN.  If "_HOST" is used as thehostname portion, it will be replaced with the actual hostname of therunning instance.  An entry for this principal must exist in the filespecified in hbase.regionserver.keytab.file</description></property><!-- Additional configuration specific to HBase security --><property><name>hadoop.policy.file</name><value>hbase-policy.xml</value><description>The policy configuration file used by RPC servers to makeauthorization decisions on client requests.  Only used when HBasesecurity is enabled.</description></property><property><name>hbase.superuser</name><value></value><description>List of users or groups (comma-separated), who are allowedfull privileges, regardless of stored ACLs, across the cluster.Only used when HBase security is enabled.</description></property><property><name>hbase.auth.key.update.interval</name><value>86400000</value><description>The update interval for master key for authentication tokensin servers in milliseconds.  Only used when HBase security is enabled.</description></property><property><name>hbase.auth.token.max.lifetime</name><value>604800000</value><description>The maximum lifetime in milliseconds after which anauthentication token expires.  Only used when HBase security is enabled.</description></property><property><name>hbase.ipc.client.fallback-to-simple-auth-allowed</name><value>false</value><description>When a client is configured to attempt a secure connection, but attempts toconnect to an insecure server, that server may instruct the client toswitch to SASL SIMPLE (unsecure) authentication. This setting controlswhether or not the client will accept this instruction from the server.When false (the default), the client will not allow the fallback to SIMPLEauthentication, and will abort the connection.</description></property><property><name>hbase.ipc.server.fallback-to-simple-auth-allowed</name><value>false</value><description>When a server is configured to require secure connections, it willreject connection attempts from clients using SASL SIMPLE (unsecure) authentication.This setting allows secure servers to accept SASL SIMPLE connections from clientswhen the client requests.  When false (the default), the server will not allow the fallbackto SIMPLE authentication, and will reject the connection.  WARNING: This setting should ONLYbe used as a temporary measure while converting clients over to secure authentication.  ItMUST BE DISABLED for secure operation.</description></property><property><name>hbase.unsafe.client.kerberos.hostname.disable.reversedns</name><value>false</value><description>This config is for experts: don't set its value unless you really know what you are doing.When set to true, HBase client using SASL Kerberos will skip reverse DNS lookup and use providedhostname of the destination for the principal instead. See https://issues.apache.org/jira/browse/HBASE-25665for more details.</description></property><property><name>hbase.display.keys</name><value>true</value><description>When this is set to true the webUI and such will display all start/end keysas part of the table details, region names, etc. When this is set to false,the keys are hidden.</description></property><property><name>hbase.coprocessor.enabled</name><value>true</value><description>Enables or disables coprocessor loading. If 'false'(disabled), any other coprocessor related configuration will be ignored.</description></property><property><name>hbase.coprocessor.user.enabled</name><value>true</value><description>Enables or disables user (aka. table) coprocessor loading.If 'false' (disabled), any table coprocessor attributes in tabledescriptors will be ignored. If "hbase.coprocessor.enabled" is 'false'this setting has no effect.</description></property><property><name>hbase.coprocessor.region.classes</name><value></value><description>A comma-separated list of region observer or endpoint coprocessorsthat are loaded by default on all tables. For any override coprocessor method,these classes will be called in order. After implementing your own Coprocessor,add it to HBase's classpath and add the fully qualified class name here.A coprocessor can also be loaded on demand by setting HTableDescriptor or theHBase shell.</description></property><property><name>hbase.coprocessor.master.classes</name><value></value><description>A comma-separated list oforg.apache.hadoop.hbase.coprocessor.MasterObserver coprocessors that areloaded by default on the active HMaster process. For any implementedcoprocessor methods, the listed classes will be called in order. Afterimplementing your own MasterObserver, just put it in HBase's classpathand add the fully qualified class name here.</description></property><property><name>hbase.coprocessor.abortonerror</name><value>true</value><description>Set to true to cause the hosting server (master or regionserver)to abort if a coprocessor fails to load, fails to initialize, or throws anunexpected Throwable object. Setting this to false will allow the server tocontinue execution but the system wide state of the coprocessor in questionwill become inconsistent as it will be properly executing in only a subsetof servers, so this is most useful for debugging only.</description></property><property><name>hbase.rest.port</name><value>8080</value><description>The port for the HBase REST server.</description></property><property><name>hbase.rest.readonly</name><value>false</value><description>Defines the mode the REST server will be started in. Possible values are:false: All HTTP methods are permitted - GET/PUT/POST/DELETE.true: Only the GET method is permitted.</description></property><property><name>hbase.rest.threads.max</name><value>100</value><description>The maximum number of threads of the REST server thread pool.Threads in the pool are reused to process REST requests. Thiscontrols the maximum number of requests processed concurrently.It may help to control the memory used by the REST server toavoid OOM issues. If the thread pool is full, incoming requestswill be queued up and wait for some free threads.</description></property><property><name>hbase.rest.threads.min</name><value>2</value><description>The minimum number of threads of the REST server thread pool.The thread pool always has at least these number of threads sothe REST server is ready to serve incoming requests.</description></property><property><name>hbase.rest.support.proxyuser</name><value>false</value><description>Enables running the REST server to support proxy-user mode.</description></property><property skipInDoc="true"><name>hbase.defaults.for.version</name><value>@@@VERSION@@@</value><description>This defaults file was compiled for version ${project.version}. This variable is usedto make sure that a user doesn't have an old version of hbase-default.xml on theclasspath.</description></property><property><name>hbase.defaults.for.version.skip</name><value>false</value><description>Set to true to skip the 'hbase.defaults.for.version' check.Setting this to true can be useful in contexts other thanthe other side of a maven generation; i.e. running in anIDE.  You'll want to set this boolean to true to avoidseeing the RuntimeException complaint: "hbase-default.xml fileseems to be for and old version of HBase (\${hbase.version}), thisversion is X.X.X-SNAPSHOT"</description></property><property><name>hbase.table.lock.enable</name><value>true</value><description>Set to true to enable locking the table in zookeeper for schema change operations.Table locking from master prevents concurrent schema modifications to corrupt tablestate.</description></property><property><name>hbase.table.max.rowsize</name><value>1073741824</value><description>Maximum size of single row in bytes (default is 1 Gb) for Get'tingor Scan'ning without in-row scan flag set. If row size exceeds this limitRowTooBigException is thrown to client.</description></property><property><name>hbase.thrift.minWorkerThreads</name><value>16</value><description>The "core size" of the thread pool. New threads are created on everyconnection until this many threads are created.</description></property><property><name>hbase.thrift.maxWorkerThreads</name><value>1000</value><description>The maximum size of the thread pool. When the pending request queueoverflows, new threads are created until their number reaches this number.After that, the server starts dropping connections.</description></property><property><name>hbase.thrift.maxQueuedRequests</name><value>1000</value><description>The maximum number of pending Thrift connections waiting in the queue. Ifthere are no idle threads in the pool, the server queues requests. Onlywhen the queue overflows, new threads are added, up tohbase.thrift.maxQueuedRequests threads.</description></property><property><name>hbase.regionserver.thrift.framed</name><value>false</value><description>Use Thrift TFramedTransport on the server side.This is the recommended transport for thrift servers and requires a similar settingon the client side. Changing this to false will select the default transport,vulnerable to DoS when malformed requests are issued due to THRIFT-601.</description></property><property><name>hbase.regionserver.thrift.framed.max_frame_size_in_mb</name><value>2</value><description>Default frame size when using framed transport, in MB</description></property><property><name>hbase.regionserver.thrift.compact</name><value>false</value><description>Use Thrift TCompactProtocol binary serialization protocol.</description></property><property><name>hbase.rootdir.perms</name><value>700</value><description>FS Permissions for the root data subdirectory in a secure (kerberos) setup.When master starts, it creates the rootdir with this permissions or sets the permissionsif it does not match.</description></property><property><name>hbase.wal.dir.perms</name><value>700</value><description>FS Permissions for the root WAL directory in a secure(kerberos) setup.When master starts, it creates the WAL dir with this permissions or sets the permissionsif it does not match.</description></property><property><name>hbase.data.umask.enable</name><value>false</value><description>Enable, if true, that file permissions should be assignedto the files written by the regionserver</description></property><property><name>hbase.data.umask</name><value>000</value><description>File permissions that should be used to write datafiles when hbase.data.umask.enable is true</description></property><property><name>hbase.snapshot.enabled</name><value>true</value><description>Set to true to allow snapshots to be taken / restored / cloned.</description></property><property><name>hbase.snapshot.restore.take.failsafe.snapshot</name><value>true</value><description>Set to true to take a snapshot before the restore operation.The snapshot taken will be used in case of failure, to restore the previous state.At the end of the restore operation this snapshot will be deleted</description></property><property><name>hbase.snapshot.restore.failsafe.name</name><value>hbase-failsafe-{snapshot.name}-{restore.timestamp}</value><description>Name of the failsafe snapshot taken by the restore operation.You can use the {snapshot.name}, {table.name} and {restore.timestamp} variablesto create a name based on what you are restoring.</description></property><property><name>hbase.snapshot.working.dir</name><value></value><description>Location where the snapshotting process will occur. The location of thecompleted snapshots will not change, but the temporary directory where the snapshotprocess occurs will be set to this location. This can be a separate filesystem thanthe root directory, for performance increase purposes. See HBASE-21098 for moreinformation</description></property><property><name>hbase.server.compactchecker.interval.multiplier</name><value>1000</value><description>The number that determines how often we scan to see if compaction is necessary.Normally, compactions are done after some events (such as memstore flush), but ifregion didn't receive a lot of writes for some time, or due to different compactionpolicies, it may be necessary to check it periodically. The interval between checks ishbase.server.compactchecker.interval.multiplier multiplied byhbase.server.thread.wakefrequency.</description></property><property><name>hbase.lease.recovery.timeout</name><value>900000</value><description>How long we wait on dfs lease recovery in total before giving up.</description></property><property><name>hbase.lease.recovery.dfs.timeout</name><value>64000</value><description>How long between dfs recover lease invocations. Should be larger than the sum ofthe time it takes for the namenode to issue a block recovery command as part ofdatanode; dfs.heartbeat.interval and the time it takes for the primarydatanode, performing block recovery to timeout on a dead datanode; usuallydfs.client.socket-timeout. See the end of HBASE-8389 for more.</description></property><property><name>hbase.column.max.version</name><value>1</value><description>New column family descriptors will use this value as the default number of versionsto keep.</description></property><property><name>dfs.client.read.shortcircuit</name><value></value><description>If set to true, this configuration parameter enables short-circuit localreads.</description></property><property><name>dfs.domain.socket.path</name><value></value><description>This is a path to a UNIX domain socket that will be used forcommunication between the DataNode and local HDFS clients, ifdfs.client.read.shortcircuit is set to true. If the string "_PORT" ispresent in this path, it will be replaced by the TCP port of the DataNode.Be careful about permissions for the directory that hosts the shareddomain socket; dfsclient will complain if open to other users than the HBase user.</description></property><property><name>hbase.dfs.client.read.shortcircuit.buffer.size</name><value>131072</value><description>If the DFSClient configurationdfs.client.read.shortcircuit.buffer.size is unset, we willuse what is configured here as the short circuit read defaultdirect byte buffer size. DFSClient native default is 1MB; HBasekeeps its HDFS files open so number of file blocks * 1MB soonstarts to add up and threaten OOME because of a shortage ofdirect memory.  So, we set it down from the default.  Makeit > the default hbase block size set in the HColumnDescriptorwhich is usually 64k.</description></property><property><name>hbase.regionserver.checksum.verify</name><value>true</value><description>If set to true (the default), HBase verifies the checksums for hfileblocks. HBase writes checksums inline with the data when it writes outhfiles. HDFS (as of this writing) writes checksums to a separate filethan the data file necessitating extra seeks.  Setting this flag savessome on i/o.  Checksum verification by HDFS will be internally disabledon hfile streams when this flag is set.  If the hbase-checksum verificationfails, we will switch back to using HDFS checksums (so do not disable HDFSchecksums!  And besides this feature applies to hfiles only, not to WALs).If this parameter is set to false, then hbase will not verify any checksums,instead it will depend on checksum verification being done in the HDFS client.</description></property><property><name>hbase.hstore.bytes.per.checksum</name><value>16384</value><description>Number of bytes in a newly created checksum chunk for HBase-levelchecksums in hfile blocks.</description></property><property><name>hbase.hstore.checksum.algorithm</name><value>CRC32C</value><description>Name of an algorithm that is used to compute checksums. Possible valuesare NULL, CRC32, CRC32C.</description></property><property><name>hbase.client.scanner.max.result.size</name><value>2097152</value><description>Maximum number of bytes returned when calling a scanner's next method.Note that when a single row is larger than this limit the row is still returned completely.The default value is 2MB, which is good for 1ge networks.With faster and/or high latency networks this value should be increased.</description></property><property><name>hbase.server.scanner.max.result.size</name><value>104857600</value><description>Maximum number of bytes returned when calling a scanner's next method.Note that when a single row is larger than this limit the row is still returned completely.The default value is 100MB.This is a safety setting to protect the server from OOM situations.</description></property><property><name>hbase.status.published</name><value>false</value><description>This setting activates the publication by the master of the status of the region server.When a region server dies and its recovery starts, the master will push this informationto the client application, to let them cut the connection immediately instead of waitingfor a timeout.</description></property><property><name>hbase.status.publisher.class</name><value>org.apache.hadoop.hbase.master.ClusterStatusPublisher$MulticastPublisher</value><description>Implementation of the status publication with a multicast message.</description></property><property><name>hbase.status.listener.class</name><value>org.apache.hadoop.hbase.client.ClusterStatusListener$MulticastListener</value><description>Implementation of the status listener with a multicast message.</description></property><property><name>hbase.status.multicast.address.ip</name><value>226.1.1.3</value><description>Multicast address to use for the status publication by multicast.</description></property><property><name>hbase.status.multicast.address.port</name><value>16100</value><description>Multicast port to use for the status publication by multicast.</description></property><property><name>hbase.dynamic.jars.dir</name><value>${hbase.rootdir}/lib</value><description>The directory from which the custom filter JARs can be loadeddynamically by the region server without the need to restart. However,an already loaded filter/co-processor class would not be un-loaded. SeeHBASE-1936 for more details.Does not apply to coprocessors.</description></property><property><name>hbase.security.authentication</name><value>simple</value><description>Controls whether or not secure authentication is enabled for HBase.Possible values are 'simple' (no authentication), and 'kerberos'.</description></property><property><name>hbase.rest.filter.classes</name><value>org.apache.hadoop.hbase.rest.filter.GzipFilter</value><description>Servlet filters for REST service.</description></property><property><name>hbase.master.loadbalancer.class</name><value>org.apache.hadoop.hbase.master.balancer.StochasticLoadBalancer</value><description>Class used to execute the regions balancing when the period occurs.See the class comment for more on how it workshttp://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/master/balancer/StochasticLoadBalancer.htmlIt replaces the DefaultLoadBalancer as the default (since renamedas the SimpleLoadBalancer).</description></property><property><name>hbase.master.loadbalance.bytable</name><value>false</value><description>Factor Table name when the balancer runs.Default: false.</description></property><property><name>hbase.master.normalizer.class</name><value>org.apache.hadoop.hbase.master.normalizer.SimpleRegionNormalizer</value><description>Class used to execute the region normalization when the period occurs.See the class comment for more on how it workshttp://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/master/normalizer/SimpleRegionNormalizer.html</description></property>
<property><name>hbase.rest.csrf.enabled</name><value>false</value><description>Set to true to enable protection against cross-site request forgery (CSRF)</description>
</property>
<property><name>hbase.rest-csrf.browser-useragents-regex</name><value>^Mozilla.*,^Opera.*</value><description>A comma-separated list of regular expressions used to match against an HTTPrequest's User-Agent header when protection against cross-site requestforgery (CSRF) is enabled for REST server by settinghbase.rest.csrf.enabled to true.  If the incoming User-Agent matchesany of these regular expressions, then the request is considered to be sentby a browser, and therefore CSRF prevention is enforced.  If the request'sUser-Agent does not match any of these regular expressions, then the requestis considered to be sent by something other than a browser, such as scriptedautomation.  In this case, CSRF is not a potential attack vector, sothe prevention is not enforced.  This helps achieve backwards-compatibilitywith existing automation that has not been updated to send the CSRFprevention header.</description>
</property><property><name>hbase.security.exec.permission.checks</name><value>false</value><description>If this setting is enabled and ACL based access control is active (theAccessController coprocessor is installed either as a system coprocessoror on a table as a table coprocessor) then you must grant all relevantusers EXEC privilege if they require the ability to execute coprocessorendpoint calls. EXEC privilege, like any other permission, can begranted globally to a user, or to a user on a per table or per namespacebasis. For more information on coprocessor endpoints, see the coprocessorsection of the HBase online manual. For more information on granting orrevoking permissions using the AccessController, see the securitysection of the HBase online manual.</description></property><property><name>hbase.procedure.regionserver.classes</name><value></value><description>A comma-separated list oforg.apache.hadoop.hbase.procedure.RegionServerProcedureManager procedure managers that areloaded by default on the active HRegionServer process. The lifecycle methods (init/start/stop)will be called by the active HRegionServer process to perform the specific globally barrieredprocedure. After implementing your own RegionServerProcedureManager, just put it inHBase's classpath and add the fully qualified class name here.</description></property><property><name>hbase.procedure.master.classes</name><value></value><description>A comma-separated list oforg.apache.hadoop.hbase.procedure.MasterProcedureManager procedure managers that areloaded by default on the active HMaster process. A procedure is identified by its signature andusers can use the signature and an instant name to trigger an execution of a globally barrieredprocedure. After implementing your own MasterProcedureManager, just put it in HBase's classpathand add the fully qualified class name here.</description></property><property><name>hbase.coordinated.state.manager.class</name><value>org.apache.hadoop.hbase.coordination.ZkCoordinatedStateManager</value><description>Fully qualified name of class implementing coordinated state manager.</description></property><property><name>hbase.regionserver.storefile.refresh.period</name><value>0</value><description>The period (in milliseconds) for refreshing the store files for the secondary regions. 0means this feature is disabled. Secondary regions sees new files (from flushes andcompactions) from primary once the secondary region refreshes the list of files in theregion (there is no notification mechanism). But too frequent refreshes might causeextra Namenode pressure. If the files cannot be refreshed for longer than HFile TTL(hbase.master.hfilecleaner.ttl) the requests are rejected. Configuring HFile TTL to a largervalue is also recommended with this setting.</description></property><property><name>hbase.region.replica.replication.enabled</name><value>false</value><description>Whether asynchronous WAL replication to the secondary region replicas is enabled or not.We have a separated implementation for replicating the WAL without using the generalinter-cluster replication framework, so now we will not add any replication peers.</description></property><property><name>hbase.http.filter.initializers</name><value>org.apache.hadoop.hbase.http.lib.StaticUserWebFilter</value><description>A comma separated list of class names. Each class in the list must extendorg.apache.hadoop.hbase.http.FilterInitializer. The corresponding Filter willbe initialized. Then, the Filter will be applied to all user facing jspand servlet web pages.The ordering of the list defines the ordering of the filters.The default StaticUserWebFilter add a user principal as defined by thehbase.http.staticuser.user property.</description></property><property><name>hbase.security.visibility.mutations.checkauths</name><value>false</value><description>This property if enabled, will check whether the labels in the visibilityexpression are associated with the user issuing the mutation</description></property><property><name>hbase.http.max.threads</name><value>16</value><description>The maximum number of threads that the HTTP Server will create in itsThreadPool.</description></property><property><name>hbase.http.metrics.servlets</name><value>jmx,metrics,prometheus</value><description>Comma separated list of servlet names to enable for metrics collection. Supportedservlets are jmx, metrics, prometheus</description></property><property><name>hbase.replication.rpc.codec</name><value>org.apache.hadoop.hbase.codec.KeyValueCodecWithTags</value><description>The codec that is to be used when replication is enabled so thatthe tags are also replicated. This is used along with HFileV3 whichsupports tags in them.  If tags are not used or if the hfile version usedis HFileV2 then KeyValueCodec can be used as the replication codec. Note thatusing KeyValueCodecWithTags for replication when there are no tags causes no harm.</description></property><property><name>hbase.replication.source.maxthreads</name><value>10</value><description>The maximum number of threads any replication source will use forshipping edits to the sinks in parallel. This also limits the number ofchunks each replication batch is broken into. Larger values can improvethe replication throughput between the master and slave clusters. Thedefault of 10 will rarely need to be changed.</description></property><!-- Static Web User Filter properties. --><property><name>hbase.http.staticuser.user</name><value>dr.stack</value><description>The user name to filter as, on static web filterswhile rendering content. An example use is the HDFSweb UI (user to be used for browsing files).</description></property><property><name>hbase.regionserver.handler.abort.on.error.percent</name><value>0.5</value><description>The percent of region server RPC threads failed to abort RS.-1 Disable aborting; 0 Abort if even a single handler has died;0.x Abort only when this percent of handlers have died;1 Abort only all of the handers have died.</description></property><!-- Mob properties. --><property><name>hbase.mob.file.cache.size</name><value>1000</value><description>Number of opened file handlers to cache.A larger value will benefit reads by providing more file handlers per mobfile cache and would reduce frequent file opening and closing.However, if this is set too high, this could lead to a "too many opened file handlers"The default value is 1000.</description></property><property><name>hbase.mob.cache.evict.period</name><value>3600</value><description>The amount of time in seconds before the mob cache evicts cached mob files.The default value is 3600 seconds.</description></property><property><name>hbase.mob.cache.evict.remain.ratio</name><value>0.5f</value><description>The ratio (between 0.0 and 1.0) of files that remains cached after an evictionis triggered when the number of cached mob files exceeds the hbase.mob.file.cache.size.The default value is 0.5f.</description></property><property><name>hbase.master.mob.cleaner.period</name><value>86400</value><description>The period that MobFileCleanerChore runs. The unit is second.The default value is one day. The MOB file name uses only the date part ofthe file creation time in it. We use this time for deciding TTL expiry ofthe files. So the removal of TTL expired files might be delayed. The maxdelay might be 24 hrs.</description></property><property><name>hbase.mob.major.compaction.region.batch.size</name><value>0</value><description>The max number of a MOB table regions that is allowed in a batch of the mob compaction. Bysetting this number to a custom value, users can control the overall effect of a majorcompaction of a large MOB-enabled table.Default is 0 - means no limit - all regions of a MOB table will be compacted at once</description></property><property><name>hbase.mob.compaction.chore.period</name><value>604800</value><description>The period that MobCompactionChore runs. The unit is second.The default value is one week.</description></property><property><name>hbase.snapshot.master.timeout.millis</name><value>300000</value><description>Timeout for master for the snapshot procedure execution.</description></property><property><name>hbase.snapshot.region.timeout</name><value>300000</value><description>Timeout for regionservers to keep threads in snapshot request pool waiting.</description></property><property><name>hbase.rpc.rows.warning.threshold</name><value>5000</value><description>Number of rows in a batch operation above which a warning will be logged.</description></property><property><name>hbase.master.wait.on.service.seconds</name><value>30</value><description>Default is 5 minutes. Make it 30 seconds for tests. SeeHBASE-19794 for some context.</description></property><property><name>hbase.master.cleaner.snapshot.interval</name><value>1800000</value><description>Snapshot Cleanup chore interval in milliseconds.The cleanup thread keeps running at this intervalto find all snapshots that are expired based on TTLand delete them.</description></property><property><name>hbase.master.snapshot.ttl</name><value>0</value><description>Default Snapshot TTL to be considered when the user does not specify TTL whilecreating snapshot. Default value 0 indicates FOREVERE - snapshot should not beautomatically deleted until it is manually deleted</description></property><property><name>hbase.master.regions.recovery.check.interval</name><value>1200000</value><description>Regions Recovery Chore interval in milliseconds.This chore keeps running at this interval tofind all regions with configurable max store file ref countand reopens them.</description></property><property><name>hbase.regions.recovery.store.file.ref.count</name><value>-1</value><description>Very large number of ref count on a compactedstore file indicates that it is a ref leakon that object(compacted store file).Such files can not be removed afterit is invalidated via compaction.Only way to recover in such scenario is toreopen the region which can releaseall resources, like the refcount,leases, etc. This config represents Store files RefCount threshold value considered for reopeningregions. Any region with compacted store filesref count > this value would be eligible forreopening by master. Here, we get the maxrefCount among all refCounts on allcompacted away store files that belong to aparticular region. Default value -1 indicatesthis feature is turned off. Only positiveinteger value should be provided toenable this feature.</description></property><property><name>hbase.regionserver.slowlog.ringbuffer.size</name><value>256</value><description>Default size of ringbuffer to be maintained by each RegionServer in orderto store online slowlog responses. This is an in-memory ring buffer ofrequests that were judged to be too slow in addition to the responseTooSlowlogging. The in-memory representation would be complete.For more details, please look into Doc Section:Get Slow Response Log from shell</description></property><property><name>hbase.regionserver.slowlog.buffer.enabled</name><value>false</value><description>Indicates whether RegionServers have ring buffer running for storingOnline Slow logs in FIFO manner with limited entries. The size ofthe ring buffer is indicated by config: hbase.regionserver.slowlog.ringbuffer.sizeThe default value is false, turn this on and get latest slowlogresponses with complete data.</description></property><property><name>hbase.regionserver.slowlog.systable.enabled</name><value>false</value><description>Should be enabled only if hbase.regionserver.slowlog.buffer.enabled is enabled. If enabled(true), all slow/large RPC logs would be persisted to system table hbase:slowlog (in additionto in-memory ring buffer at each RegionServer). The records are stored in increasingorder of time. Operators can scan the table with various combination of ColumnValueFilter.More details are provided in the doc section:"Get Slow/Large Response Logs from System table hbase:slowlog"</description></property><property><name>hbase.master.metafixer.max.merge.count</name><value>64</value><description>Maximum regions to merge at a time when we fix overlaps noted inCJ consistency report, but avoid merging 100 regions in one go!</description></property><property><name>hbase.rpc.rows.size.threshold.reject</name><value>false</value><description>If value is true, RegionServer will abort batch requests of Put/Delete with number of rowsin a batch operation exceeding threshold defined by value of config:hbase.rpc.rows.warning.threshold. The default value is false and hence, by default, onlywarning will be logged. This config should be turned on to prevent RegionServer from servingvery large batch size of rows and this way we can improve CPU usages by discardingtoo large batch request.</description></property><property><name>hbase.namedqueue.provider.classes</name><value>org.apache.hadoop.hbase.namequeues.impl.SlowLogQueueService,org.apache.hadoop.hbase.namequeues.impl.BalancerDecisionQueueService,org.apache.hadoop.hbase.namequeues.impl.BalancerRejectionQueueService,org.apache.hadoop.hbase.namequeues.WALEventTrackerQueueService</value><description>Default values for NamedQueueService implementors. This comma separated full class namesrepresent all implementors of NamedQueueService that we would like to be invoked byLogEvent handler service. One example of NamedQueue service is SlowLogQueueService whichis used to store slow/large RPC logs in ringbuffer at each RegionServer.All implementors of NamedQueueService should be found under package:"org.apache.hadoop.hbase.namequeues.impl"</description></property><property><name>hbase.master.balancer.decision.buffer.enabled</name><value>false</value><description>Indicates whether active HMaster has ring buffer running for storingbalancer decisions in FIFO manner with limited entries. The size ofthe ring buffer is indicated by config: hbase.master.balancer.decision.queue.size</description></property><property><name>hbase.master.balancer.rejection.buffer.enabled</name><value>false</value><description>Indicates whether active HMaster has ring buffer running for storingbalancer rejection in FIFO manner with limited entries. The size ofthe ring buffer is indicated by config: hbase.master.balancer.rejection.queue.size</description></property><property><name>hbase.locality.inputstream.derive.enabled</name><value>false</value><description>If true, derive StoreFile locality metrics from the underlying DFSInputStreambacking reads for that StoreFile. This value will update as the DFSInputStream'sblock locations are updated over time. Otherwise, locality is computed on StoreFileopen, and cached until the StoreFile is closed.</description></property><property><name>hbase.locality.inputstream.derive.cache.period</name><value>60000</value><description>If deriving StoreFile locality metrics from the underlying DFSInputStream, howlong should the derived values be cached for. The derivation process may involvehitting the namenode, if the DFSInputStream's block list is incomplete.</description></property>
</configuration>