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

原文

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}

原文

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

原文

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

原文

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

原文

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

原文

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

译文

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

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

原文

The port the HBase Master should bind to.

译文

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

默认值:16000

原文

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

原文

The bind address for the HBase Master web UI

译文

HBASE主web UI的绑定地址

默认值:0.0.0.0

原文

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

原文

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

原文

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

原文

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

原文

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

原文

The port the HBase RegionServer binds to.

译文

HBASE RegionServer绑定到的端口。

默认值:16020

原文

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

原文

The address for the HBase RegionServer web UI

译文

HBASE RegionServerWebUI的地址

默认值:0.0.0.0

原文

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

原文

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

原文

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

原文

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

原文

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

原文

Interval between messages from the RegionServer to Master in milliseconds.

译文

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

默认值:3000

原文

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

译文

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

默认值:3600000

原文

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

原文

The WAL file reader implementation.

译文

Wal文件读取器实现。

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

原文

The WAL file writer implementation.

译文

Wal文件编写器实现。

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

原文

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

原文

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

原文

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

原文

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

原文

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

译文

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

默认值:default

原文

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

原文

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

原文

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 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

原文

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

原文

Root ZNode for access control lists.

译文

访问控制列表的根Zode。

默认值:acl

原文

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

译文

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

默认值:default

原文

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

原文

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

译文

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

默认值:2888

原文

Port used by ZooKeeper for leader election. See

译文

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

默认值:3888

原文

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

译文

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

默认值:10

原文

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

原文

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

译文

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

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

原文

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

译文

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

默认值:2181

原文

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

原文

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

原文

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

原文

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

原文

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

原文

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

译文

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

默认值:100

原文

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

译文

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

默认值:2

原文

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

原文

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

原文

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

原文

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

原文

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

原文

Client scanner lease period in milliseconds.

译文

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

默认值:60000

原文

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

原文

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

译文

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

默认值:false

原文

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