HBase hbase-site.xml Parameters

The document was generated with the HBase default profile and the file source is hbase-default.xml.

Applied to%hbase_home%/conf/hbase-site.xml in the actual HBASE production environment.

Hbase.rootdir

This directory is a shared directory of Region server and is used to persist hbase. The URL needs to be ' completely correct ' and include the file system scheme. For example, to represent the '/hbase ' directory in HDFs, Namenode runs on port 9090 of namenode.example.org. You need to set it to Hdfs://namenode.example.org:9000/hbase. By default, HBase is written to/tmp. Without changing this configuration, the data will be lost at reboot.

Default: File:///tmp/hbase-${user.name}/hbase

Hbase.master.port

The port of the master for HBase.

Default: 60000

hbase.cluster.distributed

The operating mode of HBase. False is a standalone mode, and true is distributed mode. If the false,hbase and zookeeper are running in the same JVM.

Default: False

Hbase.tmp.dir

The temporary folder for the local file system. Can be modified to a more persistent directory. (/TMP will be clear at reboot)

Default:/tmp/hbase-${user.name}

Hbase.master.info.port

HBase Master Web interface port. Set to 1 means you don't want to let him run.

Default: 60010

Hbase.master.info.bindAddress

HBase Master Web interface-bound port

Default: 0.0.0.0

Hbase.client.write.buffer

The default size of the write buffer for the htable client. The larger the value, the greater the memory that needs to be consumed. Because the buffer has instances on both the client and the server, it consumes two places of memory on the client and server side. The benefit is that the number of RPCs can be reduced. It is possible to estimate the server-side memory: Hbase.client.write.buffer * Hbase.regionserver.handler.count

Default: 2097152

Hbase.regionserver.port

HBase Regionserver-bound port

Default: 60020

Hbase.regionserver.info.port

The HBase Regionserver Web interface is bound to a port set to 1 which means that you do not want to run the Regionserver interface with.

Default: 60030

Hbase.regionserver.info.port.auto

Whether master or Regionserver dynamically searches for a port that can be used to bind the interface. When the Hbase.regionserver.info.port is already occupied, you can search for a free port binding. This feature is useful when testing. Closed by default.

Default: False

Hbase.regionserver.info.bindAddress

HBase regionserver Web Interface IP Address

Default: 0.0.0.0

Hbase.regionserver.class

The interface used by the Regionserver. This is used when the client opens the proxy to connect to region server.

Default: Org.apache.hadoop.hbase.ipc.HRegionInterface

Hbase.client.pause

The usual client pause time. The maximum usage is the time the client waits before retrying. For example, failed get operations and region query operations are likely to be used.

Default: 1000

Hbase.client.retries.number

Maximum number of retries. For example, a region query, a get operation, an update operation, and so on, can have errors and need to retry. This is the value of the maximum retry error.

Default: 10

Hbase.client.scanner.caching

When the next method of scanner is called, and the value is not in the cache, the number of rows fetched from the service side at one time. A larger value means that the scanner will be faster, but will consume more memory. When the buffer is full, the next method call is getting slower. Slow to a certain level, may result in timeouts. For example, more than Hbase.regionserver.lease.period.

Default: 1

Hbase.client.keyvalue.maxsize

The maximum size of a keyvalue instance. This is used to set the upper bound of the single entry in the storage file. Because a keyvalue is not divisible, it can be avoided because the data is too large to cause the region to be inseparable. It is wise to set it to a number that can be divisible by the maximum region size. If set to 0 or smaller, this check is disabled. Default 10MB.

Default: 10485760

Hbase.regionserver.lease.period

The client leases the Hregion server term, which is the timeout threshold. The unit is in milliseconds. By default, the client must send a message within this time, otherwise it will be considered dead.

Default: 60000

Hbase.regionserver.handler.count

Number of RPC server instances accepted by Regionservers. For master, this attribute is the number of handler accepted by master

Default: 10

Hbase.regionserver.msginterval

Regionserver sends a message to the Master time interval, in milliseconds

Default: 3000

Hbase.regionserver.optionallogflushinterval

The interval at which the Hlog is synchronized to HDFs. If the hlog does not accumulate to a certain amount, the time will also trigger synchronization. The default is 1 seconds, per millisecond.

Default: 1000

Hbase.regionserver.regionSplitLimit

The number of region will not split after this value. This is not a hard limit for the number of region. But the role of a certain guidance, to this value should stop splitting. The default is Max_int. is to say not to stop the division.

Default: 2147483647

Hbase.regionserver.logroll.period

The interval at which commit log is committed, regardless of whether or not sufficient values are written.

Default: 3600000

Hbase.regionserver.hlog.reader.impl

HLog the implementation of file reader.

Default: Org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader

Hbase.regionserver.hlog.writer.impl

HLog the implementation of file writer.

Default: Org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogWriter

Hbase.regionserver.thread.splitcompactcheckfrequency

How often region server performs a split/compaction check.

Default: 20000

Hbase.regionserver.nbreservationblocks

The number of memory blocks stored (the translator notes: just like oil reserves). When an out of memory exception occurs, we can use these inside the regionserver to stop before the cleanup operation.

Default: 4

Hbase.zookeeper.dns.interface

When using DNS, zookeeper the name of the network interface used to escalate the IP address.

Defaults: Default

Hbase.zookeeper.dns.nameserver

When using DNS, ZOOKEEPR uses a DNS domain name or IP address that zookeeper uses to determine and master the domain name used for communication.

Defaults: Default

Hbase.regionserver.dns.interface

When using DNS, regionserver the name of the network interface used to escalate the IP address.

Defaults: Default

Hbase.regionserver.dns.nameserver

When using DNS, Regionserver uses a DNS domain name or IP address that Regionserver uses to determine and master the domain name used for communication.

Defaults: Default

Hbase.master.dns.interface

The network interface name of the IP address that master uses to escalate when using DNS.

Defaults: Default

Hbase.master.dns.nameserver

When using DNS, Regionserver uses a DNS domain name or IP address that master uses to determine the domain name used for communication.

Defaults: Default

Hbase.balancer.period

Master executes the interval for region balancer.

Default: 300000

Hbase.regions.slop

When any regionserver has average + (average * slop) a region is executed rebalance

Default: 0

Hbase.master.logcleaner.ttl

The maximum amount of time that hlog exists in the. Oldlogdir folder will be erased by Master's thread.

Default: 600000

Hbase.master.logcleaner.plugins

A set of Logcleanerdelegat that the Logscleaner service executes. Values are represented by a comma-spaced text. These wal/hlog cleaners are called sequentially. You can put the first call on the front. You can implement your own Logcleanerdelegat, add to Classpath, and write down the full name of the class here. is usually preceded by the default value.

Default: Org.apache.hadoop.hbase.master.TimeToLiveLogCleaner

Hbase.regionserver.global.memstore.upperLimit

The maximum value of all memtores for a single region server. Exceeding this value, a new update operation is suspended and the flush operation is enforced.

Default: 0.4

Hbase.regionserver.global.memstore.lowerLimit

When the flush operation is enforced, flush stops when it is below this value. The default is 35% of the heap size. If this value is the same as hbase.regionserver.global.memstore.upperLimit, it means that when the update operation is suspended because the memory limit is pending, the flush is minimized (the translator notes: Once flush is executed, Value will be lower than the lower limit, no longer executed)

Default: 0.35

Hbase.server.thread.wakefrequency

The sleep interval of the service work, in milliseconds. Can be used as a sleep interval for service threads, such as log roller.

Default: 10000

Hbase.hregion.memstore.flush.size

When the size of the memstore exceeds this value, it is flush to disk. This value is checked by a thread every hbase.server.thread.wakefrequency.

Default: 67108864

Hbase.hregion.preclose.flush.size

When the size of the Memstore in a region is greater than this value, we trigger close again. The "Pre-flush" operation is run, cleaning up the memstore that needs to be closed, and then the region is offline. When a region is offline, we can't do any more writing. If a memstore is large, the flush operation consumes a lot of time. The "Pre-flush" operation means that the memstore is emptied before the region is offline. This will cause the flush operation to be quick when the close operation is finally performed.

Default: 5242880

Hbase.hregion.memstore.block.multiplier

If the Memstore has a size of hbase.hregion.flush.size of hbase.hregion.memstore.block.multiplier multiples, the update operation is blocked. This is to prevent runaway at the peak of the update. If you do not set an upper bound, flush will take a long time to merge or split, the worst case is to throw out of memory exception. (Translator note: The speed of memory operation and disk mismatch, need to wait.) The original appears to be wrong)

Default: 2

Hbase.hregion.memstore.mslab.enabled

Experience Feature: Enable Memstore to allocate local buffers. This feature is designed to prevent the heap from being too fragmented when the load is heavily written. This can reduce the frequency of GC operations. (GC is likely to stop the world) (Translator Note: The principle of implementation is equivalent to pre-allocated memory, not every value is allocated from the heap)

Default: False

Hbase.hregion.max.filesize

Maximum Hstorefile size. If the hstorefile of a column families reaches this value, the hegion will be cut to two. default:256m.

Default: 268435456

Hbase.hstore.compactionThreshold

When a hstore contains more than this value hstorefiles (each Memstore flush produces a hstorefile), a merge operation is performed to write the Hstorefiles as a. The larger the value, the longer it takes to merge.

Default: 3

Hbase.hstore.blockingStoreFiles

When a hstore contains more than this value hstorefiles (each Memstore flush produces a hstorefile), a merge operation is performed, and the update blocks until the merge is complete, Until the value of Hbase.hstore.blockingWaitTime is exceeded.

Default: 7

Hbase.hstore.blockingWaitTime

Hbase.hstore.blockingStoreFiles limits the number of storefile that can cause update blocking, which is the time to limit blocking time. When this time is exceeded, Hregion stops blocking the update operation, but the merge has not been completed. The default is 90s.

Default: 90000

Hbase.hstore.compaction.max

The maximum number of hstorefiles per "small" merge.

