Last active
January 10, 2017 11:11
-
-
Save larsgeorge/3f7daee9f96200d2f229 to your computer and use it in GitHub Desktop.
HBase Configuration Differences (based on the hbase-default.xml file in each release)
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| /projects/private/hadoop-config-differ [git:master]$ sh target/bin/run-differ /projects/opensource/hbase/hbase-r1130916/src/main/resources/hbase-default.xml r1130916 /projects/opensource/hbase/hbase-0.92-rw/src/main/resources/hbase-default.xml 0.92 /projects/opensource/hbase/hbase-0.94-rw/src/main/resources/hbase-default.xml 0.94 /projects/opensource/hbase/hbase-0.96-rw/hbase-common/src/main/resources/hbase-default.xml 0.96 /projects/opensource/hbase/hbase-0.98-rw/hbase-common/src/main/resources/hbase-default.xml 0.98 /projects/opensource/hbase/hbase-trunk-rw-git/hbase-common/src/main/resources/hbase-default.xml 0.99 | |
| ========================================================= | |
| Start | |
| ========================================================= | |
| Checking differences across versions... | |
| Added or renamed keys in 0.92: | |
| added: Property{key='dfs.support.append', value='true', description='Does HDFS allow appends to files? This is an hdfs config. set in here so the hdfs client will do append support. You must ensure that this config. is true serverside too when running hbase (You will have to restart your cluster after setting it).', source='0.92'} | |
| added: Property{key='hadoop.policy.file', value='hbase-policy.xml', description='The policy configuration file used by RPC servers to make authorization decisions on client requests. Only used when HBase security is enabled.', source='0.92'} | |
| added: Property{key='hbase.auth.key.update.interval', value='86400000', description='The update interval for master key for authentication tokens in servers in milliseconds. Only used when HBase security is enabled.', source='0.92'} | |
| added: Property{key='hbase.auth.token.max.lifetime', value='604800000', description='The maximum lifetime in milliseconds after which an authentication token expires. Only used when HBase security is enabled.', source='0.92'} | |
| added: Property{key='hbase.bulkload.retries.number', value='0', description='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. Default: 0.', source='0.92'} | |
| added: Property{key='hbase.coprocessor.abortonerror', value='false', description='Set to true to cause the hosting server (master or regionserver) to abort if a coprocessor throws a Throwable object that is not IOException or a subclass of IOException. Setting it to true might be useful in development environments where one wants to terminate the server as soon as possible to simplify coprocessor failure analysis.', source='0.92'} | |
| added: Property{key='hbase.ipc.client.fallback-to-simple-auth-allowed', value='false', description='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. This setting is only used by the secure RPC engine.', source='0.92'} | |
| added: Property{key='hbase.offheapcache.percentage', value='0', description='The amount of off heap space to be allocated towards the experimental off heap cache. If you desire the cache to be disabled, simply set this value to 0.', source='0.92'} | |
| added: Property{key='hbase.online.schema.update.enable', value='false', description='Set true to enable online schema changes. This is an experimental feature. There are known issues modifying table schemas at the same time a region split is happening so your table needs to be quiescent or else you have to be running with splits disabled.', source='0.92'} | |
| added: Property{key='hbase.regionserver.logroll.errors.tolerated', value='2', description='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.', source='0.92'} | |
| added: Property{key='hbase.rs.cacheblocksonwrite', value='false', description='Whether an HFile block should be added to the block cache when the block is finished.', source='0.92'} | |
| added: Property{key='hbase.server.versionfile.writeattempts', value='3', description='How many time to retry attempting to write a version file before just aborting. Each attempt is seperated by the hbase.server.thread.wakefrequency milliseconds.', source='0.92'} | |
| added: Property{key='hbase.superuser', value='NULL', description='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.', source='0.92'} | |
| added: Property{key='hfile.block.index.cacheonwrite', value='false', description='This allows to put non-root multi-level index blocks into the block cache at the time the index is being written.', source='0.92'} | |
| added: Property{key='hfile.format.version', value='2', description='The HFile format version to use for new files. Set this to 1 to test backwards-compatibility. The default value of this option should be consistent with FixedFileTrailer.MAX_VERSION.', source='0.92'} | |
| added: Property{key='hfile.index.block.max.size', value='131072', description='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.', source='0.92'} | |
| added: Property{key='io.storefile.bloom.block.size', value='131072', description='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.', source='0.92'} | |
| added: Property{key='io.storefile.bloom.cacheonwrite', value='false', description='Enables cache-on-write for inline blocks of a compound Bloom filter.', source='0.92'} | |
| added: Property{key='zookeeper.znode.acl.parent', value='acl', description='Root ZNode for access control lists.', source='0.92'} | |
| Added or renamed keys in 0.94: | |
| added: Property{key='fail.fast.expired.active.master', value='false', description='If abort immediately for the expired master without trying to recover its zk session.', source='0.94'} | |
| added: Property{key='hbase.data.umask', value='000', description='File permissions that should be used to write data files when hbase.data.umask.enable is true', source='0.94'} | |
| added: Property{key='hbase.data.umask.enable', value='false', description='Enable, if true, that file permissions should be assigned to the files written by the regionserver', source='0.94'} | |
| added: Property{key='hbase.dynamic.jars.dir', value='${hbase.rootdir}/.lib', description='The directory from which the custom filter/co-processor 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.', source='0.94'} | |
| added: Property{key='hbase.lease.recovery.dfs.timeout', value='61000', description='How long between dfs recover lease invocations. Should be just larger than how long it takes the namenode to timeout trying to reach a datanode; usually dfs.socket.timeout. If HBase asked hdfs its cluster configs, we would not need this config. See the end of HBASE-8389 for more.', source='0.94'} | |
| added: Property{key='hbase.lease.recovery.timeout', value='900000', description='How long we wait on dfs lease recovery in total before giving up.', source='0.94'} | |
| added: Property{key='hbase.local.dir', value='${hbase.tmp.dir}/local/', description='Directory on the local filesystem to be used as a local storage.', source='0.94'} | |
| added: Property{key='hbase.master.hfilecleaner.plugins', value='org.apache.hadoop.hbase.master.cleaner.TimeToLiveHFileCleaner', description='A comma-separated list of HFileCleanerDelegate 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 HFileCleanerDelegate, 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 as they will be overwritten in hbase-site.xml.', source='0.94'} | |
| added: Property{key='hbase.metrics.showTableName', value='true', description='Whether to include the prefix "tbl.tablename" in per-column family metrics. If true, for each metric M, per-cf metrics will be reported for tbl.T.cf.CF.M, if false, per-cf metrics will be aggregated by column-family across tables, and reported for cf.CF.M. In both cases, the aggregated metric M across tables and cfs will be reported.', source='0.94'} | |
| added: Property{key='hbase.regionserver.checksum.verify', value='false', description='Allow hbase to do checksums rather than using hdfs checksums. This is a backwards incompatible change.', source='0.94'} | |
| added: Property{key='hbase.regionserver.optionalcacheflushinterval', value='3600000', description='Maximum amount of time an edit lives in memory before being automatically flushed. Default 1 hour. Set it to 0 to disable automatic flushing.', source='0.94'} | |
| added: Property{key='hbase.regionserver.region.split.policy', value='org.apache.hadoop.hbase.regionserver.IncreasingToUpperBoundRegionSplitPolicy', description='A split policy determines when a region should be split. The various other split policies that are available currently are ConstantSizeRegionSplitPolicy, DisabledRegionSplitPolicy, DelimitedKeyPrefixRegionSplitPolicy, KeyPrefixRegionSplitPolicy etc.', source='0.94'} | |
| added: Property{key='hbase.regionserver.separate.hlog.for.meta', value='false', description='NULL', source='0.94'} | |
| added: Property{key='hbase.rest.threads.max', value='100', description='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. The default is 100.', source='0.94'} | |
| added: Property{key='hbase.rest.threads.min', value='2', description='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. The default is 2.', source='0.94'} | |
| added: Property{key='hbase.rpc.shortoperation.timeout', value='10000', description='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.', source='0.94'} | |
| added: Property{key='hbase.rpc.timeout', value='60000', description='This is for the RPC layer to define how long HBase client applications take for a remote call to time out. It uses pings to check connections but will eventually throw a TimeoutException.', source='0.94'} | |
| added: Property{key='hbase.security.authentication', value='simple', description='Controls whether or not secure authentication is enabled for HBase. Possible values are 'simple' (no authentication), and 'kerberos'.', source='0.94'} | |
| added: Property{key='hbase.table.archive.directory', value='.archive', description='Per-table directory name under which to backup files for a table. Files are moved to the same directories as they would be under the table directory, but instead are just one level lower (under table/.archive/... rather than table/...). Currently only applies to HFiles.', source='0.94'} | |
| added: Property{key='hbase.thrift.htablepool.size.max', value='1000', description='The upper bound for the table pool used in the Thrift gateways server. Since this is per table name, we assume a single table and so with 1000 default worker threads max this is set to a matching number. For other workloads this number can be adjusted as needed.', source='0.94'} | |
| added: Property{key='hbase.thrift.maxQueuedRequests', value='1000', description='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.', source='0.94'} | |
| added: Property{key='hbase.thrift.maxWorkerThreads', value='1000', description='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.', source='0.94'} | |
| added: Property{key='hbase.thrift.minWorkerThreads', value='16', description='The "core size" of the thread pool. New threads are created on every connection until this many threads are created.', source='0.94'} | |
| added: Property{key='hbase.zookeeper.useMulti', value='false', description='Instructs HBase to make use of ZooKeeper's multi-update functionality. This allows certain ZooKeeper operations to complete more quickly and prevents some issues with rare ZooKeeper failure scenarios (see the release note of HBASE-6710 for an example). IMPORTANT: only set this to true if all ZooKeeper servers in the cluster are on version 3.4+ and will not be downgraded. ZooKeeper versions before 3.4 do not support multi-update and will not fail gracefully if multi-update is invoked (see ZOOKEEPER-1495).', source='0.94'} | |
| Removed keys in 0.94: | |
| Property{key='hbase.mapreduce.hfileoutputformat.blocksize', value='65536', description='The mapreduce HFileOutputFormat writes storefiles/hfiles. This is the minimum hfile blocksize to emit. Usually in hbase, writing hfiles, the blocksize is gotten from the table schema (HColumnDescriptor) but in the mapreduce outputformat context, we don't have access to the schema so get blocksize from Configuation. The smaller you make the blocksize, the bigger your index and the less you fetch on a random-access. Set the blocksize down if you have small cells and want faster random-access of individual cells.', source='0.92'} | |
| Added or renamed keys in 0.96: | |
| added: Property{key='hbase.client.localityCheck.threadPoolSize', value='2', description='NULL', source='0.96'} | |
| added: Property{key='hbase.client.max.perregion.tasks', value='1', description='The maximum number of concurrent connections 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.', source='0.96'} | |
| added: Property{key='hbase.client.max.perserver.tasks', value='5', description='The maximum number of concurrent tasks a single HTable instance will send to a single region server.', source='0.96'} | |
| added: Property{key='hbase.client.max.total.tasks', value='100', description='The maximum number of concurrent tasks a single HTable instance will send to the cluster.', source='0.96'} | |
| added: Property{key='hbase.client.scanner.timeout.period', value='60000', description='Client scanner lease period in milliseconds.', source='0.96'} | |
| added: Property{key='hbase.column.max.version', value='1', description='New column family descriptors will use this value as the default number of versions to keep.', source='0.96'} | |
| added: Property{key='hbase.config.read.zookeeper.config', value='false', description='Set to true to allow HBaseConfiguration to read the zoo.cfg file for ZooKeeper properties. Switching this to true is not recommended, since the functionality of reading ZK properties from a zoo.cfg file has been deprecated.', source='0.96'} | |
| added: Property{key='hbase.dfs.client.read.shortcircuit.buffer.size', value='131072', description='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.', source='0.96'} | |
| added: Property{key='hbase.hregion.majorcompaction.jitter', value='0.50', description='Jitter outer bound for major compactions. On each regionserver, we multiply the hbase.region.majorcompaction interval by some random fraction that is inside the bounds of this maximum. We then add this + or - product to when the next major compaction is to run. The idea is that major compaction does happen on every regionserver at exactly the same time. The smaller this number, the closer the compactions come together.', source='0.96'} | |
| added: Property{key='hbase.hstore.bytes.per.checksum', value='16384', description='Number of bytes in a newly created checksum chunk for HBase-level checksums in hfile blocks.', source='0.96'} | |
| added: Property{key='hbase.hstore.checksum.algorithm', value='CRC32', description='Name of an algorithm that is used to compute checksums. Possible values are NULL, CRC32, CRC32C.', source='0.96'} | |
| added: Property{key='hbase.hstore.compaction.kv.max', value='10', description='How many KeyValues to read and then write in a batch when flushing or compacting. Do less if big KeyValues and problems with OOME. Do more if wide, small rows.', source='0.96'} | |
| added: Property{key='hbase.ipc.client.tcpnodelay', value='true', description='Set no delay on rpc socket connections. See http://docs.oracle.com/javase/1.5.0/docs/api/java/net/Socket.html#getTcpNoDelay()', source='0.96'} | |
| added: Property{key='hbase.master.catalog.timeout', value='600000', description='Timeout value for the Catalog Janitor from the master to META.', source='0.96'} | |
| added: Property{key='hbase.master.loadbalancer.class', value='org.apache.hadoop.hbase.master.balancer.StochasticLoadBalancer', description='Class used to execute the regions balancing when the period occurs. See the class comment for more on how it works http://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/master/balancer/StochasticLoadBalancer.html It replaces the DefaultLoadBalancer as the default (since renamed as the SimpleLoadBalancer).', source='0.96'} | |
| added: Property{key='hbase.metrics.exposeOperationTimes', value='true', description='Whether to report metrics about time taken performing an operation on the region server. Get, Put, Delete, Increment, and Append can all have their times exposed through Hadoop metrics per CF and per region.', source='0.96'} | |
| added: Property{key='hbase.regionserver.catalog.timeout', value='600000', description='Timeout value for the Catalog Janitor from the regionserver to META.', source='0.96'} | |
| added: Property{key='hbase.rest.filter.classes', value='org.apache.hadoop.hbase.rest.filter.GzipFilter', description='Servlet filters for REST service.', source='0.96'} | |
| added: Property{key='hbase.rpc.server.engine', value='org.apache.hadoop.hbase.ipc.ProtobufRpcServerEngine', description='Implementation of org.apache.hadoop.hbase.ipc.RpcServerEngine to be used for server RPC call marshalling.', source='0.96'} | |
| added: Property{key='hbase.server.compactchecker.interval.multiplier', value='1000', description='The number that determines how often we scan to see if compaction is necessary. Normally, compactions are done after some events (such as memstore flush), but 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.', source='0.96'} | |
| added: Property{key='hbase.snapshot.enabled', value='true', description='Set to true to allow snapshots to be taken / restored / cloned.', source='0.96'} | |
| added: Property{key='hbase.snapshot.restore.failsafe.name', value='hbase-failsafe-{snapshot.name}-{restore.timestamp}', description='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.', source='0.96'} | |
| added: Property{key='hbase.snapshot.restore.take.failsafe.snapshot', value='true', description='Set to true to take a snapshot before the restore operation. The snapshot taken will be used in case of failure, to restore the previous state. At the end of the restore operation this snapshot will be deleted', source='0.96'} | |
| added: Property{key='hbase.status.listener.class', value='org.apache.hadoop.hbase.client.ClusterStatusListener$MulticastListener', description='Implementation of the status listener with a multicast message.', source='0.96'} | |
| added: Property{key='hbase.status.multicast.address.ip', value='226.1.1.3', description='Multicast address to use for the status publication by multicast.', source='0.96'} | |
| added: Property{key='hbase.status.multicast.address.port', value='60100', description='Multicast port to use for the status publication by multicast.', source='0.96'} | |
| added: Property{key='hbase.status.published', value='false', description='This setting activates the publication by the master of the status of the region server. When a region server dies and its recovery starts, the master will push this information to the client application, to let them cut the connection immediately instead of waiting for a timeout.', source='0.96'} | |
| added: Property{key='hbase.status.publisher.class', value='org.apache.hadoop.hbase.master.ClusterStatusPublisher$MulticastPublisher', description='Implementation of the status publication with a multicast message.', source='0.96'} | |
| added: Property{key='hbase.storescanner.parallel.seek.enable', value='false', description='Enables StoreFileScanner parallel-seeking in StoreScanner, a feature which can reduce response latency under special conditions.', source='0.96'} | |
| added: Property{key='hbase.storescanner.parallel.seek.threads', value='10', description='The default thread pool size if parallel-seeking feature enabled.', source='0.96'} | |
| added: Property{key='hbase.table.lock.enable', value='true', description='Set to true to enable locking the table in zookeeper for schema change operations. Table locking from master prevents concurrent schema modifications to corrupt table state.', source='0.96'} | |
| renamed: Property{key='hfile.block.bloom.cacheonwrite', value='false', description='Enables cache-on-write for inline blocks of a compound Bloom filter.', source='0.96'}, | |
| from: Property{key='io.storefile.bloom.cacheonwrite', value='false', description='Enables cache-on-write for inline blocks of a compound Bloom filter.', source='0.94'} | |
| Removed keys in 0.96: | |
| Property{key='dfs.support.append', value='true', description='Does HDFS allow appends to files? This is an hdfs config. set in here so the hdfs client will do append support. You must ensure that this config. is true serverside too when running hbase (You will have to restart your cluster after setting it).', source='0.94'} | |
| Property{key='hbase.hash.type', value='murmur', description='The hashing algorithm for use in HashFunction. Two values are supported now: murmur (MurmurHash) and jenkins (JenkinsHash). Used by bloom filters.', source='0.94'} | |
| Property{key='hbase.regionserver.class', value='org.apache.hadoop.hbase.ipc.HRegionInterface', description='The RegionServer interface to use. Used by the client opening proxy to remote region server.', source='0.94'} | |
| Property{key='hbase.regionserver.lease.period', value='60000', description='HRegion server lease period in milliseconds. Default is 60 seconds. Clients must report in within this period else they are considered dead.', source='0.94'} | |
| Property{key='hbase.regionserver.nbreservationblocks', value='4', description='The number of resevoir blocks of memory release on OOME so we can cleanup properly before server shutdown.', source='0.94'} | |
| Property{key='hbase.regionserver.separate.hlog.for.meta', value='false', description='NULL', source='0.94'} | |
| Property{key='hbase.rpc.engine', value='org.apache.hadoop.hbase.ipc.WritableRpcEngine', description='Implementation of org.apache.hadoop.hbase.ipc.RpcEngine to be used for client / server RPC call marshalling.', source='0.94'} | |
| Property{key='hbase.table.archive.directory', value='.archive', description='Per-table directory name under which to backup files for a table. Files are moved to the same directories as they would be under the table directory, but instead are just one level lower (under table/.archive/... rather than table/...). Currently only applies to HFiles.', source='0.94'} | |
| Property{key='io.storefile.bloom.cacheonwrite', value='false', description='Enables cache-on-write for inline blocks of a compound Bloom filter.', source='0.94'} | |
| Added or renamed keys in 0.98: | |
| added: Property{key='hbase.procedure.master.classes', value='NULL', description='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.', source='0.98'} | |
| added: Property{key='hbase.procedure.regionserver.classes', value='NULL', description='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.', source='0.98'} | |
| added: Property{key='hbase.rest.support.proxyuser', value='false', description='Enables running the REST server to support proxy-user mode.', source='0.98'} | |
| added: Property{key='hbase.security.exec.permission.checks', value='false', description='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.', source='0.98'} | |
| Removed keys in 0.98: | |
| Property{key='hbase.regionserver.optionallogflushinterval', value='1000', description='Sync the HLog to the HDFS after this interval if it has not accumulated enough entries to trigger a sync. Units: milliseconds.', source='0.96'} | |
| Added or renamed keys in 0.99: | |
| added: Property{key='hbase.balancer.backupMasterWeight', value='1', description='Used to control how many regions the region balancer can assign to backup Masters, compared to normal region servers. The default value 1 means a backup Master can host as many regions as a normal region server. The bigger the weight, the less the regions a backup Master will host. If the weight is less than 1, the balancer will not assign any region to any backup Master', source='0.99'} | |
| added: Property{key='hbase.bucketcache.combinedcache.enabled', value='true', description='Whether or not the bucketcache is used in league with the LRU on-heap block cache. In this mode, indices and blooms are kept in the LRU blockcache and the data blocks are kept in the bucketcache.', source='0.99'} | |
| added: Property{key='hbase.bucketcache.ioengine', value='NULL', description='Where to store the contents of the bucketcache. One of: onheap, offheap, or file. If a file, set it to file:PATH_TO_FILE. See https://hbase.apache.org/apidocs/org/apache/hadoop/hbase/io/hfile/CacheConfig.html for more information.', source='0.99'} | |
| added: Property{key='hbase.bucketcache.size', value='65536', description='The size of the buckets for the bucketcache if you only use a single size. Defaults to the default blocksize, which is 64 * 1024.', source='0.99'} | |
| added: Property{key='hbase.bucketcache.sizes', value='NULL', description='A comma-separated list of sizes for buckets for the bucketcache if you use multiple sizes. Should be a list of block sizes in order from smallest to largest. The sizes you use will depend on your data access patterns.', source='0.99'} | |
| added: Property{key='hbase.coordinated.state.manager.class', value='org.apache.hadoop.hbase.coordination.ZkCoordinatedStateManager', description='Fully qualified name of class implementing coordinated state manager.', source='0.99'} | |
| added: Property{key='hbase.display.keys', value='true', description='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.', source='0.99'} | |
| added: Property{key='hbase.hstore.compaction.max.size', value='9223372036854775807', description='A StoreFile 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.', source='0.99'} | |
| added: Property{key='hbase.hstore.compaction.min', value='3', description='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. In previous versions of HBase, the parameter hbase.hstore.compaction.min was named hbase.hstore.compactionThreshold.', source='0.99'} | |
| added: Property{key='hbase.hstore.compaction.min.size', value='134217728', description='A StoreFile 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.', source='0.99'} | |
| added: Property{key='hbase.hstore.compaction.ratio', value='1.2F', description='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.', source='0.99'} | |
| added: Property{key='hbase.hstore.compaction.ratio.offpeak', value='5.0F', description='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.', source='0.99'} | |
| added: Property{key='hbase.hstore.flusher.count', value='2', description='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.', source='0.99'} | |
| added: Property{key='hbase.hstore.time.to.purge.deletes', value='0', description='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.', source='0.99'} | |
| added: Property{key='hbase.http.filter.initializers', value='org.apache.hadoop.hbase.http.lib.StaticUserWebFilter', description='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.', source='0.99'} | |
| added: Property{key='hbase.http.max.threads', value='10', description='The maximum number of threads that the HTTP Server will create in its ThreadPool.', source='0.99'} | |
| added: Property{key='hbase.http.staticuser.user', value='dr.stack', description='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).', source='0.99'} | |
| added: Property{key='hbase.ipc.server.callqueue.handler.factor', value='0.1', description='Factor to determine the number of call queues. A value of 0 means a single queue shared between all the handlers. A value of 1 means that each handler has its own queue.', source='0.99'} | |
| added: Property{key='hbase.ipc.server.callqueue.read.ratio', value='0', description='Split the call queues into read and write queues. The specified interval (which should be between 0.0 and 1.0) will be multiplied by the number of call queues. A value of 0 indicate to not split the call queues, meaning that both read and 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.', source='0.99'} | |
| added: Property{key='hbase.ipc.server.callqueue.scan.ratio', value='0', description='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.', source='0.99'} | |
| added: Property{key='hbase.master.distributed.log.replay', value='true', description='Enable 'distributed log replay' as default engine splitting WAL files on server crash. This default is new in hbase 1.0. To fall back to the old mode 'distributed log splitter', set the value to 'false'. 'Disributed log replay' improves MTTR because it does not write intermediate files. 'DLR' required that 'hfile.format.version' be set to version 3 or higher.', source='0.99'} | |
| added: Property{key='hbase.master.infoserver.redirect', value='true', description='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.', source='0.99'} | |
| added: Property{key='hbase.offpeak.end.hour', value='-1', description='The end of off-peak hours, expressed as an integer between 0 and 23, inclusive. Set to -1 to disable off-peak.', source='0.99'} | |
| added: Property{key='hbase.offpeak.start.hour', value='-1', description='The start of off-peak hours, expressed as an integer between 0 and 23, inclusive. Set to -1 to disable off-peak.', source='0.99'} | |
| added: Property{key='hbase.region.replica.replication.enabled', value='false', description='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 mutatations 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 ReplicationAdmin java class. Replication to secondary region replicas works over standard inter-cluster replication. So replication, if disabled explicitly, also has to be enabled by setting "hbase.replication" to true for this feature to work.', source='0.99'} | |
| added: Property{key='hbase.regionserver.global.memstore.size', value='0.4', description='Maximum size of all memstores in a region server before new updates are blocked and flushes are forced. Defaults to 40% of heap. Updates are blocked and flushes are forced until size of all memstores in a region server hits hbase.regionserver.global.memstore.size.lower.limit.', source='0.99'} | |
| added: Property{key='hbase.regionserver.global.memstore.size.lower.limit', value='0.95', description='Maximum size of all memstores in a region server before flushes are forced. Defaults to 95% of hbase.regionserver.global.memstore.size. A 100% value for this value causes the minimum possible flushing to occur when updates are blocked due to memstore limiting.', source='0.99'} | |
| added: Property{key='hbase.regionserver.storefile.refresh.period', value='0', description='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.', source='0.99'} | |
| added: Property{key='hbase.regionserver.thread.compaction.throttle', value='2560', description='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', source='0.99'} | |
| added: Property{key='hbase.regionserver.thrift.compact', value='false', description='Use Thrift TCompactProtocol binary serialization protocol.', source='0.99'} | |
| added: Property{key='hbase.regionserver.thrift.framed', value='false', description='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.', source='0.99'} | |
| added: Property{key='hbase.regionserver.thrift.framed.max_frame_size_in_mb', value='2', description='Default frame size when using framed transport', source='0.99'} | |
| added: Property{key='hbase.replication.rpc.codec', value='org.apache.hadoop.hbase.codec.KeyValueCodecWithTags', description='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.', source='0.99'} | |
| added: Property{key='hbase.security.visibility.mutations.checkauths', value='false', description='This property if enabled, will check whether the labels in the visibility expression are associated with the user issuing the mutation', source='0.99'} | |
| added: Property{key='hbase.table.max.rowsize', value='1073741824', description='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.', source='0.99'} | |
| Removed keys in 0.99: | |
| Property{key='fail.fast.expired.active.master', value='false', description='If abort immediately for the expired master without trying to recover its zk session.', source='0.98'} | |
| Property{key='hbase.master.dns.interface', value='default', description='The name of the Network Interface from which a master should report its IP address.', source='0.98'} | |
| Property{key='hbase.master.dns.nameserver', value='default', description='The host name or IP address of the name server (DNS) which a master should use to determine the host name used for communication and display purposes.', source='0.98'} | |
| Property{key='hbase.master.port', value='60000', description='The port the HBase Master should bind to.', source='0.98'} | |
| Property{key='hbase.offheapcache.percentage', value='0', description='The amount of off heap space to be allocated towards the experimental off heap cache. If you desire the cache to be disabled, simply set this value to 0.', source='0.98'} | |
| Property{key='hbase.regionserver.global.memstore.lowerLimit', value='0.38', description='Maximum size of all memstores in a region server before flushes are forced. Defaults to 38% of heap. This value equal to hbase.regionserver.global.memstore.upperLimit causes the minimum possible flushing to occur when updates are blocked due to memstore limiting.', source='0.98'} | |
| Property{key='hbase.regionserver.global.memstore.upperLimit', value='0.4', description='Maximum size of all memstores in a region server before new updates are blocked and flushes are forced. Defaults to 40% of heap. Updates are blocked and flushes are forced until size of all memstores in a region server hits hbase.regionserver.global.memstore.lowerLimit.', source='0.98'} | |
| --------------------------------------------------------- | |
| Checking differences per property... | |
| Difference found for property hbase.bulkload.retries.number | |
| Property{key='hbase.bulkload.retries.number', value='0', description='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. Default: 0.', source='0.92'} | |
| Property{key='hbase.bulkload.retries.number', value='0', description='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.', source='0.96'} | |
| Difference found for property hbase.client.pause | |
| Property{key='hbase.client.pause', value='1000', description='General client pause value. Used mostly as value to wait before running a retry of a failed get, region lookup, etc.', source='r1130916'} | |
| Property{key='hbase.client.pause', value='100', description='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.', source='0.96'} | |
| Difference found for property hbase.client.retries.number | |
| Property{key='hbase.client.retries.number', value='10', description='Maximum retries. Used as maximum for all retryable operations such as fetching of the root region from root region server, getting a cell's value, starting a row update, etc. Default: 10.', source='r1130916'} | |
| Property{key='hbase.client.retries.number', value='14', description='Maximum retries. Used as maximum for all retryable operations such as fetching of the root region from root region server, getting a cell's value, starting a row update, etc. Default: 14.', source='0.94'} | |
| Property{key='hbase.client.retries.number', value='35', description='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.', source='0.96'} | |
| Difference found for property hbase.client.scanner.caching | |
| Property{key='hbase.client.scanner.caching', value='1', description='Number of rows that will be fetched when calling next on a scanner if it is not served from (local, client) memory. 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.regionserver.lease.period', source='r1130916'} | |
| Property{key='hbase.client.scanner.caching', value='100', description='Number of rows that will be fetched when calling next on a scanner if it is not served from (local, client) memory. 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', source='0.96'} | |
| Difference found for property hbase.client.write.buffer | |
| Property{key='hbase.client.write.buffer', value='2097152', description='Default size of the HTable clien 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', source='r1130916'} | |
| Property{key='hbase.client.write.buffer', value='2097152', description='Default size of the HTable client 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', source='0.96'} | |
| Difference found for property hbase.coprocessor.abortonerror | |
| Property{key='hbase.coprocessor.abortonerror', value='false', description='Set to true to cause the hosting server (master or regionserver) to abort if a coprocessor throws a Throwable object that is not IOException or a subclass of IOException. Setting it to true might be useful in development environments where one wants to terminate the server as soon as possible to simplify coprocessor failure analysis.', source='0.92'} | |
| Property{key='hbase.coprocessor.abortonerror', value='true', description='Set to true to cause the hosting server (master or regionserver) to abort if a coprocessor fails to load, fails to initialize, or throws 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.', source='0.98'} | |
| Difference found for property hbase.defaults.for.version | |
| Property{key='hbase.defaults.for.version', value='@@@VERSION@@@', description='This defaults file was compiled for version @@@VERSION@@@. This variable is used to make sure that a user doesn't have an old version of hbase-default.xml on the classpath.', source='r1130916'} | |
| Property{key='hbase.defaults.for.version', value='@@@VERSION@@@', description='This defaults file was compiled for version ${project.version}. This variable is used to make sure that a user doesn't have an old version of hbase-default.xml on the classpath.', source='0.96'} | |
| Difference found for property hbase.defaults.for.version.skip | |
| Property{key='hbase.defaults.for.version.skip', value='false', description='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 RuntimException complaint: "hbase-default.xml file seems to be for and old version of HBase (@@@VERSION@@@), this version is X.X.X-SNAPSHOT"', source='r1130916'} | |
| Property{key='hbase.defaults.for.version.skip', value='false', description='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 RuntimException complaint: "hbase-default.xml file seems to be for and old version of HBase (\${hbase.version}), this version is X.X.X-SNAPSHOT"', source='0.96'} | |
| Difference found for property hbase.dynamic.jars.dir | |
| Property{key='hbase.dynamic.jars.dir', value='${hbase.rootdir}/.lib', description='The directory from which the custom filter/co-processor 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.', source='0.94'} | |
| Property{key='hbase.dynamic.jars.dir', value='${hbase.rootdir}/lib', description='The directory from which the custom filter/co-processor 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.', source='0.96'} | |
| Difference found for property hbase.hregion.majorcompaction | |
| Property{key='hbase.hregion.majorcompaction', value='86400000', description='The time (in miliseconds) between 'major' compactions of all HStoreFiles in a region. Default: 1 day. Set to 0 to disable automated major compactions.', source='r1130916'} | |
| Property{key='hbase.hregion.majorcompaction', value='604800000', description='The time (in miliseconds) between 'major' compactions of all HStoreFiles in a region. Default: Set to 7 days. Major compactions tend to happen exactly when you need them least so enable them such that they run at off-peak for your deploy; or, since this setting is on a periodicity that is unlikely to match your loading, run the compactions via an external invocation out of a cron job or some such.', source='0.96'} | |
| Property{key='hbase.hregion.majorcompaction', value='604800000', description='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.', source='0.99'} | |
| Difference found for property hbase.hregion.majorcompaction.jitter | |
| Property{key='hbase.hregion.majorcompaction.jitter', value='0.50', description='Jitter outer bound for major compactions. On each regionserver, we multiply the hbase.region.majorcompaction interval by some random fraction that is inside the bounds of this maximum. We then add this + or - product to when the next major compaction is to run. The idea is that major compaction does happen on every regionserver at exactly the same time. The smaller this number, the closer the compactions come together.', source='0.96'} | |
| Property{key='hbase.hregion.majorcompaction.jitter', value='0.50', description='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.', source='0.99'} | |
| Difference found for property hbase.hregion.max.filesize | |
| Property{key='hbase.hregion.max.filesize', value='268435456', description='Maximum HStoreFile size. If any one of a column families' HStoreFiles has grown to exceed this value, the hosting HRegion is split in two. Default: 256M.', source='r1130916'} | |
| Property{key='hbase.hregion.max.filesize', value='1073741824', description='Maximum HStoreFile size. If any one of a column families' HStoreFiles has grown to exceed this value, the hosting HRegion is split in two. Default: 1G.', source='0.92'} | |
| Property{key='hbase.hregion.max.filesize', value='10737418240', description='Maximum HStoreFile size. If any one of a column families' HStoreFiles has grown to exceed this value, the hosting HRegion is split in two. Default: 10G.', source='0.94'} | |
| Property{key='hbase.hregion.max.filesize', value='10737418240', description='Maximum HStoreFile size. If any one of a column families' HStoreFiles has grown to exceed this value, the hosting HRegion is split in two.', source='0.96'} | |
| Property{key='hbase.hregion.max.filesize', value='10737418240', description='Maximum HFile size. If the sum of the sizes of a region's HFiles has grown to exceed this value, the region is split in two.', source='0.99'} | |
| Difference found for property hbase.hregion.memstore.block.multiplier | |
| Property{key='hbase.hregion.memstore.block.multiplier', value='2', description='Block updates if memstore has hbase.hregion.block.memstore time hbase.hregion.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.', source='r1130916'} | |
| Property{key='hbase.hregion.memstore.block.multiplier', value='2', description='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.', source='0.96'} | |
| Property{key='hbase.hregion.memstore.block.multiplier', value='4', description='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.', source='0.99'} | |
| Difference found for property hbase.hregion.memstore.flush.size | |
| Property{key='hbase.hregion.memstore.flush.size', value='67108864', description='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.', source='r1130916'} | |
| Property{key='hbase.hregion.memstore.flush.size', value='134217728', description='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.', source='0.92'} | |
| Difference found for property hbase.hstore.blockingStoreFiles | |
| Property{key='hbase.hstore.blockingStoreFiles', value='7', description='If more than this number of StoreFiles in any one Store (one StoreFile is written per flush of MemStore) then updates are blocked for this HRegion until a compaction is completed, or until hbase.hstore.blockingWaitTime has been exceeded.', source='r1130916'} | |
| Property{key='hbase.hstore.blockingStoreFiles', value='10', description='If more than this number of StoreFiles in any one Store (one StoreFile is written per flush of MemStore) then updates are blocked for this HRegion until a compaction is completed, or until hbase.hstore.blockingWaitTime has been exceeded.', source='0.96'} | |
| Property{key='hbase.hstore.blockingStoreFiles', value='10', description='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.', source='0.99'} | |
| Difference found for property hbase.hstore.blockingWaitTime | |
| Property{key='hbase.hstore.blockingWaitTime', value='90000', description='The time an HRegion will block updates for after hitting the StoreFile limit defined by hbase.hstore.blockingStoreFiles. After this time has elapsed, the HRegion will stop blocking updates even if a compaction has not been completed. Default: 90 seconds.', source='r1130916'} | |
| Property{key='hbase.hstore.blockingWaitTime', value='90000', description='The time an HRegion will block updates for after hitting the StoreFile limit defined by hbase.hstore.blockingStoreFiles. After this time has elapsed, the HRegion will stop blocking updates even if a compaction has not been completed.', source='0.96'} | |
| Property{key='hbase.hstore.blockingWaitTime', value='90000', description='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.', source='0.99'} | |
| Difference found for property hbase.hstore.compaction.kv.max | |
| Property{key='hbase.hstore.compaction.kv.max', value='10', description='How many KeyValues to read and then write in a batch when flushing or compacting. Do less if big KeyValues and problems with OOME. Do more if wide, small rows.', source='0.96'} | |
| Property{key='hbase.hstore.compaction.kv.max', value='10', description='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.', source='0.99'} | |
| Difference found for property hbase.hstore.compaction.max | |
| Property{key='hbase.hstore.compaction.max', value='10', description='Max number of HStoreFiles to compact per 'minor' compaction.', source='r1130916'} | |
| Property{key='hbase.hstore.compaction.max', value='10', description='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.', source='0.99'} | |
| Difference found for property hbase.hstore.compactionThreshold | |
| Property{key='hbase.hstore.compactionThreshold', value='3', description='If more than this number of HStoreFiles in any one HStore (one HStoreFile is written per flush of memstore) then a compaction is run to rewrite all HStoreFiles files as one. Larger numbers put off compaction but when it runs, it takes longer to complete.', source='r1130916'} | |
| Property{key='hbase.hstore.compactionThreshold', value='3', description='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.', source='0.99'} | |
| Difference found for property hbase.ipc.client.fallback-to-simple-auth-allowed | |
| Property{key='hbase.ipc.client.fallback-to-simple-auth-allowed', value='false', description='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. This setting is only used by the secure RPC engine.', source='0.92'} | |
| Property{key='hbase.ipc.client.fallback-to-simple-auth-allowed', value='false', description='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.', source='0.96'} | |
| Difference found for property hbase.lease.recovery.dfs.timeout | |
| Property{key='hbase.lease.recovery.dfs.timeout', value='61000', description='How long between dfs recover lease invocations. Should be just larger than how long it takes the namenode to timeout trying to reach a datanode; usually dfs.socket.timeout. If HBase asked hdfs its cluster configs, we would not need this config. See the end of HBASE-8389 for more.', source='0.94'} | |
| Property{key='hbase.lease.recovery.dfs.timeout', value='64000', description='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.socket.timeout. See the end of HBASE-8389 for more.', source='0.96'} | |
| Property{key='hbase.lease.recovery.dfs.timeout', value='64000', description='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.', source='0.99'} | |
| Difference found for property hbase.master.info.port | |
| Property{key='hbase.master.info.port', value='60010', description='The port for the HBase Master web UI. Set to -1 if you do not want a UI instance run.', source='r1130916'} | |
| Property{key='hbase.master.info.port', value='16010', description='The port for the HBase Master web UI. Set to -1 if you do not want a UI instance run.', source='0.99'} | |
| Difference found for property hbase.master.logcleaner.plugins | |
| Property{key='hbase.master.logcleaner.plugins', value='org.apache.hadoop.hbase.master.TimeToLiveLogCleaner', description='A comma-separated list of LogCleanerDelegate invoked by the LogsCleaner service. These WAL/HLog cleaners are called in order, so put the HLog cleaner that prunes the most HLog files in front. To implement your own LogCleanerDelegate, 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.', source='r1130916'} | |
| Property{key='hbase.master.logcleaner.plugins', value='org.apache.hadoop.hbase.master.cleaner.TimeToLiveLogCleaner', description='A comma-separated list of LogCleanerDelegate invoked by the LogsCleaner service. These WAL/HLog cleaners are called in order, so put the HLog cleaner that prunes the most HLog files in front. To implement your own LogCleanerDelegate, 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.', source='0.94'} | |
| Difference found for property hbase.online.schema.update.enable | |
| Property{key='hbase.online.schema.update.enable', value='false', description='Set true to enable online schema changes. This is an experimental feature. There are known issues modifying table schemas at the same time a region split is happening so your table needs to be quiescent or else you have to be running with splits disabled.', source='0.92'} | |
| Property{key='hbase.online.schema.update.enable', value='true', description='Set true to enable online schema changes.', source='0.96'} | |
| Difference found for property hbase.regions.slop | |
| Property{key='hbase.regions.slop', value='0.2', description='Rebalance if any regionserver has average + (average * slop) regions. Default is 20% slop.', source='r1130916'} | |
| Property{key='hbase.regions.slop', value='0.2', description='Rebalance if any regionserver has average + (average * slop) regions.', source='0.96'} | |
| Difference found for property hbase.regionserver.checksum.verify | |
| Property{key='hbase.regionserver.checksum.verify', value='false', description='Allow hbase to do checksums rather than using hdfs checksums. This is a backwards incompatible change.', source='0.94'} | |
| Property{key='hbase.regionserver.checksum.verify', value='true', description='If set to true, HBase will read data and then verify checksums for hfile blocks. Checksum verification inside HDFS will be switched off. If the hbase-checksum verification fails, then it will switch back to using HDFS checksums.', source='0.96'} | |
| Property{key='hbase.regionserver.checksum.verify', value='true', description='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.', source='0.99'} | |
| Difference found for property hbase.regionserver.global.memstore.lowerLimit | |
| Property{key='hbase.regionserver.global.memstore.lowerLimit', value='0.35', description='When memstores are being forced to flush to make room in memory, keep flushing until we hit this mark. Defaults to 35% of heap. This value equal to hbase.regionserver.global.memstore.upperLimit causes the minimum possible flushing to occur when updates are blocked due to memstore limiting.', source='r1130916'} | |
| Property{key='hbase.regionserver.global.memstore.lowerLimit', value='0.38', description='Maximum size of all memstores in a region server before flushes are forced. Defaults to 38% of heap. This value equal to hbase.regionserver.global.memstore.upperLimit causes the minimum possible flushing to occur when updates are blocked due to memstore limiting.', source='0.96'} | |
| Difference found for property hbase.regionserver.global.memstore.upperLimit | |
| Property{key='hbase.regionserver.global.memstore.upperLimit', value='0.4', description='Maximum size of all memstores in a region server before new updates are blocked and flushes are forced. Defaults to 40% of heap', source='r1130916'} | |
| Property{key='hbase.regionserver.global.memstore.upperLimit', value='0.4', description='Maximum size of all memstores in a region server before new updates are blocked and flushes are forced. Defaults to 40% of heap. Updates are blocked and flushes are forced until size of all memstores in a region server hits hbase.regionserver.global.memstore.lowerLimit.', source='0.96'} | |
| Difference found for property hbase.regionserver.handler.count | |
| Property{key='hbase.regionserver.handler.count', value='10', description='Count of RPC Listener instances spun up on RegionServers. Same property is used by the Master for count of master handlers. Default is 10.', source='r1130916'} | |
| Property{key='hbase.regionserver.handler.count', value='30', description='Count of RPC Listener instances spun up on RegionServers. Same property is used by the Master for count of master handlers.', source='0.96'} | |
| Difference found for property hbase.regionserver.hlog.reader.impl | |
| Property{key='hbase.regionserver.hlog.reader.impl', value='org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader', description='The HLog file reader implementation.', source='r1130916'} | |
| Property{key='hbase.regionserver.hlog.reader.impl', value='org.apache.hadoop.hbase.regionserver.wal.ProtobufLogReader', description='The HLog file reader implementation.', source='0.96'} | |
| Difference found for property hbase.regionserver.hlog.writer.impl | |
| Property{key='hbase.regionserver.hlog.writer.impl', value='org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogWriter', description='The HLog file writer implementation.', source='r1130916'} | |
| Property{key='hbase.regionserver.hlog.writer.impl', value='org.apache.hadoop.hbase.regionserver.wal.ProtobufLogWriter', description='The HLog file writer implementation.', source='0.96'} | |
| Difference found for property hbase.regionserver.info.port | |
| Property{key='hbase.regionserver.info.port', value='60030', description='The port for the HBase RegionServer web UI Set to -1 if you do not want the RegionServer UI to run.', source='r1130916'} | |
| Property{key='hbase.regionserver.info.port', value='16030', description='The port for the HBase RegionServer web UI Set to -1 if you do not want the RegionServer UI to run.', source='0.99'} | |
| Difference found for property hbase.regionserver.optionallogflushinterval | |
| Property{key='hbase.regionserver.optionallogflushinterval', value='1000', description='Sync the HLog to the HDFS after this interval if it has not accumulated enough entries to trigger a sync. Default 1 second. Units: milliseconds.', source='r1130916'} | |
| Property{key='hbase.regionserver.optionallogflushinterval', value='1000', description='Sync the HLog to the HDFS after this interval if it has not accumulated enough entries to trigger a sync. Units: milliseconds.', source='0.96'} | |
| Difference found for property hbase.regionserver.port | |
| Property{key='hbase.regionserver.port', value='60020', description='The port the HBase RegionServer binds to.', source='r1130916'} | |
| Property{key='hbase.regionserver.port', value='16020', description='The port the HBase RegionServer binds to.', source='0.99'} | |
| Difference found for property hbase.regionserver.regionSplitLimit | |
| Property{key='hbase.regionserver.regionSplitLimit', value='2147483647', description='Limit for the number of regions after which no more region splitting should take place. This is not a 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 MAX_INT; i.e. do not block splitting.', source='r1130916'} | |
| Property{key='hbase.regionserver.regionSplitLimit', value='2147483647', description='Limit for the number of regions after which no more region splitting should take place. This is not a hard limit for the number of regions but acts as a guideline for the regionserver to stop splitting after a certain limit. Default is MAX_INT; i.e. do not block splitting.', source='0.96'} | |
| Difference found for property hbase.rest.threads.max | |
| Property{key='hbase.rest.threads.max', value='100', description='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. The default is 100.', source='0.94'} | |
| Property{key='hbase.rest.threads.max', value='100', description='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.', source='0.96'} | |
| Difference found for property hbase.rest.threads.min | |
| Property{key='hbase.rest.threads.min', value='2', description='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. The default is 2.', source='0.94'} | |
| Property{key='hbase.rest.threads.min', value='2', description='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.', source='0.96'} | |
| Difference found for property hbase.rootdir | |
| Property{key='hbase.rootdir', value='file:///tmp/hbase-${user.name}/hbase', description='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 HBase writes into /tmp. Change this configuration else all data will be lost on machine restart.', source='r1130916'} | |
| Property{key='hbase.rootdir', value='${hbase.tmp.dir}/hbase', description='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.', source='0.96'} | |
| Difference found for property hbase.status.multicast.address.port | |
| Property{key='hbase.status.multicast.address.port', value='60100', description='Multicast port to use for the status publication by multicast.', source='0.96'} | |
| Property{key='hbase.status.multicast.address.port', value='16100', description='Multicast port to use for the status publication by multicast.', source='0.99'} | |
| Difference found for property hbase.tmp.dir | |
| Property{key='hbase.tmp.dir', value='/tmp/hbase-${user.name}', description='Temporary directory on the local filesystem. Change this setting to point to a location more permanent than '/tmp' (The '/tmp' directory is often cleared on machine restart).', source='r1130916'} | |
| Property{key='hbase.tmp.dir', value='${java.io.tmpdir}/hbase-${user.name}', description='Temporary directory on the local filesystem. Change this setting to point to a location more permanent than '/tmp' (The '/tmp' directory is often cleared on machine restart).', source='0.94'} | |
| Property{key='hbase.tmp.dir', value='${java.io.tmpdir}/hbase-${user.name}', description='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.', source='0.96'} | |
| Difference found for property hbase.zookeeper.peerport | |
| Property{key='hbase.zookeeper.peerport', value='2888', description='Port used by ZooKeeper peers to talk to each other. See http://hadoop.apache.org/zookeeper/docs/r3.1.1/zookeeperStarted.html#sc_RunningReplicatedZooKeeper for more information.', source='r1130916'} | |
| Property{key='hbase.zookeeper.peerport', value='2888', description='Port used by ZooKeeper peers to talk to each other. Seehttp://hadoop.apache.org/zookeeper/docs/r3.1.1/zookeeperStarted.html#sc_RunningReplicatedZooKeeper for more information.', source='0.96'} | |
| Difference found for property hbase.zookeeper.property.maxClientCnxns | |
| Property{key='hbase.zookeeper.property.maxClientCnxns', value='30', description='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.', source='r1130916'} | |
| Property{key='hbase.zookeeper.property.maxClientCnxns', value='300', description='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.', source='0.92'} | |
| Difference found for property hbase.zookeeper.quorum | |
| Property{key='hbase.zookeeper.quorum', value='localhost', description='Comma separated list of servers in the ZooKeeper Quorum. 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 quorum servers. If HBASE_MANAGES_ZK is set in hbase-env.sh this is the list of servers which we will start/stop ZooKeeper on.', source='r1130916'} | |
| Property{key='hbase.zookeeper.quorum', value='localhost', description='Comma separated list of servers in the ZooKeeper ensemble (This config. should have been named hbase.zookeeper.ensemble). For example, "host1.mydomain.com,host2.mydomain.com,host3.mydomain.com". By default this is set to localhost for local and pseudo-distributed 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.clientPort config. and pass it into zookeeper constructor as the connectString parameter.', source='0.96'} | |
| Difference found for property hbase.zookeeper.useMulti | |
| Property{key='hbase.zookeeper.useMulti', value='false', description='Instructs HBase to make use of ZooKeeper's multi-update functionality. This allows certain ZooKeeper operations to complete more quickly and prevents some issues with rare ZooKeeper failure scenarios (see the release note of HBASE-6710 for an example). IMPORTANT: only set this to true if all ZooKeeper servers in the cluster are on version 3.4+ and will not be downgraded. ZooKeeper versions before 3.4 do not support multi-update and will not fail gracefully if multi-update is invoked (see ZOOKEEPER-1495).', source='0.94'} | |
| Property{key='hbase.zookeeper.useMulti', value='false', description='Instructs HBase to make use of ZooKeeper's multi-update functionality. This allows certain ZooKeeper operations to complete more quickly and prevents some issues with rare Replication failure scenarios (see the release note of HBASE-2611 for an example). IMPORTANT: only set this to true if all ZooKeeper servers in the cluster are on version 3.4+ and will not be downgraded. ZooKeeper versions before 3.4 do not support multi-update and will not fail gracefully if multi-update is invoked (see ZOOKEEPER-1495).', source='0.96'} | |
| Difference found for property hfile.block.cache.size | |
| Property{key='hfile.block.cache.size', value='0.2', description='Percentage of maximum heap (-Xmx setting) to allocate to block cache used by HFile/StoreFile. Default of 0.2 means allocate 20%. Set to 0 to disable.', source='r1130916'} | |
| Property{key='hfile.block.cache.size', value='0.25', description='Percentage of maximum heap (-Xmx setting) to allocate to block cache used by HFile/StoreFile. Default of 0.25 means allocate 25%. Set to 0 to disable but it's not recommended.', source='0.92'} | |
| Property{key='hfile.block.cache.size', value='0.4', description='Percentage of maximum heap (-Xmx setting) to allocate to block cache used by HFile/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.', source='0.96'} | |
| Property{key='hfile.block.cache.size', value='0.4', description='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.', source='0.99'} | |
| Difference found for property hfile.format.version | |
| Property{key='hfile.format.version', value='2', description='The HFile format version to use for new files. Set this to 1 to test backwards-compatibility. The default value of this option should be consistent with FixedFileTrailer.MAX_VERSION.', source='0.92'} | |
| Property{key='hfile.format.version', value='3', description='The HFile format version to use for new files. Version 3 adds support for tags in hfiles (See http://hbase.apache.org/book.html#hbase.tags). Distributed Log Replay requires that tags are enabled. Also see the configuration 'hbase.replication.rpc.codec'.', source='0.99'} | |
| Difference found for property zookeeper.session.timeout | |
| Property{key='zookeeper.session.timeout', value='180000', description='ZooKeeper session timeout. HBase passes this to the zk quorum as suggested maximum time for a session (This setting becomes zookeeper's 'maxSessionTimeout'). See http://hadoop.apache.org/zookeeper/docs/current/zookeeperProgrammers.html#ch_zkSessions "The client sends a requested timeout, the server responds with the timeout that it can give the client. " In milliseconds.', source='r1130916'} | |
| Property{key='zookeeper.session.timeout', value='90000', description='ZooKeeper session timeout in milliseconds. It is used in two different ways. First, this value is used in the ZK client that HBase uses to connect to the ensemble. It is also used by HBase when it starts a ZK server and it is passed as the 'maxSessionTimeout'. See http://hadoop.apache.org/zookeeper/docs/current/zookeeperProgrammers.html#ch_zkSessions. For example, if a HBase region server connects to a ZK ensemble that's also managed by HBase, then the session timeout will be the one specified by this configuration. But, a region server that connects to an ensemble managed with a different configuration will be subjected that ensemble's maxSessionTimeout. So, even though HBase might propose using 90 seconds, the ensemble can have a max timeout lower than this and it will take precedence. The current default that ZK ships with is 40 seconds, which is lower than HBase's.', source='0.96'} | |
| Total: 47 differences. | |
| ========================================================= |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment