HBASE配置参数说明中文文档(官方文档翻译)

HBASE所有参数原文加中文译文,方便学习交流研究使用,因使用爬虫获取部分内容翻译可能存在误差,仅供参考,以原文内容为准.

官方原文地址

hbase.tmp.dir

原文

Temporary directory on the local filesystem. Change this setting to point to a location more permanent than ‘/tmp’, the usual resolve for java.io.tmpdir, as the ‘/tmp’ directory is cleared on machine restart.

译文

本地文件系统上的临时目录。将此设置更改为指向比‘/tmp’更永久的位置，这是java.io.tmpdir的通常解析，因为‘/tmp’目录在机器重新启动时被清除。

默认值:${java.io.tmpdir}/hbase-${user.name}

hbase.rootdir

原文

The directory shared by region servers and into which HBase persists. The URL should be ‘fully-qualified’ to include the filesystem scheme. For example, to specify the HDFS directory ‘/hbase’ where the HDFS instance’s namenode is running at namenode.example.org on port 9000, set this value to: hdfs://namenode.example.org:9000/hbase. By default, we write to whatever ${hbase.tmp.dir} is set too — usually /tmp — so change this configuration or else all data will be lost on machine restart.

译文

区域服务器共享的目录，HBASE持久化。URL应该是“完全限定的”，以包括文件系统方案。例如，要指定HDFS目录‘/HBASE’，其中HDFS实例的NameNode在端口9000上的namenode.example.org上运行，请将此值设置为：hdfs：//namenode.example.org：9000/HBASE。默认情况下，我们会将${hbase.tmp.dir}也设置为–通常是/tmp–因此更改此配置，否则在机器重新启动时所有数据都会丢失。

默认值:${hbase.tmp.dir}/hbase

hbase.cluster.distributed

原文

The mode the cluster will be in. Possible values are false for standalone mode and true for distributed mode. If false, startup will run all HBase and ZooKeeper daemons together in the one JVM.

译文

集群将进入的模式。独立模式为false，分布式模式为true。如果为false, startup将在一个JVM中同时运行所有的HBase和ZooKeeper进程。

默认值:false

hbase.zookeeper.quorum

原文

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 modes of operation. For a fully-distributed setup, this should be set to a full list of ZooKeeper ensemble servers. If HBASE_MANAGES_ZK is set in hbase-env.sh this is the list of servers which hbase will start/stop ZooKeeper on as part of cluster start/stop. Client-side, we will take this list of ensemble members and put it together with the hbase.zookeeper.property.clientPort config. and pass it into zookeeper constructor as the connectString parameter.

译文

用逗号分隔的ZooKeeper集合中的服务器列表。应该命名为hbase.zookeeper.ensemble)。例如,host1.mydomain.com, host2.mydomain.com, host3.mydomain.com。默认情况下，对于本地和伪分布式的操作模式，它被设置为localhost。对于一个完全分布式的设置，这应该设置为一个完整的ZooKeeper集成服务器列表。如果在hbase-env.sh中设置了HBASE_MANAGES_ZK，这是hbase启动/停止ZooKeeper作为集群启动/停止的一部分的服务器列表。在客户端，我们将把这个集合成员列表和hbase.zookeeper.property.clientPort配置放在一起。并将它作为connectString参数传递给zookeeper的构造函数。

默认值:127.0.0.1

zookeeper.recovery.retry.maxsleeptime

原文

Max sleep time before retry zookeeper operations in milliseconds, a max time is needed here so that sleep time won’t grow unboundedly

译文

在重试zookeeper操作之前的最大睡眠时间(以毫秒为单位)，这里需要一个最大的睡眠时间，这样睡眠时间就不会无限制地增长.

默认值:60000

hbase.local.dir

原文

Directory on the local filesystem to be used as a local storage.

译文

作为本地存储的本地文件系统上的目录。

默认值:${hbase.tmp.dir}/local/

hbase.master.port

原文

The port the HBase Master should bind to.

译文

HBASE母版应该绑定到的端口。

默认值:16000

hbase.master.info.port

原文

The port for the HBase Master web UI. Set to -1 if you do not want a UI instance run.

译文

HBASE主web UI的端口。如果不希望运行UI实例，则设置为-1。

默认值:16010

hbase.master.info.bindAddress

原文

The bind address for the HBase Master web UI

译文

HBASE主web UI的绑定地址

默认值:0.0.0.0

hbase.master.logcleaner.plugins

原文

A comma-separated list of BaseLogCleanerDelegate invoked by the LogsCleaner service. These WAL cleaners are called in order, so put the cleaner that prunes the most files in front. To implement your own BaseLogCleanerDelegate, just put it in HBase’s classpath and add the fully qualified class name here. Always add the above default log cleaners in the list.

译文

LogsCleaner服务调用的一个以逗号分隔的BaseLogCleanerDelegate列表。这些Wal清洁工是按顺序调用的，所以把修剪最多文件的清洁器放在前面。要实现自己的BaseLogCleanerDelegate，只需将其放入HBASE的类路径中，并在这里添加完全限定的类名。始终在列表中添加上述默认日志清除器。

默认值:org.apache.hadoop.hbase.master.cleaner.TimeToLiveLogCleaner,org.apache.hadoop.hbase.master.cleaner.TimeToLiveProcedureWALCleaner,org.apache.hadoop.hbase.master.cleaner.TimeToLiveMasterLocalStoreWALCleaner

hbase.master.logcleaner.ttl

原文

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.

译文

Wal在存档({hbase.rootdir}/oldWALs)目录中停留多长时间，然后由主线程清理。该值以毫秒为单位。

默认值:600000

hbase.master.hfilecleaner.plugins

原文

A comma-separated list of BaseHFileCleanerDelegate invoked by the HFileCleaner service. These HFiles cleaners are called in order, so put the cleaner that prunes the most files in front. To implement your own BaseHFileCleanerDelegate, just put it in HBase’s classpath and add the fully qualified class name here. Always add the above default hfile cleaners in the list as they will be overwritten in hbase-site.xml.

译文

由HFileCleaner服务调用的BaseHFileCleanerDelegate的逗号分隔列表。这些HFiles清洁器是按顺序调用的，所以将修剪最多文件的清洁器放在前面。要实现自己的BaseHFileCleanerDelegate，只需将其放入HBASE的类路径中，并在这里添加完全限定的类名。始终在列表中添加上述默认hfile清理器，因为它们将在HBASE-site.xml中覆盖。

默认值:org.apache.hadoop.hbase.master.cleaner.TimeToLiveHFileCleaner,org.apache.hadoop.hbase.master.cleaner.TimeToLiveMasterLocalStoreHFileCleaner

hbase.master.infoserver.redirect

原文

Whether or not the Master listens to the Master web UI port (hbase.master.info.port) and redirects requests to the web UI server shared by the Master and RegionServer. Config. makes sense when Master is serving Regions (not the default).

译文

主服务器是否侦听主Web UI端口(hbase.master.info.port)并将请求重定向到主服务器和RegionServer共享的Web UI服务器。配置。当Master正在为区域服务时(不是默认的)，这是有意义的。

默认值:true

hbase.master.fileSplitTimeout

原文

Splitting a region, how long to wait on the file-splitting step before aborting the attempt. Default: 600000. This setting used to 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 to prime the current ‘hbase.master.fileSplitTimeout’ Configuration.

译文

分割一个区域，在中止尝试之前，在文件拆分步骤上等待多长时间。违约：600000。在HBASE-1.x中，此设置以前称为hbase.Regiserver.fileSplitTimeout。Split现在在主端运行，因此重命名(如果找到‘hbase.master.fileSplitTimeout’设置，将使用它来初始化当前的‘hbase.master.fileSplitTimeout’配置。

默认值:600000

hbase.regionserver.port

原文

The port the HBase RegionServer binds to.

译文

HBASE RegionServer绑定到的端口。

默认值:16020

hbase.regionserver.info.port

原文

The port for the HBase RegionServer web UI Set to -1 if you do not want the RegionServer UI to run.

译文

如果不希望运行RegionServerUI，则HBASE RegionServerWebUI的端口设置为-1。

默认值:16030

hbase.regionserver.info.bindAddress

原文

The address for the HBase RegionServer web UI

译文

HBASE RegionServerWebUI的地址

默认值:0.0.0.0

hbase.regionserver.info.port.auto

原文

Whether or not the Master or RegionServer UI should search for a port to bind to. Enables automatic port search if hbase.regionserver.info.port is already in use. Useful for testing, turned off by default.

译文

主服务器或RegionServerUI是否应该搜索要绑定到的端口。启用自动端口搜索，如果已在使用hbase.Regiserver.info.port。用于测试，默认关闭。

默认值:false

hbase.regionserver.handler.count

原文

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 of CPU count. If mostly read-only, handlers count close to cpu count does well. Start with twice the CPU count and tune from there.

译文

在RegionServers上旋转的RPC侦听器实例的计数。主处理器对主处理程序的计数使用相同的属性。太多的处理程序可能会适得其反。使其成为CPU计数的倍数。如果大多数情况下是只读的，则处理程序的计数接近CPU计数。从CPU数量的两倍开始，然后从那里进行调优。

默认值:30

hbase.ipc.server.callqueue.handler.factor

原文

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.

译文

以确定呼叫队列的数量。值0表示所有处理程序之间共享的单个队列。值1意味着每个处理程序都有自己的队列。

默认值:0.1

hbase.ipc.server.callqueue.read.ratio

原文

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 write requests 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 10 a 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 requests and 7 queues will contain only write requests. a read.ratio of 0.5 means that: 5 queues will contain only read requests and 5 queues will contain only write requests. a read.ratio of 0.8 means that: 8 queues will contain only read requests and 2 queues will contain only write requests. a read.ratio of 1 means that: 9 queues will contain only read requests and 1 queues will contain only write requests.

译文

将调用队列拆分为读队列和写队列。指定的间隔(应该在0.0到1.0之间)将乘以调用队列的数量。值0表示不拆分调用队列，这意味着读写请求将被推送到同一组队列中。小于0.5的值意味着读取队列将比写入队列少。值0.5意味着读取和写入队列的数量相同。大于0.5的值意味着读取队列将多于写入队列。值为1.0意味着除了一个队列之外的所有队列都用于发送读取请求。示例：如果调用队列的总数为10，那么read.充足率为0意味着：这10个队列将同时包含读/写请求。Read.的比率为0.3意味着：3个队列只包含读请求，7个队列只包含写请求。Read.的比率为0.5意味着：5个队列只包含读请求，5个队列只包含写请求。Read.比率为0.8意味着：8个队列只包含读请求，两个队列只包含写请求。读取比为1意味着：9个队列只包含读取请求，一个队列只包含写请求。

默认值:0

hbase.ipc.server.callqueue.scan.ratio

原文

Given the number of read call queues, calculated from the total number of call queues multiplied by the callqueue.read.ratio, the scan.ratio property will 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 queues A 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 8 a 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 requests and 6 queues will contain only short-read requests. a scan.ratio of 0.5 means that: 4 queues will contain only long-read requests and 4 queues will contain only short-read requests. a scan.ratio of 0.8 means that: 6 queues will contain only long-read requests and 2 queues will contain only short-read requests.

译文

给定读取呼叫队列的数量，根据呼叫队列的总数乘以呼叫队列的Read.Rate，scan.rate属性将读取的呼叫队列拆分为小读取队列和长读取队列。小于0.5的值意味着长读队列将比短读队列少。值0.5意味着短读和长读队列的数量相同。大于0.5的值意味着长读队列将比短读队列多。值0或1表示在GET和扫描中使用相同的队列集。示例：假定读取呼叫队列的总数为8，扫描比为0或1意味着：8个队列将同时包含长和短的读取请求。0.3的扫描比意味着：2个队列只包含长读请求，6个队列只包含短读请求。0.5的扫描比意味着：4个队列只包含长读请求，4个队列只包含短读请求。0.8的扫描比意味着：6个队列只包含长读请求，两个队列只包含短读请求。

默认值:0

hbase.regionserver.msginterval

原文

Interval between messages from the RegionServer to Master in milliseconds.

译文

从RegionServer到Master的消息之间的间隔(毫秒)。

默认值:3000

hbase.regionserver.logroll.period

原文

Period at which we will roll the commit log regardless of how many edits it has.

译文

不管提交日志有多少编辑，我们都将在其中滚动。

默认值:3600000

hbase.regionserver.logroll.errors.tolerated

原文

The number of consecutive WAL close errors we will allow before triggering a server abort. A setting of 0 will cause the region server to abort if closing the current WAL writer fails during log rolling. Even a small value (2 or 3) will allow a region server to ride over transient HDFS errors.

译文

触发服务器中止之前将允许的连续Wal关闭错误的数目。如果在日志滚动期间关闭当前Wal写程序失败，则设置为0将导致区域服务器中止。即使是一个较小的值(2或3)也将允许区域服务器通过瞬态HDFS错误。

默认值:2

hbase.regionserver.hlog.reader.impl

原文

The WAL file reader implementation.

译文

Wal文件读取器实现。

默认值:org.apache.hadoop.hbase.regionserver.wal.ProtobufLogReader

hbase.regionserver.hlog.writer.impl

原文

The WAL file writer implementation.

译文

Wal文件编写器实现。

默认值:org.apache.hadoop.hbase.regionserver.wal.ProtobufLogWriter

hbase.regionserver.global.memstore.size

原文

Maximum size of all memstores in a region server before new updates are blocked and flushes are forced. Defaults to 40% of heap (0.4). Updates are blocked and flushes are forced until size of all memstores in a region server hits hbase.regionserver.global.memstore.size.lower.limit. The default value in this configuration has been intentionally left empty in order to honor the old hbase.regionserver.global.memstore.upperLimit property if present.

译文

在阻止新的更新和强制刷新之前，区域服务器中所有MemStore的最大大小。默认为堆的40%(0.4)。更新将被阻止并强制刷新，直到区域服务器中所有内存存储的大小到达hbase.regionserver.global.memstore.size.lower.limit.为止。此配置中的默认值被有意保留为空，以便遵守旧的hbase.Regierver.global.memstore.upperLimit属性(如果存在)。

默认值:none

hbase.regionserver.global.memstore.size.lower.limit

原文

Maximum size of all memstores in a region server before flushes are forced. Defaults to 95% of hbase.regionserver.global.memstore.size (0.95). A 100% value for this value causes the minimum possible flushing to occur when updates are blocked due to memstore limiting. The default value in this configuration has been intentionally left empty in order to honor the old hbase.regionserver.global.memstore.lowerLimit property if present.

译文

在强制刷新之前，区域服务器中所有内存存储的最大大小。默认为95%的hbase.Regierver.global.memstore.size(0.95)。此值的100%值将导致在由于memstore限制而阻止更新时发生最小可能的刷新。此配置中的默认值被有意保留为空，以遵守旧的hbase.Regierver.global.memstore.lowerLimit属性(如果存在)。

默认值:none

hbase.systemtables.compacting.memstore.type

原文

Determines the type of memstore to be used for system tables like META, namespace tables etc. By default NONE is the type and hence we use the default memstore for all the system tables. If we need to use compacting memstore for system tables then set this property to BASIC/EAGER

译文

确定要用于系统表(如meta、命名空间表等)的memstore类型。默认情况下，没有一个是类型，因此我们对所有系统表使用默认的memstore。如果我们需要对系统表使用密实memstore，那么将此属性设置为basic/急切

默认值:NONE

hbase.regionserver.optionalcacheflushinterval

原文

Maximum amount of time an edit lives in memory before being automatically flushed. Default 1 hour. Set it to 0 to disable automatic flushing.

译文

编辑在被自动刷新之前驻留在内存中的最大时间。默认1小时。将其设置为0以禁用自动冲洗。

默认值:3600000

hbase.regionserver.dns.interface

原文

The name of the Network Interface from which a region server should report its IP address.

译文

用于区域服务器报告其IP地址的网络接口的名称。

默认值:default

hbase.regionserver.dns.nameserver

原文

The host name or IP address of the name server (DNS) which a region server should use to determine the host name used by the master for communication and display purposes.

译文

名称服务器(DNS)的主机名或IP地址，该区域服务器应用来确定主机用于通信和显示目的的主机名。

默认值:default

hbase.regionserver.region.split.policy

原文

A split policy determines when a region should be split. The various other split policies that are available currently are BusyRegionSplitPolicy, ConstantSizeRegionSplitPolicy, DisabledRegionSplitPolicy, DelimitedKeyPrefixRegionSplitPolicy, KeyPrefixRegionSplitPolicy, and SteppingSplitPolicy. DisabledRegionSplitPolicy blocks manual region splitting.

译文

拆分策略确定什么时候应该分割区域。当前可用的其他各种拆分策略有BusyRegionSplitPolicy、ConstantSizeRegionSplitPolicy、DisabledRegionSplitPolicy、DempitedKeyPrefix RegionSplitPolicy、KeyPrefix RegionSplitPolicy和SteppingSplitPolicy。DisabledRegionSplitPolicy阻止手动区域拆分。

默认值:org.apache.hadoop.hbase.regionserver.SteppingSplitPolicy

hbase.regionserver.regionSplitLimit

原文

Limit for the number of regions after which no more region splitting should take place. This is not hard limit for the number of regions but acts as a guideline for the regionserver to stop splitting after a certain limit. Default is set to 1000.

译文

限制区域数目，在此之后不应再进行区域分割。这并不是区域数量的硬限制，而是区域服务器在一定限制之后停止拆分的指导方针。默认设置为1000。

默认值:1000

zookeeper.session.timeout

原文

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

译文

zookeeper会话超时，以毫秒为单位。它有两种不同的用法。首先，此值用于HBASE用于连接到集成的ZK客户端。在启动ZK服务器时，HBASE也会使用它，并将其作为“maxSessionTimeout”传递。看见

默认值:90000

zookeeper.znode.parent

原文

Root ZNode for HBase in ZooKeeper. All of HBase’s ZooKeeper files that are configured with a relative path will go under this node. By default, all of HBase’s ZooKeeper file paths are configured with a relative path, so they will all go under this directory unless changed.

译文

饲养员中HBASE的根Zode。所有使用相对路径配置的HBASEzookeeper文件都将位于此节点下。默认情况下，所有HBASE的zookeeper文件路径都配置了一个相对路径，因此除非更改，否则它们都将位于此目录下。

默认值:/hbase

zookeeper.znode.acl.parent

原文

Root ZNode for access control lists.

译文

访问控制列表的根Zode。

默认值:acl

hbase.zookeeper.dns.interface

原文

The name of the Network Interface from which a ZooKeeper server should report its IP address.

译文

网络接口的名称，从网络接口服务器应该报告其IP地址。

默认值:default

hbase.zookeeper.dns.nameserver

原文

The host name or IP address of the name server (DNS) which a ZooKeeper server should use to determine the host name used by the master for communication and display purposes.

译文

名称服务器(DNS)的主机名或IP地址，饲养员服务器应该使用它来确定主机用于通信和显示的主机名。

默认值:default

hbase.zookeeper.peerport

原文

Port used by ZooKeeper peers to talk to each other. See

译文

饲养员用来互相交谈的端口。看见

默认值:2888

hbase.zookeeper.leaderport

原文

Port used by ZooKeeper for leader election. See

译文

zookeeper用来选举领导人的港口。看见

默认值:3888

hbase.zookeeper.property.initLimit

原文

Property from ZooKeeper’s config zoo.cfg. The number of ticks that the initial synchronization phase can take.

译文

属性来自zookeeper的配置zoo.cfg。初始同步阶段可以采取的滴答数。

默认值:10

hbase.zookeeper.property.syncLimit

原文

Property from ZooKeeper’s config zoo.cfg. The number of ticks that can pass between sending a request and getting an acknowledgment.

译文

属性来自zookeeper的配置zoo.cfg。在发送请求和获得确认之间传递的蜱数。

默认值:5

hbase.zookeeper.property.dataDir

原文

Property from ZooKeeper’s config zoo.cfg. The directory where the snapshot is stored.

译文

属性来自zookeeper的配置zoo.cfg。存储快照的目录。

默认值:${hbase.tmp.dir}/zookeeper

hbase.zookeeper.property.clientPort

原文

Property from ZooKeeper’s config zoo.cfg. The port at which the clients will connect.

译文

属性来自zookeeper的配置zoo.cfg。客户端连接的端口。

默认值:2181

hbase.zookeeper.property.maxClientCnxns

原文

Property from ZooKeeper’s config zoo.cfg. Limit on number of concurrent connections (at the socket level) that a single client, identified by IP address, may make to a single member of the ZooKeeper ensemble. Set high to avoid zk connection issues running standalone and pseudo-distributed.

译文

属性来自zookeeper的配置zoo.cfg。限制单个客户端由IP地址标识的并发连接的数量(在套接字级别)，可以对zookeeper集合的单个成员进行限制。设置高，以避免ZK连接问题，运行独立和伪分布式。

默认值:300

hbase.client.write.buffer

原文

Default size of the BufferedMutator write buffer in bytes. A bigger buffer takes more memory — on both the client and server side since server instantiates the passed write buffer to process it — but a larger buffer size reduces the number of RPCs made. For an estimate of server-side memory-used, evaluate hbase.client.write.buffer * hbase.regionserver.handler.count

译文

BufferedMutator写入缓冲区的默认大小(以字节为单位)。一个更大的缓冲区需要更多的内存–在客户端和服务器端，因为服务器实例化传递的写缓冲区来处理它–但是更大的缓冲区大小减少了所制造的RPC的数量。对于服务器端内存使用的估计，请计算hbase.client.write.Buff*hbase.Regier.handler.count。

默认值:2097152

hbase.client.pause

原文

General client pause value. Used mostly as value to wait before running a retry of a failed get, region lookup, etc. See hbase.client.retries.number for description of how we backoff from this initial pause amount and how this pause works w/ retries.

译文

一般客户端暂停值。主要用作在运行失败的GET、区域查找等重试之前等待的值。有关我们如何从这个初始暂停量中退避以及此暂停如何工作的说明，请参见hbase.client.recerees.number。

默认值:100

hbase.client.pause.cqtbe

原文

Whether or not to use a special client pause for CallQueueTooBigException (cqtbe). Set this property to a higher value than hbase.client.pause if you observe frequent CQTBE from the same RegionServer and the call queue there keeps full

译文

是否对CallQueueTooBigException(Cqtbe)使用特殊的客户端暂停。如果您观察到来自同一RegionServer的频繁CQTBE，并且调用队列保持满，则将此属性设置为比hbase.client.停顿更高的值。

默认值:none

hbase.client.retries.number

原文

Maximum retries. Used as maximum for all retryable operations 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. At first we retry at this interval but then with backoff, we pretty quickly reach retrying every ten seconds. See HConstants#RETRY_BACKOFF for how the backup ramps up. Change this setting and hbase.client.pause to suit your workload.

译文

最大重试。用作所有可还原操作的最大值，例如获取单元格的值、启动行更新等。重试间隔是基于hbase.client.PARTE的粗略函数。一开始，我们在这段时间内重试，但在退却的情况下，我们很快就会每10秒重试一次。请参阅HConstants#retry_Backoff，了解备份是如何上升的。更改此设置和hbase.client.停顿以适应您的工作负载。

默认值:15

hbase.client.max.total.tasks

原文

The maximum number of concurrent mutation tasks a single HTable instance will send to the cluster.

译文

单个HTable实例将发送到集群的并发突变任务的最大数量。

默认值:100

hbase.client.max.perserver.tasks

原文

The maximum number of concurrent mutation tasks a single HTable instance will send to a single region server.

译文

单个HTable实例将发送到单个区域服务器的并发突变任务的最大数量。

默认值:2

hbase.client.max.perregion.tasks

原文

The maximum number of concurrent mutation tasks the client will maintain to a single Region. That is, if there is already hbase.client.max.perregion.tasks writes in progress for this region, new puts won’t be sent to this region until some writes finishes.

译文

客户端将维护到单个区域的并发突变任务的最大数量。也就是说，如果已经有hbase.client.max.perzone.任务正在为该区域写入，则在某些写入完成之前不会向该区域发送新的PUT。

默认值:1

hbase.client.perserver.requests.threshold

原文

The max number of concurrent pending requests for one server in all client threads (process level). Exceeding requests will be thrown ServerTooBusyException immediately to prevent user’s threads being occupied and blocked by only one slow region server. If you use a fix number of threads to access HBase in a synchronous way, set this to a suitable value which is related to the number of threads will help you. See

译文

所有客户端线程(进程级)中对一台服务器的最大并发挂起请求数。超出请求将立即抛出ServerTooBusyException，以防止用户的线程被一个慢速区域服务器占用和阻塞。如果您使用固定数量的线程以同步方式访问HBASE，则将其设置为与线程数量相关的适当值，这将有助于您。看见

默认值:2147483647

hbase.client.scanner.caching

原文

Number of rows that we try to fetch when calling next on a scanner if it is not served from (local, client) memory. This configuration works together with hbase.client.scanner.max.result.size to try and use the network efficiently. The default value is Integer.MAX_VALUE by default so that the network will fill the chunk size defined by hbase.client.scanner.max.result.size rather than be limited by a particular number of rows since the size of rows varies table to table. If you know ahead of time that you will not require more than a certain number of rows from a scan, this configuration should be set to that row limit via Scan#setCaching. Higher caching values will enable faster scanners but will eat up more memory 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 scanner timeout; i.e. hbase.client.scanner.timeout.period

译文

如果没有从(本地、客户端)内存中调用Next时，我们尝试获取的行数。此配置与hbase.client.scanner.max.Result.size一起工作，以有效地使用网络。默认值是Integer.MAX_value(默认情况下)，这样网络将填充由hbase.client.scanner.max.Result.size定义的块大小，而不是受特定行数的限制，因为行的大小随表的不同而不同。如果提前知道需要扫描的行数不超过一定数量，则应通过扫描#setCache将此配置设置为该行限制。更高的缓存值将支持更快的扫描器，但会占用更多的内存，当缓存为空时，Next的某些调用可能会花费越来越长的时间。不要设置此值，使调用之间的时间大于扫描器超时时间；即hbase.client.scanner.timeout。

默认值:2147483647

hbase.client.keyvalue.maxsize

原文

Specifies the combined maximum allowed size of a KeyValue instance. This is to set an upper boundary for a single entry saved in a storage file. Since they cannot be split it helps avoiding that a region cannot be split any further because the data is too large. It seems wise to set this to a fraction of the maximum region size. Setting it to zero or less disables the check.

译文

指定KeyValue实例的组合允许的最大大小。这是为保存在存储文件中的单个条目设置上边界。由于它们不能分开，这有助于避免由于数据太大而不能进一步分割区域。将其设置为最大区域大小的一小部分似乎是明智的。将其设置为零或更少将禁用检查。

默认值:10485760

hbase.server.keyvalue.maxsize

原文

Maximum allowed size of an individual cell, inclusive of value and all key components. 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.

译文

每个单元格的最大允许大小，包括值和所有关键组件。值为0或更少的值将禁用该检查。默认值为10 MB。这是一个安全设置，以保护服务器不受OOM情况的影响。

默认值:10485760

hbase.client.scanner.timeout.period

原文

Client scanner lease period in milliseconds.

译文

客户端扫描器租赁期(毫秒)。

默认值:60000

hbase.bulkload.retries.number

原文

Maximum retries. This is maximum number of iterations to atomic bulk loads are attempted in the face of splitting operations 0 means never give up.

译文

最大重试。这是对原子大容量负载的最大迭代次数，在拆分操作的情况下，0表示永不放弃。

默认值:10

hbase.compaction.after.bulkload.enable

原文

Request Compaction after bulkload immediately. If bulkload is continuous, the triggered compactions may increase load, bring about performance side effect.

译文

大容量装载后立即请求压实。如果负荷是连续的，触发压实可能会增加负荷，带来性能副作用。

默认值:false

hbase.master.balancer.maxRitPercent

原文

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.

译文

平衡时过渡区域的最大百分比。默认值为1.0。所以没有平衡器节流。如果将此配置设置为0.01，则表示平衡时最多有1%的区域处于过渡状态。然后，当平衡时，集群的可用性至少是99%。

默认值:1.0

hbase.balancer.period

原文

Period at which the region balancer runs in the Master, in milliseconds.

译文

区域平衡器在主程序中运行的时间段，以毫秒为单位。

默认值:300000

hbase.regions.slop

原文

Rebalance if any regionserver has average + (average * slop) regions. The default value of this parameter is 0.001 in StochasticLoadBalancer (the default load balancer), while the default is 0.2 in other load balancers (i.e., SimpleLoadBalancer).

译文

如果任何区域服务器都有平均+(平均*斜率)区域，则重新平衡。在StochasticLoadBalenger(默认负载均衡器)中，此参数的默认值为0.001，而在其他负载平衡器中，默认值为0.2(即SimpleLoadBalenger)。

默认值:0.001

hbase.normalizer.period

原文

Period at which the region normalizer runs in the Master, in milliseconds.

译文

区域归一化器在母版中运行的周期，以毫秒为单位。

默认值:300000

hbase.normalizer.split.enabled

原文

Whether to split a region as part of normalization.

译文

是否分割一个区域作为正常化的一部分。

默认值:true

hbase.normalizer.merge.enabled

原文

Whether to merge a region as part of normalization.

译文

是否合并一个区域作为规范化的一部分。

默认值:true

hbase.normalizer.min.region.count

原文

The minimum number of regions in a table to consider it for merge normalization.

译文

表中考虑合并规范化的最小区域数。

默认值:3

hbase.normalizer.merge.min_region_age.days

原文

The minimum age for a region to be considered for a merge, in days.

译文

考虑合并的区域的最低年龄，以天为单位。

默认值:3

hbase.normalizer.merge.min_region_age.days

原文

The minimum age for a region to be considered for a merge, in days.

译文

考虑合并的区域的最低年龄，以天为单位。

默认值:3

hbase.normalizer.merge.min_region_size.mb

原文

The minimum size for a region to be considered for a merge, in whole MBs.

译文

要考虑合并的区域的最小大小，在整个MBS中。

默认值:1

hbase.server.thread.wakefrequency

原文

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 tune flushing and compaction check interval by hbase.regionserver.flush.check.period and hbase.regionserver.compaction.check.period. (in milliseconds)

译文

在主服务器端，此配置用于FS相关行为：检查HDFS是否处于安全模式，设置或检查hbase.version文件，设置或检查hbase.id文件。使用默认值应该可以。在地区服务器端，此配置用于几个位置：冲洗检查间隔、压实检查间隔、Wal滚动检查间隔。特别是，ADMIN可以通过hbase.Regiserver.flush.check.time和hbase.Regiserver.compaction.check.time来调整刷新和压缩检查间隔。(以毫秒为单位)

默认值:10000

hbase.regionserver.flush.check.period

原文

It determines the flushing check period of PeriodicFlusher in regionserver. If unset, it uses hbase.server.thread.wakefrequency as default value. (in milliseconds)

译文

确定了分区服务器中周期清洗机的冲洗检查周期。如果未设置，则使用hbase.server.线程。(以毫秒为单位)

默认值:${hbase.server.thread.wakefrequency}

hbase.regionserver.compaction.check.period

原文

It determines the compaction check period of CompactionChecker in regionserver. If unset, it uses hbase.server.thread.wakefrequency as default value. (in milliseconds)

译文

它确定了区域服务器中CompactionChecker的压缩检查周期。如果未设置，则使用hbase.server.线程。(以毫秒为单位)

默认值:${hbase.server.thread.wakefrequency}

hbase.server.versionfile.writeattempts

原文

How many times to retry attempting to write a version file before just aborting. Each attempt is separated by the hbase.server.thread.wakefrequency milliseconds.

译文

在中止之前，要尝试编写版本文件多少次。每一次尝试都由hbase.server.线程.唤醒频率毫秒分隔。

默认值:3

hbase.hregion.memstore.flush.size

原文

Memstore will be flushed to disk if size of the memstore exceeds this number of bytes. Value is checked by a thread that runs every hbase.server.thread.wakefrequency.

译文

如果memstore的大小超过此字节数，则memstore将被刷新到磁盘。值由一个线程检查，该线程运行每个hbase.server.线程。

默认值:134217728

hbase.hregion.percolumnfamilyflush.size.lower.bound.min

原文

If FlushLargeStoresPolicy is used and there are multiple column families, then every time that we hit the total memstore limit, we find out all the column families whose memstores exceed a “lower bound” and only flush them while retaining the others in memory. The “lower bound” will be “hbase.hregion.memstore.flush.size / column_family_number” by default unless value of this property is larger than that. If none of the families have their memstore size more than lower bound, all the memstores will be flushed (just as usual).

译文

如果使用的是FlushLargeStoresPolicy，并且有多个列族，那么每次我们达到MemStore的总限制时，我们都会找出它的所有列族，它们的内存超过“下限”，并且只在内存中保存其他列族。默认情况下，“下限”将是“hbase.hRegi.memstore.flush.size/Column_CONERY”，除非此属性的值大于该值。如果没有一个家庭的记忆商店的大小超过下限，所有的备忘录将被刷新(就像往常一样)。

默认值:16777216

hbase.hregion.preclose.flush.size

原文

If the memstores in a region are this size or larger when we go to close, run a “pre-flush” to clear out memstores before we put up the region closed flag and take the region offline. On close, a flush is run under the close flag to empty memory. During this 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 to complete. The preflush is meant to clean out the bulk of the memstore before putting up the close flag and taking the region offline so the flush that runs under the close flag has little to do.

译文

当我们关闭时，如果区域中的Memstore是这样大小或更大的，那么在我们挂起区域关闭标志并使区域离线之前，运行一个“预刷新”来清除内存存储。关闭时，在关闭标志下运行刷新以空内存。在此期间，该区域处于脱机状态，我们不会进行任何写入操作。如果memstore内容很大，则此刷新可能需要很长时间才能完成。预刷新的目的是在挂起关闭标志并使区域离线之前清除memstore的大部分内容，因此在Close标志下运行的刷新几乎没有什么作用。

默认值:5242880

hbase.hregion.memstore.block.multiplier

原文

Block updates if memstore has hbase.hregion.memstore.block.multiplier times hbase.hregion.memstore.flush.size bytes. Useful preventing runaway memstore during spikes in update traffic. Without an upper-bound, memstore fills such that when it flushes the resultant flush files take a long time to compact or split, or worse, we OOME.

译文

块更新，如果memstore有hbase.hRegi.memstore.块.乘数乘以hbase.hRegi.memstore.flush.size字节。有效防止在更新流量尖峰期间失控的记忆存储。由于没有上限，所以当它刷新结果的刷新文件时，需要很长时间来压缩或拆分，或者更糟的是，我们需要很长时间才能完成OOME。

默认值:4

hbase.hregion.memstore.mslab.enabled

原文

Enables the MemStore-Local Allocation Buffer, a feature which works to prevent heap fragmentation under heavy write loads. This can reduce the frequency of stop-the-world GC pauses on large heaps.

译文

启用memStore-本地分配缓冲区，这是一种在重写负载下防止堆碎片的功能。这可以减少停止世界GC暂停在大堆上的频率.

默认值:true

hbase.hregion.memstore.mslab.chunksize

原文

The maximum byte size of a chunk in the MemStoreLAB. Unit: bytes

译文

MemStorelab中块的最大字节大小。单位：字节

默认值:2097152

hbase.regionserver.offheap.global.memstore.size

原文

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 MSLAB will be HeapByteBuffer, otherwise the non-zero value means how many megabyte of off-heap memory will be used for chunks in MSLAB and all chunks in MSLAB will be DirectByteBuffer. Unit: megabytes.

译文

RegionServer中所有MemStores可能使用的堆外内存量。值为0意味着不使用堆外内存，MSlab中的所有块都将是HeapByteBuffer，否则，非零值意味着MSlab中的块将使用多少MB的堆外内存，而MSlab中的所有块将是DirectByteBuffer。单位：兆字节。

默认值:0

hbase.hregion.memstore.mslab.max.allocation

原文

The maximal size of one allocation in the MemStoreLAB, if the desired byte size exceed this threshold then it will be just allocated from JVM heap rather than MemStoreLAB.

译文

MemStorelab中一个分配的最大大小，如果想要的字节大小超过这个阈值，那么它将只从JVM堆而不是memStorelab分配。

默认值:262144

hbase.hregion.max.filesize

原文

Maximum file size. If the sum of the sizes of a region’s HFiles has grown to exceed this value, the region is split in two. There are two choices of how this option works, the first is when any store’s size exceed the threshold then split, and the other is overall region’s size exceed the threshold then split, it can be configed by hbase.hregion.split.overallfiles.

译文

最大文件大小。如果区域的HFiles的大小之和已超过此值，则该区域被分成两部分。关于该选项的工作方式有两种选择，第一种是当任何商店的大小超过阈值之后被分割，另一种是整个区域的大小超过阈值然后拆分，它可以由hbase.hRegi.split.overallfile来信任。

默认值:10737418240

hbase.hregion.split.overallfiles

原文

If we should sum overall region files size when check to split.

译文

如果我们应该加和整个区域文件大小时，检查为拆分。

默认值:true

hbase.hregion.majorcompaction

原文

Time between major compactions, expressed in milliseconds. Set to 0 to disable time-based automatic major compactions. User-requested and size-based major compactions will still run. This value is multiplied by hbase.hregion.majorcompaction.jitter to cause compaction to start at a somewhat-random time during a given window of time. The default value is 7 days, expressed in milliseconds. If major compactions are causing disruption in your environment, you can configure them to run at off-peak times for your deployment, or disable time-based major compactions by setting this parameter to 0, and run major compactions in a cron job or by another external mechanism.

译文

主要压缩之间的时间，以毫秒表示。设置为0以禁用基于时间的自动主要压缩。用户请求和基于大小的主要压缩仍将运行。此值乘以hbase.hRegi.mainorcompaction.jitter，从而使压缩在给定时间窗口内的某个随机时间开始。默认值为7天，以毫秒表示。如果主要压缩导致环境中断，则可以将它们配置为在部署的非高峰时间运行，或者通过将此参数设置为0来禁用基于时间的主要压缩，并在cron作业或其他外部机制中运行主要压缩。

默认值:604800000

hbase.hregion.majorcompaction.jitter

原文

A multiplier applied to hbase.hregion.majorcompaction to cause compaction to occur a given amount of time either side of hbase.hregion.majorcompaction. The smaller the number, the closer the compactions will happen to the hbase.hregion.majorcompaction interval.

译文

一种应用于hbase.hRegi.main压缩的乘法器，用于使压缩发生给定的时间，而hbase.hRegi.main的任何一侧都会发生压缩。数量越小，压实发生的时间就越近。

默认值:0.50

hbase.hstore.compactionThreshold

原文

If more than this number of StoreFiles exist in any one Store (one StoreFile is written per flush of MemStore), a compaction is run to rewrite all StoreFiles into a single StoreFile. Larger values delay compaction, but when compaction does occur, it takes longer to complete.

译文

如果在任何一个存储中存在超过此数量的StoreFiles(每次刷新memStore都会编写一个StoreFile)，则会运行压缩，将所有StoreFiles重写为一个StoreFile。较大的值会延迟压缩，但当压缩确实发生时，则需要更长的时间才能完成。

默认值:3

hbase.regionserver.compaction.enabled

原文

Enable/disable compactions on by setting true/false. We can further switch compactions dynamically with the compaction_switch shell command.

译文

通过设置true/false启用/禁用压缩。我们还可以使用压实_Switch shell命令动态地切换压实。

默认值:true

hbase.hstore.flusher.count

原文

The number of flush threads. With fewer threads, the MemStore flushes will be queued. With more threads, the flushes will be executed in parallel, increasing the load on HDFS, and potentially causing more compactions.

译文

冲洗线程的数目。使用较少的线程，memStore刷新将被排队。使用更多的线程，刷新将并行执行，从而增加HDFS的负载，并可能导致更多的压缩。

默认值:2

hbase.hstore.blockingStoreFiles

原文

If more than this number of StoreFiles exist in any one Store (one StoreFile is written per flush of MemStore), updates are blocked for this region until a compaction is completed, or until hbase.hstore.blockingWaitTime has been exceeded.

译文

如果在任何一个存储中存在超过此数量的StoreFiles(在memStore的每个刷新中写入一个StoreFile)，则将阻止此区域的更新，直到完成压缩，或直到超过hbase.hstore.block ingWaitTime为止。

默认值:16

hbase.hstore.blockingWaitTime

原文

The time for which a region will block updates after reaching the StoreFile limit defined by hbase.hstore.blockingStoreFiles. After this time has elapsed, the region will stop blocking updates even if a compaction has not been completed.

译文

在达到hbase.hstore.block ingStoreFiles定义的StoreFile限制之后，区域阻止更新的时间。过了这段时间后，即使压缩尚未完成，该区域也将停止阻塞更新。

默认值:90000

hbase.hstore.compaction.min

原文

The minimum number of StoreFiles which must be eligible for compaction before compaction can run. The goal of tuning hbase.hstore.compaction.min is to avoid ending up with too many tiny StoreFiles to compact. Setting this value to 2 would cause a minor compaction each time you have two StoreFiles in a Store, and this is probably not appropriate. If you set this value too high, all the other values will need to be adjusted accordingly. For most cases, the default value is appropriate (empty value here, results in 3 by code logic). In previous versions of HBase, the parameter hbase.hstore.compaction.min was named hbase.hstore.compactionThreshold.

译文

压缩之前必须符合压缩条件的StoreFiles的最小数量。优化hbase.hstore.compaction.min的目标是避免过多的小型StoreFiles压缩。如果将此值设置为2，则每次在Store中有两个StoreFiles时都会造成较小的压缩，这可能是不合适的。如果将此值设置得太高，则需要相应地调整所有其他值。在大多数情况下，默认值是适当的(此处为空值，由代码逻辑得到3)。在HBASE的早期版本中，参数hbase.hstore.compaction.min被命名为hbase.hstore.compactionThresHolding。

默认值:none

hbase.hstore.compaction.max

原文

The maximum number of StoreFiles which will be selected for a single minor compaction, regardless of the number of eligible StoreFiles. Effectively, the value of hbase.hstore.compaction.max controls the length of time it takes a single compaction to complete. Setting it larger means that more StoreFiles are included in a compaction. For most cases, the default value is appropriate.

译文

将为单个小压缩选择的最大StoreFiles数，而不考虑合格StoreFiles的数量。实际上，hbase.hstore.compaction.max的值控制完成一次压缩所需的时间长度。将其设置为更大意味着压缩中包含了更多StoreFiles。在大多数情况下，默认值是适当的。

默认值:10

hbase.hstore.compaction.min.size

原文

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 if they are eligible. Because this limit represents the “automatic include” limit for all StoreFiles smaller than this value, this value may need to be reduced in write-heavy environments where many StoreFiles in the 1-2 MB range are being flushed, because every StoreFile will be targeted for compaction and the resulting StoreFiles may still be under the minimum size and require further compaction. If this parameter is lowered, the ratio check is triggered more quickly. This addressed some issues seen in earlier versions of HBase but changing this parameter is no longer necessary in most situations. Default: 128 MB expressed in bytes.

译文

小于这个大小的StoreFile(或StoreFiles的选择，当使用ExploringCompactionPolicy时)总是有资格进行较小的压缩。HFiles此大小或更大的文件由hbase.hstore.compaction.充足率进行评估，以确定它们是否合格。由于此限制表示小于此值的所有StoreFiles的“自动包含”限制，因此在许多1-2 MB范围内的StoreFiles正在被刷新的情况下，可能需要减少此值，因为每个StoreFile都将成为压缩的目标，由此产生的StoreFiles可能仍然处于最小大小，需要进一步压缩。如果降低了此参数，则会更快地触发比率检查。这解决了HBASE早期版本中出现的一些问题，但在大多数情况下不再需要更改此参数。默认值：128 MB，以字节表示。

默认值:134217728

hbase.hstore.compaction.max.size

原文

A StoreFile (or a selection of StoreFiles, when using ExploringCompactionPolicy) larger than this size will be excluded from compaction. The effect of raising hbase.hstore.compaction.max.size is fewer, larger StoreFiles that do not get compacted often. If you feel that compaction is happening too often without much benefit, you can try raising this value. Default: the value of LONG.MAX_VALUE, expressed in bytes.

译文

大于此大小的StoreFile(或StoreFiles的选择，当使用Explorer ingCompactionPolicy时)将被排除在压缩之外。提高hbase.hstore.compaction.max.size的效果是不经常压缩的更小、更大的StoreFiles。如果您觉得压实发生得太频繁，没有什么好处，您可以尝试提高此值。默认值：LONG.MAX_VALUE的值，以字节表示。

默认值:9223372036854775807

hbase.hstore.compaction.ratio

原文

For minor compaction, this ratio is used to determine whether a given StoreFile which is larger than hbase.hstore.compaction.min.size is eligible for compaction. Its effect is to limit compaction of large StoreFiles. The value of hbase.hstore.compaction.ratio is expressed as a floating-point decimal. A large ratio, such as 10, will produce a single giant StoreFile. Conversely, a low value, such as .25, will produce behavior similar to the BigTable compaction algorithm, producing four StoreFiles. A moderate value of between 1.0 and 1.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 will compact larger StoreFiles. However, during reads, HBase will need to seek through fewer StoreFiles to accomplish the read. Consider this approach if you cannot take advantage of Bloom filters. Otherwise, you can lower this value to something like 1.0 to reduce the background cost of writes, and use Bloom filters to control the number of StoreFiles touched during reads. For most cases, the default value is appropriate.

译文

对于较小的压缩，此比率用于确定大于hbase.hstore.compaction.min.size的给定StoreFile是否符合压缩条件。其效果是限制大型存储文件的压缩。Hbase.hstore.compaction.Rate的值表示为浮点小数点。一个很大的比率，如10，将产生一个巨大的存储文件。相反，低值(如.25)将产生类似于BigTable压缩算法的行为，生成四个StoreFiles。建议采用1.0到1.4之间的适度值。在调优此值时，您正在平衡写入成本和读取成本。将值提高(大约为1.4)将有更多的写入成本，因为您将压缩更大的StoreFiles。然而，在读取期间，HBASE将需要通过更少的StoreFiles来完成读取。如果不能利用Bloom过滤器，请考虑这种方法。否则，您可以将此值降低到1.0这样的值，以降低写入的后台成本，并使用Bloom过滤器来控制读取期间接触到的StoreFiles的数量。在大多数情况下，默认值是适当的。

默认值:1.2F

hbase.hstore.compaction.ratio.offpeak

原文

Allows you to set a different (by default, more aggressive) ratio for determining whether larger StoreFiles are included in compactions during off-peak hours. Works in the same way as hbase.hstore.compaction.ratio. Only applies if hbase.offpeak.start.hour and hbase.offpeak.end.hour are also enabled.

译文

允许您设置不同的(默认情况下，更具侵略性)比率，以确定在非高峰时间压缩中是否包括更大的StoreFiles。工作方式与hbase.hstore.compaction.充足率相同。只有在启用hbase.offpeak.start.time和hbase.offpeak.end.time时才适用。

默认值:5.0F

hbase.hstore.time.to.purge.deletes

原文

The amount of time to delay purging of delete markers with future timestamps. If unset, or set to 0, all delete markers, including those with future timestamps, are purged during the next major compaction. Otherwise, a delete marker is kept until the major compaction which occurs after the marker’s timestamp plus the value of this setting, in milliseconds.

译文

延迟清除带有未来时间戳的删除标记的时间。如果未设置或设置为0，则在下一次主要压缩过程中清除所有删除标记，包括具有未来时间戳的标记。否则，删除标记将保留到标记的时间戳加上此设置的值(以毫秒为单位)之后发生的主要压缩为止。

默认值:0

hbase.offpeak.start.hour

原文

The start of off-peak hours, expressed as an integer between 0 and 23, inclusive. Set to -1 to disable off-peak.

译文

非高峰时段的开始，以0到23之间的整数表示，包括在内.设置为-1以禁用非峰值。

默认值:-1

hbase.offpeak.end.hour

原文

The end of off-peak hours, expressed as an integer between 0 and 23, inclusive. Set to -1 to disable off-peak.

译文

非高峰时间的结束，以0到23之间的整数表示，包括在内.设置为-1以禁用非峰值。

默认值:-1

hbase.regionserver.thread.compaction.throttle

原文

There are two different thread pools for compactions, one for large compactions and the other for small compactions. This helps to keep compaction of lean tables (such as hbase:meta) fast. If a compaction is larger than this threshold, it goes 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 from the default.

译文

有两个不同的线程池用于压缩，一个用于大型压缩，另一个用于小型压缩。这有助于快速压缩精益表(如HBASE：META)。如果压缩大于此阈值，则进入大型压缩池。在大多数情况下，默认值是适当的。默认值：2xhbase.hstore.compaction.max x hbase.hRegi.memstore.flush.size(默认值为128 MB)。Value字段假定hbase.hRegi.memstore.flush.size的值与默认值保持不变。

默认值:2684354560

hbase.regionserver.majorcompaction.pagecache.drop

原文

Specifies whether to drop pages read/written into the system page cache by major compactions. Setting it to true helps prevent major compactions from polluting the page cache, which is almost always required, especially for clusters with low/moderate memory to storage ratio.

译文

指定是否按主要压缩将读/写到系统页缓存中的页删除。将其设置为true有助于防止主要压缩污染页面缓存，这几乎总是必需的，特别是对于内存/存储比较低/中等的集群。

默认值:true

hbase.regionserver.minorcompaction.pagecache.drop

原文

Specifies whether to drop pages read/written into the system page cache by minor compactions. Setting it to true helps prevent minor compactions from polluting the page cache, which is most beneficial on clusters with low memory to storage ratio or very write heavy clusters. You may want to set it to false under moderate to low write workload when bulk of the reads are on the most recently written data.

译文

指定是否按次要压缩将读/写到系统页缓存中的页删除。将其设置为TRUE有助于防止小压缩污染页面缓存，这对于内存与存储比较低或写入量很大的集群最为有利。当大部分读取是在最近编写的数据上时，您可能希望在中等到低的写入工作负载下将其设置为false。

默认值:true

hbase.hstore.compaction.kv.max

原文

The maximum number of KeyValues to read and then write in a batch when flushing or compacting. Set this lower if you have big KeyValues and problems with Out Of Memory Exceptions Set this higher if you have wide, small rows.

译文

冲洗或压缩时要在批处理中读取和写入的最大键值数。如果您有大的KeyValue，那么将这个值设置得更低，如果您有宽的、小的行，则在内存异常情况下设置这个值。

默认值:10

hbase.storescanner.parallel.seek.enable

原文

Enables StoreFileScanner parallel-seeking in StoreScanner, a feature which can reduce response latency under special conditions.

译文

在StoreScaner中启用StoreFileScaner并行搜索，这是一种在特殊情况下可以减少响应延迟的功能。

默认值:false

hbase.storescanner.parallel.seek.threads

原文

The default thread pool size if parallel-seeking feature enabled.

译文

如果启用并行查找功能，则默认线程池大小。

默认值:10

hfile.block.cache.policy

原文

The eviction policy for the L1 block cache (LRU or TinyLFU).

译文

L1块缓存(LRU或TinyLFU)的驱逐策略。

默认值:LRU

hfile.block.cache.size

原文

Percentage of maximum heap (-Xmx setting) to allocate to block cache used by a StoreFile. Default of 0.4 means allocate 40%. Set to 0 to disable but it’s not recommended; you need at least enough cache to hold the storefile indices.

译文

分配给StoreFile使用的块缓存的最大堆(-XMX设置)百分比。违约0.4意味着分配40%。设置为0以禁用，但不建议禁用；您至少需要足够的缓存来保存存储文件索引。

默认值:0.4

hfile.block.index.cacheonwrite

原文

This allows to put non-root multi-level index blocks into the block cache at the time the index is being written.

译文

这允许在写入索引时将非根多层索引块放入块缓存中。

默认值:false

hfile.index.block.max.size

原文

When the size of a leaf-level, intermediate-level, or root-level index block in a multi-level block index grows to this size, the block is written out and a new block is started.

译文

当多级块索引中的叶级、中间级或根级索引块的大小增长到此大小时，将写入该块并启动一个新块。

默认值:131072

hbase.bucketcache.ioengine

原文

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

译文

存储存储桶缓存内容的位置。其中之一：堆，文件，文件，mmap或pmem。如果一个或多个文件，将其设置为file(S)：path_to_file。Mmap意味着内容将在mmaped文件中。使用mmap：path_to_file。“pmem”是存储在持久内存设备上的文件上的桶缓存。使用pmem：path_to_file。看见

默认值:none

hbase.hstore.compaction.throughput.lower.bound

原文

The target lower bound on aggregate compaction throughput, in bytes/sec. Allows you to tune the minimum available compaction throughput when the PressureAwareCompactionThroughputController throughput controller is active. (It is active by default.)

译文

聚合压缩吞吐量的目标下限，以字节/秒为单位。允许您在PressureAwareCompactionThrouputController吞吐量控制器处于活动状态时调整最小可用的压缩吞吐量。(默认情况下它是活动的。)

默认值:52428800

hbase.hstore.compaction.throughput.higher.bound

原文

The target upper bound on aggregate compaction throughput, in bytes/sec. Allows you to control aggregate compaction throughput demand when the PressureAwareCompactionThroughputController throughput controller is active. (It is active by default.) The maximum throughput will be tuned between the lower and upper bounds when compaction pressure is within the range [0.0, 1.0]. If compaction pressure is 1.0 or greater the higher bound will be ignored until pressure returns to the normal range.

译文

聚合压缩吞吐量的目标上限，以字节/秒为单位。允许您在PressureAwareCompactionThrouputController吞吐量控制器处于活动状态时控制聚合压缩吞吐量需求。(默认情况下它是活动的。)当压实压力在[0.0，1.0]范围内时，最大吞吐量将在上下界之间进行调优。如果压实压力为1.0或更高，则会忽略更高的界限，直到压力恢复到正常范围。

默认值:104857600

hbase.bucketcache.size

原文

It is the total capacity in megabytes of BucketCache. Default: 0.0

译文

它是总容量，以兆字节的桶Cache。缺省值：0.0

默认值:none

hbase.bucketcache.bucket.sizes

原文

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 set in code (See BucketAllocator#DEFAULT_BUCKET_SIZES).

译文

用逗号分隔的存储桶大小列表。可以是多种尺寸。列出从最小到最大的块大小。您使用的大小将取决于您的数据访问模式。必须是256的倍数，否则当您从缓存中读取时，您将遇到‘java.io.IOException：无效的HFile块魔术’。如果在这里没有指定值，那么可以在代码中选择默认的桶大小(请参见BucketAllocator#default_bucket_size)。

默认值:none

hfile.format.version

原文

The HFile format version to use for new files. Version 3 adds support for tags in hfiles (See

译文

用于新文件的HFile格式版本。版本3增加了对hfiles中标记的支持(请参阅

默认值:3

hfile.block.bloom.cacheonwrite

原文

Enables cache-on-write for inline blocks of a compound Bloom filter.

译文

为复合Bloom过滤器的内联块启用缓存上写。

默认值:false

io.storefile.bloom.block.size

原文

The size in bytes of a single block (“chunk”) of a compound Bloom filter. This size is approximate, because Bloom blocks can only be inserted at data block boundaries, and the number of keys per data block varies.

译文

复合Bloom过滤器的单个块(“块”)的大小(以字节为单位)。这个大小是近似的，因为Bloom块只能插入数据块边界，而且每个数据块的键数不同。

默认值:131072

hbase.rs.cacheblocksonwrite

原文

Whether an HFile block should be added to the block cache when the block is finished.

译文

当块完成时，是否应该将HFile块添加到块缓存中。

默认值:false

hbase.rpc.timeout

原文

This is for the RPC layer to define how long (millisecond) HBase client applications take for a remote call to time out. It uses pings to check connections but will eventually throw a TimeoutException.

译文

这是为了让RPC层定义一个远程调用超时所需的时间(毫秒)HBASE客户端应用程序。它使用pings来检查连接，但最终会抛出一个TimeoutException。

默认值:60000

hbase.client.operation.timeout

原文

Operation timeout is a top-level restriction (millisecond) that makes sure a blocking operation in Table will not be blocked more than this. In each operation, if rpc request fails because of timeout or other reason, it will retry until success or throw RetriesExhaustedException. But if the total time being blocking reach the operation timeout before retries exhausted, it will break early and throw SocketTimeoutException.

译文

操作超时是一个顶级限制(毫秒)，它确保表中的阻塞操作不会被阻塞更多。在每个操作中，如果RPC请求由于超时或其他原因而失败，它将重试直到成功或抛出检索ExhaustedException。但是，如果阻塞的总时间在重试耗尽之前到达操作超时，它将提前中断并抛出SocketTimeoutException。

默认值:1200000

hbase.cells.scanned.per.heartbeat.check

原文

The number of cells scanned in between heartbeat checks. Heartbeat checks occur during the processing of scans to determine whether or not the server should stop scanning in order to send back a heartbeat message to the client. Heartbeat messages are used to keep the client-server connection alive during long running scans. Small values mean that the heartbeat checks will occur more often and thus will provide a tighter bound on the execution time of the scan. Larger values mean that the heartbeat checks occur less frequently

译文

在心跳检查之间扫描的细胞数。在处理扫描过程中会进行心跳检查，以确定服务器是否应该停止扫描，以便向客户端发回心跳消息。心跳消息用于在长时间运行扫描期间保持客户机-服务器连接活动。较小的值意味着心跳检查将更频繁地发生，因此将对扫描的执行时间提供更严格的限制。较大的值意味着心跳检查发生的频率较低。

默认值:10000

hbase.rpc.shortoperation.timeout

原文

This is another version of “hbase.rpc.timeout”. For those RPC operation within cluster, we rely on this configuration to set a short timeout limitation for short operation. For example, short rpc timeout for region server’s trying to report to active master can benefit quicker master failover process.

译文

这是另一个版本的“hbase.rpc.timeout”。对于集群中的那些RPC操作，我们依靠此配置为短操作设置一个短超时限制。例如，区域服务器试图向活动主服务器报告的rpc超时时间较短，可以帮助加快主故障转移过程。

默认值:10000

hbase.ipc.client.tcpnodelay

原文

Set no delay on rpc socket connections. See

译文

不延迟RPC套接字连接。看见

默认值:true

hbase.unsafe.regionserver.hostname

原文

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

译文

这个配置是为专家准备的：除非您真正知道自己在做什么，否则不要设置它的值。当设置为非空值时，这表示基础服务器的(面向外部的)主机名。见

默认值:none

hbase.unsafe.regionserver.hostname.disable.master.reversedns

原文

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 will skip reverse DNS lookup and use the hostname sent by regionserver instead. Note that this config and hbase.unsafe.regionserver.hostname are mutually exclusive. See

译文

这个配置是为专家准备的：除非您真正知道自己在做什么，否则不要设置它的值。当设置为true时，Region服务器将为ServerName使用当前节点主机名，而HMaster将跳过反向DNS查找，而使用由Region服务器发送的主机名。请注意，此配置和hbase.unsecurity.Regiserver.hostname是互斥的。看见

默认值:false

hbase.master.keytab.file

原文

Full path to the kerberos keytab file to use for logging in the configured HMaster server principal.

译文

用于在配置的HMaster服务器主体中登录的Kerberos keytab文件的完整路径。

默认值:none

hbase.master.kerberos.principal

原文

Ex. “hbase/_HOST@EXAMPLE.COM”. The kerberos principal name that should be used to run the HMaster process. The principal name should be in the form: user/hostname@DOMAIN. If “_HOST” is used as the hostname portion, it will be replaced with the actual hostname of the running instance.

译文

前。“HBASE/_host@example.com”。用于运行HMaster进程的Kerberos主体名称。主体名称应该以以下形式显示：user/hostname@Domain。如果使用“_host”作为主机名部分，则它将被替换为正在运行的实例的实际主机名。

默认值:none

hbase.regionserver.keytab.file

原文

Full path to the kerberos keytab file to use for logging in the configured HRegionServer server principal.

译文

用于登录配置的HRegionServer服务器主体的Kerberos keytab文件的完整路径。

默认值:none

hbase.regionserver.kerberos.principal

原文

Ex. “hbase/_HOST@EXAMPLE.COM”. The kerberos principal name that should be used to run the HRegionServer process. The principal name should be in the form: user/hostname@DOMAIN. If “_HOST” is used as the hostname portion, it will be replaced with the actual hostname of the running instance. An entry for this principal must exist in the file specified in hbase.regionserver.keytab.file

译文

前。“HBASE/_host@example.com”。用于运行HRegionServer进程的Kerberos主体名称。主体名称应该以以下形式显示：user/hostname@Domain。如果使用“_host”作为主机名部分，则它将被替换为正在运行的实例的实际主机名。此主体的条目必须存在于hbase.Regiserver.keytab.file中指定的文件中。

默认值:none

hadoop.policy.file

原文

The policy configuration file used by RPC servers to make authorization decisions on client requests. Only used when HBase security is enabled.

译文

RPC服务器用于对客户端请求进行授权决策的策略配置文件。仅在启用HBASE安全性时才使用。

默认值:hbase-policy.xml

hbase.superuser

原文

List of users or groups (comma-separated), who are allowed full privileges, regardless of stored ACLs, across the cluster. Only used when HBase security is enabled.

译文

用户或组的列表(以逗号分隔)，这些用户或组被允许在集群中使用完整的特权，而不管所存储的ACL是什么。仅在启用HBASE安全性时才使用。

默认值:none

hbase.auth.key.update.interval

原文

The update interval for master key for authentication tokens in servers in milliseconds. Only used when HBase security is enabled.

译文

服务器中身份验证令牌的主密钥更新间隔(毫秒)。仅在启用HBASE安全性时才使用。

默认值:86400000

hbase.auth.token.max.lifetime

原文

The maximum lifetime in milliseconds after which an authentication token expires. Only used when HBase security is enabled.

译文

验证令牌到期后的最大生存期(毫秒)。仅在启用HBASE安全性时才使用。

默认值:604800000

hbase.ipc.client.fallback-to-simple-auth-allowed

原文

When a client is configured to attempt a secure connection, but attempts to connect to an insecure server, that server may instruct the client to switch to SASL SIMPLE (unsecure) authentication. This setting controls whether or not the client will accept this instruction from the server. When false (the default), the client will not allow the fallback to SIMPLE authentication, and will abort the connection.

译文

当客户端被配置为尝试安全连接，但试图连接到不安全的服务器时，该服务器可能会指示客户端切换到SASL简单(不安全)身份验证。此设置控制客户端是否接受来自服务器的此指令。如果为false(默认)，客户端将不允许回退到简单身份验证，并将中止连接。

默认值:false

hbase.ipc.server.fallback-to-simple-auth-allowed

原文

When a server is configured to require secure connections, it will reject connection attempts from clients using SASL SIMPLE (unsecure) authentication. This setting allows secure servers to accept SASL SIMPLE connections from clients when the client requests. When false (the default), the server will not allow the fallback to SIMPLE authentication, and will reject the connection. WARNING: This setting should ONLY be used as a temporary measure while converting clients over to secure authentication. It MUST BE DISABLED for secure operation.

译文

当服务器被配置为需要安全连接时，它将拒绝使用SASL简单(不安全)身份验证的客户端的连接尝试。此设置允许安全服务器在客户端请求时接受来自客户端的SASL简单连接。如果为false(默认值)，服务器将不允许回退到简单身份验证，并将拒绝连接。警告：在将客户端转换为安全身份验证时，只应将此设置用作临时措施。为了安全操作，必须禁用它。

默认值:false

hbase.unsafe.client.kerberos.hostname.disable.reversedns

原文

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 provided hostname of the destination for the principal instead. See

译文

这个配置是为专家准备的：除非您真正知道自己在做什么，否则不要设置它的值。当设置为true时，使用SASL Kerberos的HBASE客户端将跳过反向DNS查找，而使用主体提供的目的地主机名。看见

默认值:false

hbase.display.keys

原文

When this is set to true the webUI and such will display all start/end keys as part of the table details, region names, etc. When this is set to false, the keys are hidden.

译文

当此设置为true时，WebUI将显示所有开始/结束键，作为表详细信息、区域名称等的一部分。当设置为false时，这些键将被隐藏。

默认值:true

hbase.coprocessor.enabled

原文

Enables or disables coprocessor loading. If ‘false’ (disabled), any other coprocessor related configuration will be ignored.

译文

启用或禁用协处理器加载。如果“false”(禁用)，任何其他协处理器相关配置都将被忽略。

默认值:true

hbase.coprocessor.user.enabled

原文

Enables or disables user (aka. table) coprocessor loading. If ‘false’ (disabled), any table coprocessor attributes in table descriptors will be ignored. If “hbase.coprocessor.enabled” is ‘false’ this setting has no effect.

译文

启用或禁用用户(又名。(表)协处理器加载。如果“false”(禁用)，表描述符中的任何表协处理器属性都将被忽略。如果“hbase.coprocessor.启用”是‘false’，则此设置没有任何效果。

默认值:true

hbase.coprocessor.region.classes

原文

A comma-separated list of region observer or endpoint coprocessors that 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 the HBase shell.

译文

默认情况下在所有表上加载的区域观察者或端点协处理器的逗号分隔列表。对于任何重写协处理器方法，将按顺序调用这些类。在实现您自己的协处理器之后，将它添加到HBASE的类路径中，并在这里添加完全限定的类名。还可以通过设置HTableDescriptor或HBASE外壳按需加载协处理器。

默认值:none

hbase.coprocessor.master.classes

原文

A comma-separated list of org.apache.hadoop.hbase.coprocessor.MasterObserver coprocessors that are loaded by default on the active HMaster process. For any implemented coprocessor methods, the listed classes will be called in order. After implementing your own MasterObserver, just put it in HBase’s classpath and add the fully qualified class name here.

译文

默认情况下在Active HMaster进程上加载的以逗号分隔的org.apache.hadoop.hbase.coprocessor.MasterObserver协处理器列表。对于任何已实现的协处理器方法，将按顺序调用列出的类。在实现您自己的Master观察者之后，只需将其放入HBASE的类路径中，并在这里添加完全限定的类名。

默认值:none

hbase.coprocessor.abortonerror

原文

Set to true to cause the hosting server (master or regionserver) to abort if a coprocessor fails to load, fails to initialize, or throws an unexpected Throwable object. Setting this to false will allow the server to continue execution but the system wide state of the coprocessor in question will become inconsistent as it will be properly executing in only a subset of servers, so this is most useful for debugging only.

译文

如果协处理器无法加载、无法初始化或抛出意外的Throwable对象，则设置为true将导致宿主服务器(主服务器或地区服务器)中止。将此设置为false将允许服务器继续执行，但所讨论的协处理器的系统范围状态将变得不一致，因为它将仅在一组服务器上正确执行，因此只对调试非常有用。

默认值:true

hbase.rest.port

原文

The port for the HBase REST server.

译文

HBASE REST服务器的端口。

默认值:8080

hbase.rest.readonly

原文

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.

译文

定义REST服务器将在何种模式下启动。可能的值是：false：所有HTTP方法都是允许的-get/put/post/delete。True：只允许GET方法。

默认值:false

hbase.rest.threads.max

原文

The maximum number of threads of the REST server thread pool. Threads in the pool are reused to process REST requests. This controls the maximum number of requests processed concurrently. It may help to control the memory used by the REST server to avoid OOM issues. If the thread pool is full, incoming requests will be queued up and wait for some free threads.

译文

REST服务器线程池的最大线程数。池中的线程被重用来处理REST请求。这控制并发处理的请求的最大数量。它可能有助于控制REST服务器使用的内存，以避免OOM问题。如果线程池已满，则传入请求将排队等待一些空闲线程。

默认值:100

hbase.rest.threads.min

原文

The minimum number of threads of the REST server thread pool. The thread pool always has at least these number of threads so the REST server is ready to serve incoming requests.

译文

REST服务器线程池的最小线程数。线程池总是至少有这些线程数，所以REST服务器已经准备好为传入的请求提供服务了。

默认值:2

hbase.rest.support.proxyuser

原文

Enables running the REST server to support proxy-user mode.

译文

允许运行REST服务器以支持代理-用户模式。

默认值:false

hbase.defaults.for.version.skip

原文

Set to true to skip the ‘hbase.defaults.for.version’ check. Setting this to true can be useful in contexts other than the other side of a maven generation; i.e. running in an IDE. You’ll want to set this boolean to true to avoid seeing the RuntimeException complaint: “hbase-default.xml file seems to be for and old version of HBase (${hbase.version}), this version is X.X.X-SNAPSHOT”

译文

设置为true，跳过“hbase.defaults.for.version”检查。将其设置为true在Maven生成的另一端以外的上下文中很有用，即在IDE中运行。您需要将此布尔值设置为true，以避免看到RuntimeException抱怨：“HBASE-default.xml文件似乎是HBASE的旧版本(${hbase.version})，此版本为X.X.X-快照”。

默认值:false

hbase.table.lock.enable

原文

Set to true to enable locking the table in zookeeper for schema change operations. Table locking from master prevents concurrent schema modifications to corrupt table state.

译文

将其设置为true，以便为模式更改操作在ZooAdministrator中锁定表。从主表锁定防止并发架构修改到损坏的表状态。

默认值:true

hbase.table.max.rowsize

原文

Maximum size of single row in bytes (default is 1 Gb) for Get’ting or Scan’ning without in-row scan flag set. If row size exceeds this limit RowTooBigException is thrown to client.

译文

以字节为单位的最大行大小(默认为1GB)，用于在不设置行内扫描标志的情况下获取或扫描。如果行大小超过此限制，将向客户端抛出RowTooBigException。

默认值:1073741824

hbase.thrift.minWorkerThreads

原文

The “core size” of the thread pool. New threads are created on every connection until this many threads are created.

译文

线程池的“核心大小”。在每个连接上都会创建新线程，直到创建了这么多线程为止。

默认值:16

hbase.thrift.maxWorkerThreads

原文

The maximum size of the thread pool. When the pending request queue overflows, new threads are created until their number reaches this number. After that, the server starts dropping connections.

译文

线程池的最大大小。当挂起的请求队列溢出时，将创建新线程，直到它们的数目达到此数字为止。之后，服务器开始删除连接。

默认值:1000

hbase.thrift.maxQueuedRequests

原文

The maximum number of pending Thrift connections waiting in the queue. If there are no idle threads in the pool, the server queues requests. Only when the queue overflows, new threads are added, up to hbase.thrift.maxQueuedRequests threads.

译文

队列中等待的挂起连接的最大数量。如果池中没有空闲线程，服务器将对请求进行队列。只有当队列溢出时，才会添加新线程，直到hbase.thrift.maxQueuedRequest线程。

默认值:1000

hbase.regionserver.thrift.framed

原文

Use Thrift TFramedTransport on the server side. This is the recommended transport for thrift servers and requires a similar setting on the client side. Changing this to false will select the default transport, vulnerable to DoS when malformed requests are issued due to THRIFT-601.

译文

在服务器端使用TFramedTransfer。这是建议用于节约服务器的传输，并且需要在客户端设置类似的设置。将此更改为false将选择默认传输，当由于节省-601而发出格式错误的请求时，很容易出现DoS。

默认值:false

hbase.regionserver.thrift.framed.max_frame_size_in_mb

原文

Default frame size when using framed transport, in MB

译文

使用帧传输时的默认帧大小(以MB为单位)

默认值:2

hbase.regionserver.thrift.compact

原文

Use Thrift TCompactProtocol binary serialization protocol.

译文

使用TCompactProtocol二进制序列化协议。

默认值:false

hbase.rootdir.perms

原文

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 permissions if it does not match.

译文

安全(Kerberos)设置中根数据子目录的FS权限。当主服务器启动时，它使用此权限创建rootdir，如果不匹配，则设置该权限。

默认值:700

hbase.wal.dir.perms

原文

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 permissions if it does not match.

译文

安全(Kerberos)设置中根Wal目录的FS权限。当主服务器启动时，它将使用此权限创建Wal dir，如果不匹配，则设置该权限。

默认值:700

hbase.data.umask.enable

原文

Enable, if true, that file permissions should be assigned to the files written by the regionserver

译文

如果为真，则应将该文件权限分配给由分区服务器编写的文件。

默认值:false

hbase.data.umask

原文

File permissions that should be used to write data files when hbase.data.umask.enable is true

译文

当hbase.data.umask.Enable为真时应用于写入数据文件的文件权限

默认值:000

hbase.snapshot.enabled

原文

Set to true to allow snapshots to be taken / restored / cloned.

译文

设置为true允许获取/恢复/克隆快照。

默认值:true

hbase.snapshot.restore.take.failsafe.snapshot

原文

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

译文

设置为true，以在还原操作之前拍摄快照。在发生故障时，将使用所拍摄的快照来恢复以前的状态。在还原操作结束时，此快照将被删除。

默认值:true

hbase.snapshot.restore.failsafe.name

原文

Name of the failsafe snapshot taken by the restore operation. You can use the {snapshot.name}, {table.name} and {restore.timestamp} variables to create a name based on what you are restoring.

译文

还原操作获取的故障安全快照的名称。您可以使用{snshot.name}、{table.name}和{RESTore.timeSTAMP}变量根据正在还原的内容创建名称。

默认值:hbase-failsafe-{snapshot.name}-{restore.timestamp}

hbase.snapshot.working.dir

原文

Location where the snapshotting process will occur. The location of the completed snapshots will not change, but the temporary directory where the snapshot process occurs will be set to this location. This can be a separate filesystem than the root directory, for performance increase purposes. See HBASE-21098 for more information

译文

将发生快照处理的位置。完成快照的位置不会更改，但是快照进程发生的临时目录将设置为此位置。为了提高性能，这可以是一个独立的文件系统而不是根目录。有关更多信息，请参见hbase-21098。

默认值:none

hbase.server.compactchecker.interval.multiplier

原文

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 if region didn’t receive a lot of writes for some time, or due to different compaction policies, it may be necessary to check it periodically. The interval between checks is hbase.server.compactchecker.interval.multiplier multiplied by hbase.server.thread.wakefrequency.

译文

决定我们每隔多长时间扫描一次以确定是否需要压缩的数字。通常情况下，压缩是在一些事件(例如memstore刷新)之后完成的，但是如果Region在一段时间内没有收到大量的写操作，或者由于不同的压缩策略，可能需要定期检查它。检查之间的间隔是hbase.server.compactchecker.interval.multiplier乘以hbase.server.线程。

默认值:1000

hbase.lease.recovery.timeout

原文

How long we wait on dfs lease recovery in total before giving up.

译文

在放弃之前，我们需要等待多久才能收回DFS租约。

默认值:900000

hbase.lease.recovery.dfs.timeout

原文

How long between dfs recover lease invocations. Should be larger than the sum of the time it takes for the namenode to issue a block recovery command as part of datanode; dfs.heartbeat.interval and the time it takes for the primary datanode, performing block recovery to timeout on a dead datanode; usually dfs.client.socket-timeout. See the end of HBASE-8389 for more.

译文

DFS恢复租约调用之间的时间。应该大于NameNode作为DataNode的一部分发出块恢复命令所需的时间之和；dfs.Hearbeat.Interval以及主DataNode执行块恢复到死DataNode超时所需的时间；通常是dfs.client.套接字超时。有关更多信息，请参阅HBASE-8389的末尾。

默认值:64000

hbase.column.max.version

原文

New column family descriptors will use this value as the default number of versions to keep.

译文

新的列族描述符将使用此值作为要保留的默认版本数。

默认值:1

dfs.client.read.shortcircuit

原文

If set to true, this configuration parameter enables short-circuit local reads.

译文

如果设置为真，则此配置参数启用短路本地读取.

默认值:none

dfs.domain.socket.path

原文

This is a path to a UNIX domain socket that will be used for communication between the DataNode and local HDFS clients, if dfs.client.read.shortcircuit is set to true. If the string “_PORT” is present in this path, it will be replaced by the TCP port of the DataNode. Be careful about permissions for the directory that hosts the shared domain socket; dfsclient will complain if open to other users than the HBase user.

译文

这是一个通向UNIX域套接字的路径，如果dfs.client.read.短路设置为true，该套接字将用于DataNode和本地HDFS客户端之间的通信。如果该路径中存在字符串“_port”，则它将被DataNode的TCP端口替换。请注意托管共享域套接字的目录的权限；如果向HBASE用户以外的其他用户打开dfsclient，dfsclient会发出投诉。

默认值:none

hbase.dfs.client.read.shortcircuit.buffer.size

原文

If the DFSClient configuration dfs.client.read.shortcircuit.buffer.size is unset, we will use what is configured here as the short circuit read default direct byte buffer size. DFSClient native default is 1MB; HBase keeps its HDFS files open so number of file blocks * 1MB soon starts to add up and threaten OOME because of a shortage of direct memory. So, we set it down from the default. Make it > the default hbase block size set in the HColumnDescriptor which is usually 64k.

译文

如果DFSClient配置dfs.client.read.短路.Buffer.size未设置，我们将使用这里配置的短路读取默认直接字节缓冲区大小。DFSClient本机默认值为1MB；HBASE将其HDFS文件保持为打开状态，因此，由于缺乏直接内存，文件块的数量很快就会增加和威胁OOME。所以，我们把它从默认设置下来。在HColumnDescriptor中设置的默认HBASE块大小(通常为64K)。

默认值:131072

hbase.regionserver.checksum.verify

原文

If set to true (the default), HBase verifies the checksums for hfile blocks. HBase writes checksums inline with the data when it writes out hfiles. HDFS (as of this writing) writes checksums to a separate file than the data file necessitating extra seeks. Setting this flag saves some on i/o. Checksum verification by HDFS will be internally disabled on hfile streams when this flag is set. If the hbase-checksum verification fails, we will switch back to using HDFS checksums (so do not disable HDFS checksums! 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.

译文

如果设置为true(默认值)，HBASE将验证hfile块的校验和。HBASE在写入hfile时会将校验和与数据一起写入。HDFS(撰写本文时)将校验和写入一个单独的文件，而不是数据文件，这需要额外的查找。设置此标志可以保存一些I/O。当设置此标志时，HDFS的校验和验证将在hfile流上被内部禁用。如果HBASE-校验和验证失败，我们将切换到使用HDFS校验和(所以不要禁用HDFS校验和！此外，此功能仅适用于hfiles，而不适用于WALS)。如果此参数设置为false，则HBASE将不会验证任何校验和，而是依赖于在HDFS客户端中进行的校验和验证。

默认值:true

hbase.hstore.bytes.per.checksum

原文

Number of bytes in a newly created checksum chunk for HBase-level checksums in hfile blocks.

译文

在hfile块中为HBASE级别校验和新创建的校验和块中的字节数。

默认值:16384

hbase.hstore.checksum.algorithm

原文

Name of an algorithm that is used to compute checksums. Possible values are NULL, CRC32, CRC32C.

译文

用于计算校验和的算法的名称。可能的值为NULL、CRC 32、CRC32C。

默认值:CRC32C

hbase.client.scanner.max.result.size

原文

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.

译文

调用扫描仪的下一个方法时返回的最大字节数。请注意，当单个行大于此限制时，仍将完全返回行。默认值是2MB，这对1GE网络是很好的。随着更快和/或高延迟网络，这个值应该增加。

默认值:2097152

hbase.server.scanner.max.result.size

原文

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.

译文

调用扫描仪的下一个方法时返回的最大字节数。请注意，当单个行大于此限制时，仍将完全返回行。默认值为100 MB。这是一个安全设置，以保护服务器不受OOM情况的影响。

默认值:104857600

hbase.status.published

原文

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 information to the client application, to let them cut the connection immediately instead of waiting for a timeout.

译文

此设置激活主服务器对区域服务器状态的发布。当区域服务器死亡并开始恢复时，主服务器将将此信息推送到客户端应用程序，让它们立即切断连接，而不是等待超时。

默认值:false

hbase.status.publisher.class

原文

Implementation of the status publication with a multicast message.

译文

使用多播消息实现状态发布。

默认值:org.apache.hadoop.hbase.master.ClusterStatusPublisher$MulticastPublisher

hbase.status.listener.class

原文

Implementation of the status listener with a multicast message.

译文

使用多播消息实现状态侦听器。

默认值:org.apache.hadoop.hbase.client.ClusterStatusListener$MulticastListener

hbase.status.multicast.address.ip

原文

Multicast address to use for the status publication by multicast.

译文

要用于多播状态发布的多播地址。

默认值:226.1.1.3

hbase.status.multicast.address.port

原文

Multicast port to use for the status publication by multicast.

译文

用于多播状态发布的多播端口。

默认值:16100

hbase.dynamic.jars.dir

原文

The directory from which the custom filter JARs can be loaded dynamically by the region server without the need to restart. However, an already loaded filter/co-processor class would not be un-loaded. See HBASE-1936 for more details. Does not apply to coprocessors.

译文

可以由区域服务器动态加载自定义筛选器JAR的目录，而无需重新启动。但是，已经加载的过滤器/协处理器类不会被卸载。详情见HBASE-1936。不适用于协处理器。

默认值:${hbase.rootdir}/lib

hbase.security.authentication

原文

Controls whether or not secure authentication is enabled for HBase. Possible values are ‘simple’ (no authentication), and ‘kerberos’.

译文

控制是否为HBASE启用安全身份验证。可能的值是“Simple”(没有身份验证)和“Kerberos”。

默认值:simple

hbase.rest.filter.classes

原文

Servlet filters for REST service.

译文

REST服务的servlet过滤器。

默认值:org.apache.hadoop.hbase.rest.filter.GzipFilter

hbase.master.loadbalancer.class

原文

Class used to execute the regions balancing when the period occurs. See the class comment for more on how it works

译文

类用于在发生期间时执行区域平衡。有关其工作方式的更多信息，请参见类注释。

默认值:org.apache.hadoop.hbase.master.balancer.StochasticLoadBalancer

hbase.master.loadbalance.bytable

原文

Factor Table name when the balancer runs. Default: false.

译文

当平衡器运行时，元素表名称。默认值：假。

默认值:false

hbase.master.normalizer.class

原文

Class used to execute the region normalization when the period occurs. See the class comment for more on how it works

译文

类用于在发生期间时执行区域正常化。有关其工作方式的更多信息，请参见类注释。

默认值:org.apache.hadoop.hbase.master.normalizer.SimpleRegionNormalizer

hbase.rest.csrf.enabled

原文

Set to true to enable protection against cross-site request forgery (CSRF)

译文

设置为true，以防止跨站点请求伪造(Csrf)。

默认值:false

hbase.security.exec.permission.checks

原文

If this setting is enabled and ACL based access control is active (the AccessController coprocessor is installed either as a system coprocessor or on a table as a table coprocessor) then you must grant all relevant users EXEC privilege if they require the ability to execute coprocessor endpoint calls. EXEC privilege, like any other permission, can be granted globally to a user, or to a user on a per table or per namespace basis. For more information on coprocessor endpoints, see the coprocessor section of the HBase online manual. For more information on granting or revoking permissions using the AccessController, see the security section of the HBase online manual.

译文

如果启用了此设置，并且基于ACL的访问控制处于活动状态(AccessController协处理器作为系统协处理器或表协处理器安装在表上)，则如果所有相关用户都需要执行协处理器端点调用，则必须授予他们exec特权。与任何其他权限一样，可以全局地将exec权限授予用户，或在每个表或每个命名空间的基础上授予用户。有关协处理器端点的详细信息，请参阅HBASE联机手册中的协处理器部分。有关使用AccessController授予或撤销权限的详细信息，请参阅HBASE联机手册的安全部分。

默认值:false

hbase.procedure.regionserver.classes

原文

A comma-separated list of org.apache.hadoop.hbase.procedure.RegionServerProcedureManager procedure managers that are loaded 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 barriered procedure. After implementing your own RegionServerProcedureManager, just put it in HBase’s classpath and add the fully qualified class name here.

译文

默认情况下加载在Active HRegionServer进程上的以逗号分隔的org.apache.hadoop.hbase.procedure.RegionServerProcedureManager过程管理器列表。Active HRegionServer流程将调用生命周期方法(init/start/top)来执行特定的全局阻塞过程。在实现自己的RegionServerProcdureManager之后，只需将其放入HBASE的类路径中，并在这里添加完全限定的类名即可。

默认值:none

hbase.procedure.master.classes

原文

A comma-separated list of org.apache.hadoop.hbase.procedure.MasterProcedureManager procedure managers that are loaded by default on the active HMaster process. A procedure is identified by its signature and users can use the signature and an instant name to trigger an execution of a globally barriered procedure. After implementing your own MasterProcedureManager, just put it in HBase’s classpath and add the fully qualified class name here.

译文

默认情况下在Active HMaster进程上加载的以逗号分隔的org.apache.hadoop.hbase.procedure.MasterProcedureManager过程管理器列表。过程由其签名标识，用户可以使用签名和即时名称来触发执行全局阻塞的过程。在实现您自己的MasterProcedreManager之后，只需将其放入HBASE的类路径中，并在这里添加完全限定的类名。

默认值:none

hbase.coordinated.state.manager.class

原文

Fully qualified name of class implementing coordinated state manager.

译文

实施协调状态管理器的类的完全限定名称。

默认值:org.apache.hadoop.hbase.coordination.ZkCoordinatedStateManager

hbase.regionserver.storefile.refresh.period

原文

The period (in milliseconds) for refreshing the store files for the secondary regions. 0 means this feature is disabled. Secondary regions sees new files (from flushes and compactions) from primary once the secondary region refreshes the list of files in the region (there is no notification mechanism). But too frequent refreshes might cause extra 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 larger value is also recommended with this setting.

译文

刷新次要区域存储文件的时间段(毫秒)。0表示此功能被禁用。当辅助区域刷新区域中的文件列表(没有通知机制)后，辅助区域会看到主区域中的新文件(来自刷新和压缩)。但是频繁的复习可能会带来额外的NameNode压力。如果文件刷新时间不能超过HFile TTL(hbase.master.hfilecleaner.ttl)，则请求将被拒绝。使用此设置还建议将HFile TTL配置为更大的值。

默认值:0

hbase.region.replica.replication.enabled

原文

Whether asynchronous WAL replication to the secondary region replicas is enabled or not. If this is enabled, a replication peer named “region_replica_replication” will be created which will tail the logs and replicate the mutations to region replicas for tables that have region replication > 1. If this is enabled once, disabling this replication also requires disabling the replication peer using shell or Admin java class. Replication to secondary region replicas works over standard inter-cluster replication.

译文

是否启用到辅助区域副本的异步Wal复制。如果启用了该功能，将创建一个名为“RegionReplica_Replication”的复制对等点，它将跟踪日志并将突变复制复制到区域副本中，对于区域复制>1的表。如果启用一次，则禁用此复制还需要禁用使用shell或Admin java类的复制对等点。复制到次要区域副本比标准的群集间复制更有效。

默认值:false

hbase.http.filter.initializers

原文

A comma separated list of class names. Each class in the list must extend org.apache.hadoop.hbase.http.FilterInitializer. The corresponding Filter will be initialized. Then, the Filter will be applied to all user facing jsp and servlet web pages. The ordering of the list defines the ordering of the filters. The default StaticUserWebFilter add a user principal as defined by the hbase.http.staticuser.user property.

译文

以逗号分隔的类名列表。列表中的每个类都必须扩展org.apache.hadoop.hbase.http.FilterInitializer.相应的过滤器将被初始化。然后，过滤器将应用于面向jsp和servlet网页的所有用户。列表的排序定义了过滤器的排序。默认的StaticUserWebFilter添加一个由hbase.http.staticuser.user属性定义的用户主体。

默认值:org.apache.hadoop.hbase.http.lib.StaticUserWebFilter

hbase.security.visibility.mutations.checkauths

原文

This property if enabled, will check whether the labels in the visibility expression are associated with the user issuing the mutation

译文

如果启用此属性，将检查可见性表达式中的标签是否与发出突变的用户相关联。

默认值:false

hbase.http.max.threads

原文

The maximum number of threads that the HTTP Server will create in its ThreadPool.

译文

HTTPServer将在其ThreadPool中创建的最大线程数。

默认值:16

hbase.replication.rpc.codec

原文

The codec that is to be used when replication is enabled so that the tags are also replicated. This is used along with HFileV3 which supports tags in them. If tags are not used or if the hfile version used is HFileV2 then KeyValueCodec can be used as the replication codec. Note that using KeyValueCodecWithTags for replication when there are no tags causes no harm.

译文

在启用复制时使用的编解码器，以便也复制标记。这与HFileV 3一起使用，HFileV 3支持它们中的标记。如果没有使用标记，或者使用的hfile版本是HFileV 2，那么KeyValueCodec可以用作复制编解码器。注意，在没有标签的情况下，使用KeyValueCodecWithTGS进行复制不会造成任何伤害。

默认值:org.apache.hadoop.hbase.codec.KeyValueCodecWithTags

hbase.replication.source.maxthreads

原文

The maximum number of threads any replication source will use for shipping edits to the sinks in parallel. This also limits the number of chunks each replication batch is broken into. Larger values can improve the replication throughput between the master and slave clusters. The default of 10 will rarely need to be changed.

译文

任何复制源用于并行地将编辑传送到接收器的最大线程数。这也限制了每个复制批次被分解成块的数量。较大的值可以提高主群集和从群集之间的复制吞吐量。默认的10将很少需要更改。

默认值:10

hbase.http.staticuser.user

原文

The user name to filter as, on static web filters while rendering content. An example use is the HDFS web UI (user to be used for browsing files).

译文

在呈现内容时，在静态web筛选时，要筛选的用户名。一个例子是HDFSWebUI(用于浏览文件的用户)。

默认值:dr.stack

hbase.regionserver.handler.abort.on.error.percent

原文

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.

译文

区域服务器RPC线程的百分比未能中止RS。-1禁用中止；0如果单个处理程序已死亡，则为0；0.x仅在处理程序已死亡的百分比时中止；1仅在所有处理程序都已死亡时中止。

默认值:0.5

hbase.mob.file.cache.size

原文

Number of opened file handlers to cache. A larger value will benefit reads by providing more file handlers per mob file 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.

译文

要缓存的已打开文件处理程序的数目。通过为每个暴徒文件缓存提供更多的文件处理程序，一个更大的值将有利于读取，并将减少频繁的文件打开和关闭。但是，如果设置得太高，可能会导致“打开的文件处理程序太多”–默认值为1000。

默认值:1000

hbase.mob.cache.evict.period

原文

The amount of time in seconds before the mob cache evicts cached mob files. The default value is 3600 seconds.

译文

暴徒缓存驱逐缓存的暴徒文件的时间(以秒为单位)。默认值为3600秒。

默认值:3600

hbase.mob.cache.evict.remain.ratio

原文

The ratio (between 0.0 and 1.0) of files that remains cached after an eviction is triggered when the number of cached mob files exceeds the hbase.mob.file.cache.size. The default value is 0.5f.

译文

当缓存的暴民文件的数量超过hbase.mob.file.cache.size时触发的文件的比率(0.0到1.0之间)。默认值为0.5F。

默认值:0.5f

hbase.master.mob.cleaner.period

原文

The period that MobFileCleanerChore runs. The unit is second. The default value is one day. The MOB file name uses only the date part of the file creation time in it. We use this time for deciding TTL expiry of the files. So the removal of TTL expired files might be delayed. The max delay might be 24 hrs.

译文

MobFileCleanerChore运行的时间段。部队排在第二位。默认值是一天。暴徒文件名仅使用其中文件创建时间的日期部分。我们用这个时间来决定文件的TTL过期。因此，TTL过期文件的删除可能会延迟。最大延迟可能是24小时。

默认值:86400

hbase.mob.major.compaction.region.batch.size

原文

The max number of a MOB table regions that is allowed in a batch of the mob compaction. By setting this number to a custom value, users can control the overall effect of a major compaction of a large MOB-enabled table. Default is 0 - means no limit - all regions of a MOB table will be compacted at once

译文

在一批暴徒压缩中允许的暴徒表区域的最大数目。通过将此数字设置为自定义值，用户可以控制大型启用暴徒表的主要压缩的总体效果。默认值为0-意味着没有限制-暴民表的所有区域将一次压缩。

默认值:0

hbase.mob.compaction.chore.period

原文

The period that MobCompactionChore runs. The unit is second. The default value is one week.

译文

MobCompactionChore运行的时间段。部队排在第二位。默认值是一周。

默认值:604800

hbase.snapshot.master.timeout.millis

原文

Timeout for master for the snapshot procedure execution.

译文

快照过程执行的主程序超时。

默认值:300000

hbase.snapshot.region.timeout

原文

Timeout for regionservers to keep threads in snapshot request pool waiting.

译文

区域服务器超时，以使快照请求池中的线程等待。

默认值:300000

hbase.rpc.rows.warning.threshold

原文

Number of rows in a batch operation above which a warning will be logged.

译文

将记录警告的批处理操作中的行数。

默认值:5000

hbase.master.wait.on.service.seconds

原文

Default is 5 minutes. Make it 30 seconds for tests. See HBASE-19794 for some context.

译文

默认为5分钟。30秒做测试。有关某些上下文，请参见HBASE-19794。

默认值:30

hbase.master.cleaner.snapshot.interval

原文

Snapshot Cleanup chore interval in milliseconds. The cleanup thread keeps running at this interval to find all snapshots that are expired based on TTL and delete them.

译文

快照清理工作间隔以毫秒为单位。清理线程在此间隔内继续运行，以根据TTL查找过期的所有快照并删除它们。

默认值:1800000

hbase.master.snapshot.ttl

原文

Default Snapshot TTL to be considered when the user does not specify TTL while creating snapshot. Default value 0 indicates FOREVERE - snapshot should not be automatically deleted until it is manually deleted

译文

当用户在创建快照时不指定TTL时，将考虑默认快照TTL。默认值0指示在手动删除之前不应自动删除Forevere-快照。

默认值:0

hbase.master.regions.recovery.check.interval

原文

Regions Recovery Chore interval in milliseconds. This chore keeps running at this interval to find all regions with configurable max store file ref count and reopens them.

译文

区域恢复工作间隔以毫秒为单位。此杂务在此间隔内继续运行，以找到具有可配置的最大存储文件ref计数的所有区域，并重新打开它们。

默认值:1200000

hbase.regions.recovery.store.file.ref.count

原文

Very large number of ref count on a compacted store file indicates that it is a ref leak on that object(compacted store file). Such files can not be removed after it is invalidated via compaction. Only way to recover in such scenario is to reopen the region which can release all resources, like the refcount, leases, etc. This config represents Store files Ref Count threshold value considered for reopening regions. Any region with compacted store files ref count > this value would be eligible for reopening by master. Here, we get the max refCount among all refCounts on all compacted away store files that belong to a particular region. Default value -1 indicates this feature is turned off. Only positive integer value should be provided to enable this feature.

译文

压缩存储文件上的大量Ref计数表明它是该对象(压缩存储文件)上的Ref泄漏。这样的文件不能删除后，它是无效的，通过压缩。在这种情况下恢复的唯一方法是重新打开可以释放所有资源的区域，如recount、租约等。此配置表示对于重新打开区域所考虑的Store文件、Ref计数阈值。任何具有压缩存储文件的区域(ref count>此值)都有资格由主服务器重新打开。在这里，我们得到在所有压缩的存储文件中属于特定区域的所有Ref计数中的max Ref Count。默认值-1表示关闭了此功能。应该只提供正整数值来启用此功能。

默认值:-1

hbase.regionserver.slowlog.ringbuffer.size

原文

Default size of ringbuffer to be maintained by each RegionServer in order to store online slowlog responses. This is an in-memory ring buffer of requests that were judged to be too slow in addition to the responseTooSlow logging. The in-memory representation would be complete. For more details, please look into Doc Section: Get Slow Response Log from shell

译文

每个RegionServer为存储在线慢速日志响应而要维护的循环缓冲区的默认大小。这是一个内存中的环形缓冲区，除了responseTooSlow日志记录之外，这些请求被认为太慢了。内存表示将完成。有关更多细节，请查看DOC部分：从shell获取慢响应日志

默认值:256

hbase.regionserver.slowlog.buffer.enabled

原文

Indicates whether RegionServers have ring buffer running for storing Online Slow logs in FIFO manner with limited entries. The size of the ring buffer is indicated by config: hbase.regionserver.slowlog.ringbuffer.size The default value is false, turn this on and get latest slowlog responses with complete data.

译文

指示RegionServers是否具有用于以FIFO方式以有限项的方式存储联机慢速日志的环形缓冲区。循环缓冲区的大小由config：hbase.Regiserver.cellog.ringBuffer.size(默认值为false)指示，打开该值并获得包含完整数据的最新慢日志响应。

默认值:false

hbase.regionserver.slowlog.systable.enabled

原文

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 addition to in-memory ring buffer at each RegionServer). The records are stored in increasing order 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”

译文

只有在启用hbase.Regierserver.cellog.Buffer.Enable时才应该启用。如果启用(True)，所有慢/大型RPC日志都将持久化到系统表HBASE：low log(除了每个RegionServer上的内存环缓冲区外)。这些记录是按时间顺序存储的。运算符可以使用ColumnValueFilter的各种组合扫描表。在doc部分中提供了更多详细信息：“从系统表HBASE获得慢/大响应日志：缓慢日志”。

默认值:false

hbase.master.metafixer.max.merge.count

原文

Maximum regions to merge at a time when we fix overlaps noted in CJ consistency report, but avoid merging 100 regions in one go!

译文

当我们修复CJ一致性报告中提到的重叠时，最大的合并区域，但避免一次合并100个区域！

默认值:64

hbase.rpc.rows.size.threshold.reject

原文

If value is true, RegionServer will abort batch requests of Put/Delete with number of rows in a batch operation exceeding threshold defined by value of config: hbase.rpc.rows.warning.threshold. The default value is false and hence, by default, only warning will be logged. This config should be turned on to prevent RegionServer from serving very large batch size of rows and this way we can improve CPU usages by discarding too large batch request.

译文

如果值为true，RegionServer将中止PUT/Delete的批处理请求，批处理操作中的行数将超过config：hbase.rpc.rows.warning.阈值定义的阈值。默认值为false，因此，在默认情况下，只记录警告。应该打开此配置，以防止RegionServer提供非常大的批处理大小的行，这样我们就可以通过丢弃太大的批处理请求来改进CPU使用。

默认值:false

hbase.namedqueue.provider.classes

原文

Default values for NamedQueueService implementors. This comma separated full class names represent all implementors of NamedQueueService that we would like to be invoked by LogEvent handler service. One example of NamedQueue service is SlowLogQueueService which is 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”

译文

NamedQueueService实现者的默认值。这个逗号分隔的完整类名表示我们希望由LogEvent处理程序服务调用的NamedQueueService的所有实现者。NamedQueue服务的一个例子是SlowLogQueueService，它用于在每个RegionServer的环缓冲区中存储慢速/大型RPC日志。NamedQueueService的所有实现者都应该在包中找到：“org.apache.hadoop.hbase.nameQuees.impl”

默认值:org.apache.hadoop.hbase.namequeues.impl.SlowLogQueueService,org.apache.hadoop.hbase.namequeues.impl.BalancerDecisionQueueService

hbase.master.balancer.decision.buffer.enabled

原文

Indicates whether active HMaster has ring buffer running for storing balancer decisions in FIFO manner with limited entries. The size of the ring buffer is indicated by config: hbase.master.balancer.decision.queue.size

译文

指示Active HMaster是否有用于以FIFO方式以有限项存储平衡器判决的环缓冲区。环形缓冲区的大小由config：hbase.master.balancer.Decision.Quee.size指示。

默认值:false

特殊参数

hbase.client.localityCheck.threadPoolSize

该参数官方没有给出解释

含义(来源网络)

做localityCheck的线程池大小，默认是2；

默认值2

hbase.rest-csrf.browser-useragents-regex

原文

A comma-separated list of regular expressions used to match against an HTTP request’s User-Agent header when protection against cross-site request forgery (CSRF) is enabled for REST server by setting hbase.rest.csrf.enabled to true. If the incoming User-Agent matches any of these regular expressions, then the request is considered to be sent by a browser, and therefore CSRF prevention is enforced. If the request’s User-Agent does not match any of these regular expressions, then the request is considered to be sent by something other than a browser, such as scripted automation. In this case, CSRF is not a potential attack vector, so the prevention is not enforced. This helps achieve backwards-compatibility with existing automation that has not been updated to send the CSRF prevention header.

译文

通过将hbase.rest.csrf.enabled设置为true，当REST服务器启用防止跨站请求伪造(CSRF)保护时，用于匹配HTTP请求的User-Agent报头，以逗号分隔的正则表达式列表。如果传入的User-Agent匹配这些正则表达式中的任何一个，则认为该请求是由浏览器发送的，因此执行CSRF预防。如果请求的User-Agent不匹配这些正则表达式中的任何一个，则认为该请求是由浏览器以外的东西发送的，例如脚本自动化。在这种情况下，CSRF不是潜在的攻击载体，因此不执行预防。这有助于实现与现有自动化的向后兼容性，这些自动化还没有更新到发送CSRF预防头。

默认值Mozilla.,Opera.(格式不太标准,官方同样)