Default: 10

Hbase.hregion.majorcompaction

The interval of major compactions for all hstorefile in a region. The default is 1 days. Setting to 0 disables this feature.

Default: 86400000

Hbase.mapreduce.hfileoutputformat.blocksize

In MapReduce, Hfileoutputformat can write Storefiles/hfiles. This value is the minimum value of the hfile blocksize. The bloocksize is usually determined by the table schema (Hcolumndescriptor) when HBase writes hfile, but we cannot get blocksize in the schema when the MapReduce is written. The smaller the value, the greater your index, and the smaller the data you need to access randomly. If your cell is small, and you need a faster random access, you can turn this value down.

Default: 65536

Hfile.block.cache.size

The block cache allocated to Hfile/storefile is the ratio of the maximum heap (-xmx setting). The default is 20%, which is set to 0 is not assigned.

Default: 0.2

Hbase.hash.type

The hashing algorithm used by the hash function. You can choose from two values:: Murmur (MurmurHash) and Jenkins (Jenkinshash). This hash is for bloom filters.

Default: Murmur

Hbase.master.keytab.file

Hmaster server verifies the Kerberos keytab file path used by the login. (Note: HBase uses Kerberos for security)

Default:

Hbase.master.kerberos.principal

For example. "Hbase/[email protected]". Hmaster operation requires the use of Kerberos principal name. Principal name can be obtained in: User/[email protected]. If "_host" is used as hostname portion, it needs to be replaced with the actual running hostname.

Default:

Hbase.regionserver.keytab.file

Hregionserver Verify the Kerberos keytab file path used by the login.

Default:

Hbase.regionserver.kerberos.principal

For example. "Hbase/[email protected]". Hregionserver operation requires the use of Kerberos principal name. Principal name can be obtained in: User/[email protected]. If "_host" is used as hostname portion, it needs to be replaced with the actual running hostname. There must be a entry in this file to describe Hbase.regionserver.keytab.file

Default:

Zookeeper.session.timeout

ZooKeeper session timed out. HBase passes this value to the ZK cluster, recommending to him the maximum time-out for a session. See Http://hadoop.apache.org/zookeeper/docs/current/zookeeperProgrammers.html#ch_zkSessions "The client sends a Requested timeout, the server responds with the-timeout that it can give the client. "。 Unit is milliseconds

Default: 180000

Zookeeper.znode.parent

The root znode of hbase in zookeeper. All HBase zookeeper will use this directory to configure the relative path. By default, all HBase zookeeper file paths are used relative to the path, so they will all go under this directory.

Default:/hbase

Zookeeper.znode.rootserver

Znode the path to the root region of the save. This value is written by Master, which is read by the client and Regionserver. If set to a relative address, the parent directory is ${zookeeper.znode.parent}. By default, it means that the path to the root region is stored in the/hbase/root-region-server.

Default: Root-region-server

Hbase.zookeeper.quorum

Zookeeper the address list of the cluster, separated by commas. For example: "Host1.mydomain.com,host2.mydomain.com,host3.mydomain.com". The default is localhost, which is for pseudo-distributed use. To be modified in order to be used in a fully distributed situation. If HBASE_MANAGES_ZK is set at hbase-env.sh, these zookeeper nodes will start with HBase.

Default: localhost

Hbase.zookeeper.peerport

The port used by the Zookeeper node. See more: Http://hadoop.apache.org/zookeeper/docs/r3.1.1/zookeeperStarted.html#sc_RunningReplicatedZooKeeper

Default: 2888

Hbase.zookeeper.leaderport

Zookeeper is used to select the port of the leader, see in detail: http://hadoop.apache.org/zookeeper/docs/r3.1.1/zookeeperStarted.html#sc_ Runningreplicatedzookeeper

Default: 3888

Hbase.zookeeper.property.initLimit

The configuration in the Zookeeper zoo.conf. Ticks number limit for initializing the synchronization phase

Default: 10

Hbase.zookeeper.property.syncLimit

The configuration in the Zookeeper zoo.conf. Send a request to obtain recognition between the number of ticks limits

Default: 5

Hbase.zookeeper.property.dataDir

The configuration in the Zookeeper zoo.conf. Where the snapshot is stored

Default: ${hbase.tmp.dir}/zookeeper

Hbase.zookeeper.property.clientPort

The configuration in the Zookeeper zoo.conf. Port for client connections

Default: 2181

Hbase.zookeeper.property.maxClientCnxns

The configuration in the Zookeeper zoo.conf. Zookeeper the number of concurrent requests for a single client (IP-differentiated) that a single node in the cluster accepts. This value can be increased to prevent problems in single-machine and pseudo-distributed mode.

Default: 2000

Hbase.rest.port

Port of HBase REST Server

Default: 8080

Hbase.rest.readonly

Defines the run mode for rest server. Can be set to the following value: false: All HTTP requests are allowed-get/put/post/delete. True: Only get requests are allowed

Default: False

Transferred from: http://greatwqs.iteye.com/blog/1837178

HBase hbase-site.xml Parameters