Accumulo tables have a few options that can be configured to alter the default\n behavior of Accumulo as well as improve performance based on the data stored.\n These include locality groups, constraints, bloom filters, iterators, and block\n-cache. For a complete list of available configuration options, see Configuration Management.
\n+cache. For a complete list of available configuration options, see [configuration].\nAccumulo supports storing sets of column families separately on disk to allow\n clients to efficiently scan over columns that are frequently used together and to avoid\n scanning over column families that are not requested. After a locality group is set,\n@@ -7022,15 +6718,15 @@\n secret and make sure that the accumulo-site.xml file is not readable to other users.\n For alternatives to storing the instance.secret in plaintext, please read the\n Sensitive Configuration Values section.
\nSome settings can be modified via the Accumulo shell and take effect immediately, but\n some settings require a process restart to take effect. See the configuration documentation\n-(available in the docs directory of the tarball and in Configuration Management) for details.
\n+(available in the docs directory of the tarball and in [configuration]) for details.\nOne aspect of Accumulo’s configuration which is different as compared to the rest of the Hadoop\n ecosystem is that the server-process classpath is determined in part by multiple values. A\n bootstrap classpath is based soley on the accumulo-start.jar, Log4j and $ACCUMULO_CONF_DIR.
Q: My Hadoop DataNode is hung for hours trying to decommission.
\nA: Write Ahead Logs stay open until they hit the size threshold, which could be many hours or days in some cases. These open files will prevent a DN from finishing its decommissioning process (HDFS-3599) in some versions of Hadoop 2. If you stop the DN, then the WALog file will not be closed and you could lose data. To work around this issue, we now close WALogs on a time period specified by the property tserver.walog.max.age with a default period of 24 hours.
\nAll accumulo properties have a default value in the source code. Properties can also be set\n-in accumulo-site.xml and in zookeeper on per-table or system-wide basis. If properties are set in more than one location,\n-accumulo will choose the property with the highest precedence. This order of precedence is described\n-below (from highest to lowest):
\n-Table properties are applied to the entire cluster when set in zookeeper using the accumulo API or shell. While table properties take precedent over system properties, both will override properties set in accumulo-site.xml
\n-Table properties consist of all properties with the table.* prefix. Table properties are configured on a per-table basis using the following shell commmand:
\n-config -t TABLE -s PROPERTY=VALUE\n-
System properties are applied to the entire cluster when set in zookeeper using the accumulo API or shell. System properties consist of all properties with a yes in the Zookeeper Mutable column in the table below. They are set with the following shell command:
config -s PROPERTY=VALUE\n-
If a table.* property is set using this method, the value will apply to all tables except those configured on per-table basis (which have higher precedence).
\n-While most system properties take effect immediately, some require a restart of the process which is indicated in Zookeeper Mutable.
\n-Accumulo processes (master, tserver, etc) read their local accumulo-site.xml on start up. Therefore, changes made to accumulo-site.xml must rsynced across the cluster and processes must be restarted to apply changes.
\n-Certain properties (indicated by a no in Zookeeper Mutable) cannot be set in zookeeper and only set in this file. The accumulo-site.xml also allows you to configure tablet servers with different settings.
All properties have a default value in the source code. This value has the lowest precedence and is overriden if set in accumulo-site.xml or zookeeper.
\n-While the default value is usually optimal, there are cases where a change can increase query and ingest performance.
\n-Any properties that are stored in ZooKeeper should consider the limitations of ZooKeeper itself with respect to the\n-number of nodes and the size of the node data. Custom table properties and options for Iterators configured on tables\n-are two areas in which there aren’t any failsafes built into the API that can prevent the user from making this mistake.
\n-While these properties have the ability to add some much needed dynamic configuration tools, use cases which might fall\n-into these warnings should be reconsidered.
\n-The config command in the shell allows you to view the current system configuration. You can also use the -t option to view a table’s configuration as below:
$ ./bin/accumulo shell -u root\n-Enter current password for 'root'@'accumulo-instance': ******\n-\n-Shell - Apache Accumulo Interactive Shell\n--\n-- version: 1.6.0\n-- instance name: accumulo-instance\n-- instance id: 4f48fa03-f692-43ce-ae03-94c9ea8b7181\n--\n-- type 'help' for a list of available commands\n--\n-root@accumulo-instance> config -t foo\n----------+---------------------------------------------+------------------------------------------------------\n-SCOPE | NAME | VALUE\n----------+---------------------------------------------+------------------------------------------------------\n-default | table.balancer ............................ | org.apache.accumulo.server.master.balancer.DefaultLoadBalancer\n-default | table.bloom.enabled ....................... | false\n-default | table.bloom.error.rate .................... | 0.5%\n-default | table.bloom.hash.type ..................... | murmur\n-default | table.bloom.key.functor ................... | org.apache.accumulo.core.file.keyfunctor.RowFunctor\n-default | table.bloom.load.threshold ................ | 1\n-default | table.bloom.size .......................... | 1048576\n-default | table.cache.block.enable .................. | false\n-default | table.cache.index.enable .................. | false\n-default | table.compaction.major.everything.at ...... | 19700101000000GMT\n-default | table.compaction.major.everything.idle .... | 1h\n-default | table.compaction.major.ratio .............. | 1.3\n-site | @override .............................. | 1.4\n-system | @override .............................. | 1.5\n-table | @override .............................. | 1.6\n-default | table.compaction.minor.idle ............... | 5m\n-default | table.compaction.minor.logs.threshold ..... | 3\n-default | table.failures.ignore ..................... | false\n-
Jump to:\n-rpc.* | instance.* | instance.rpc.sasl.impersonation.* (Deprecated) | general.* | master.* | tserver.* | tserver.replication.replayer.* | gc.* | monitor.* | trace.* | trace.span.receiver.* | trace.token.property.* | table.* | table.custom.* | table.constraint.* | table.iterator.* | table.iterator.scan.* | table.iterator.minc.* | table.iterator.majc.* | table.group.* | table.majc.compaction.strategy.opts.* | table.replication.target.* | table.sampler.opt.* | general.vfs.context.classpath.* | replication.* | replication.peer.* | replication.peer.user.* | replication.peer.password.* | replication.peer.keytab.*
\n-Properties in this category related to the configuration of SSL keys for RPC. See also instance.ssl.enabled
\n-Path of the keystore file for the servers' private SSL key
\n-Type: PATH
\n-Zookeeper Mutable: no
\n-Default Value: $ACCUMULO_CONF_DIR/ssl/keystore.jks
Password used to encrypt the SSL private keystore. Leave blank to use the Accumulo instance secret
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: empty
Type of SSL keystore
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: jks
Path of the truststore file for the root cert
\n-Type: PATH
\n-Zookeeper Mutable: no
\n-Default Value: $ACCUMULO_CONF_DIR/ssl/truststore.jks
Password used to encrypt the SSL truststore. Leave blank to use no password
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: empty
Type of SSL truststore
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: jks
The quality of protection to be used with SASL. Valid values are 'auth', 'auth-int', and 'auth-conf'
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: auth
Comma separated list of cipher suites that can be used by accepted connections
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: empty
The protocol used to connect to a secure server, must be in the list of enabled protocols on the server side (rpc.ssl.server.enabled.protocols)
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: TLSv1.2
Comma separated list of protocols that can be used to accept connections
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: TLSv1.2
Use JSSE system properties to configure SSL rather than the rpc.javax.net.ssl.* Accumulo properties
\n-Type: BOOLEAN
\n-Zookeeper Mutable: no
\n-Default Value: false
Properties in this category must be consistent throughout a cloud. This is enforced and servers won’t be able to communicate if these differ.
\n-Deprecated. HDFS directory in which accumulo instance will run. Do not change after accumulo is initialized.
\n-Type: ABSOLUTEPATH
\n-Zookeeper Mutable: no
\n-Default Value: /accumulo
Deprecated. A url accumulo should use to connect to DFS. If this is empty, accumulo will obtain this information from the hadoop configuration. This property will only be used when creating new files if instance.volumes is empty. After an upgrade to 1.6.0 Accumulo will start using absolute paths to reference files. Files created before a 1.6.0 upgrade are referenced via relative paths. Relative paths will always be resolved using this config (if empty using the hadoop config).
\n-Type: URI
\n-Zookeeper Mutable: no
\n-Default Value: empty
One-line configuration property controlling the network locations (hostnames) that are allowed to impersonate other users
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: empty
One-line configuration property controlling what users are allowed to impersonate other users
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: empty
Configures Thrift RPCs to require SASL with GSSAPI which supports Kerberos authentication. Mutually exclusive with SSL RPC configuration.
\n-Type: BOOLEAN
\n-Zookeeper Mutable: no
\n-Default Value: false
Require clients to present certs signed by a trusted root
\n-Type: BOOLEAN
\n-Zookeeper Mutable: no
\n-Default Value: false
Use SSL for socket connections from clients and among accumulo services. Mutually exclusive with SASL RPC configuration.
\n-Type: BOOLEAN
\n-Zookeeper Mutable: no
\n-Default Value: false
A secret unique to a given instance that all servers must know in order to communicate with one another. It should be changed prior to the initialization of Accumulo. To change it after Accumulo has been initialized, use the ChangeSecret tool and then update conf/accumulo-site.xml everywhere. Before using the ChangeSecret tool, make sure Accumulo is not running and you are logged in as the user that controls Accumulo files in HDFS. To use the ChangeSecret tool, run the command: ./bin/accumulo org.apache.accumulo.server.util.ChangeSecret
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: DEFAULT
The authenticator class that accumulo will use to determine if a user has privilege to perform an action
\n-Type: CLASSNAME
\n-Zookeeper Mutable: no
\n-Default Value: org.apache.accumulo.server.security.handler.ZKAuthenticator
The authorizor class that accumulo will use to determine what labels a user has privilege to see
\n-Type: CLASSNAME
\n-Zookeeper Mutable: no
\n-Default Value: org.apache.accumulo.server.security.handler.ZKAuthorizor
The permission handler class that accumulo will use to determine if a user has privilege to perform an action
\n-Type: CLASSNAME
\n-Zookeeper Mutable: no
\n-Default Value: org.apache.accumulo.server.security.handler.ZKPermHandler
A comma seperated list of dfs uris to use. Files will be stored across these filesystems. If this is empty, then instance.dfs.uri will be used. After adding uris to this list, run 'accumulo init --add-volume' and then restart tservers. If entries are removed from this list then tservers will need to be restarted. After a uri is removed from the list Accumulo will not create new files in that location, however Accumulo can still reference files created at that location before the config change. To use a comma or other reserved characters in a URI use standard URI hex encoding. For example replace commas with %2C.
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: empty
Since accumulo stores absolute URIs changing the location of a namenode could prevent Accumulo from starting. The property helps deal with that situation. Provide a comma separated list of uri replacement pairs here if a namenode location changes. Each pair shold be separated with a space. For example, if hdfs://nn1 was replaced with hdfs://nnA and hdfs://nn2 was replaced with hdfs://nnB, then set this property to 'hdfs://nn1 hdfs://nnA,hdfs://nn2 hdfs://nnB' Replacements must be configured for use. To see which volumes are currently in use, run 'accumulo admin volumes -l'. To use a comma or other reserved characters in a URI use standard URI hex encoding. For example replace commas with %2C.
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: empty
Comma separated list of zookeeper servers
\n-Type: HOSTLIST
\n-Zookeeper Mutable: no
\n-Default Value: localhost:2181
Zookeeper session timeout; max value when represented as milliseconds should be no larger than 2147483647
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: no
\n-Default Value: 30s
Deprecated. Prefix that allows configuration of users that are allowed to impersonate other users
\n-Properties in this category affect the behavior of accumulo overall, but do not have to be consistent throughout a cloud.
\n-A list of all of the places to look for a class. Order does matter, as it will look for the jar starting in the first location to the last. Please note, hadoop conf and hadoop lib directories NEED to be here, along with accumulo lib and zookeeper directory. Supports full regex on filename alone.
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value:
$ACCUMULO_CONF_DIR,\n-$ACCUMULO_HOME/lib/[^.].*.jar,\n-$ZOOKEEPER_HOME/zookeeper[^.].*.jar,\n-$HADOOP_CONF_DIR,\n-$HADOOP_PREFIX/[^.].*.jar,\n-$HADOOP_PREFIX/lib/(?!slf4j)[^.].*.jar,\n-$HADOOP_PREFIX/share/hadoop/common/[^.].*.jar,\n-$HADOOP_PREFIX/share/hadoop/common/lib/(?!slf4j)[^.].*.jar,\n-$HADOOP_PREFIX/share/hadoop/hdfs/[^.].*.jar,\n-$HADOOP_PREFIX/share/hadoop/mapreduce/[^.].*.jar,\n-$HADOOP_PREFIX/share/hadoop/yarn/[^.].*.jar,\n-$HADOOP_PREFIX/share/hadoop/yarn/lib/jersey.*.jar,\n-/usr/hdp/current/hadoop-client/[^.].*.jar,\n-/usr/hdp/current/hadoop-client/lib/(?!slf4j)[^.].*.jar,\n-/usr/hdp/current/hadoop-hdfs-client/[^.].*.jar,\n-/usr/hdp/current/hadoop-mapreduce-client/[^.].*.jar,\n-/usr/hdp/current/hadoop-yarn-client/[^.].*.jar,\n-/usr/hdp/current/hadoop-yarn-client/lib/jersey.*.jar,\n-/usr/hdp/current/hive-client/lib/hive-accumulo-handler.jar\n-/usr/lib/hadoop/[^.].*.jar,\n-/usr/lib/hadoop/lib/[^.].*.jar,\n-/usr/lib/hadoop-hdfs/[^.].*.jar,\n-/usr/lib/hadoop-mapreduce/[^.].*.jar,\n-/usr/lib/hadoop-yarn/[^.].*.jar,\n-/usr/lib/hadoop-yarn/lib/jersey.*.jar,\n-
The length of time that delegation tokens and secret keys are valid
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: no
\n-Default Value: 7d
The length of time between generation of new secret keys
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: no
\n-Default Value: 1d
A list of all of the places where changes in jars or classes will force a reload of the classloader.
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: $ACCUMULO_HOME/lib/ext/[^.].*.jar
Path to the kerberos keytab to use. Leave blank if not using kerberoized hdfs
\n-Type: PATH
\n-Zookeeper Mutable: no
\n-Default Value: empty
Name of the kerberos principal to use. _HOST will automatically be replaced by the machines hostname in the hostname portion of the principal. Leave blank if not using kerberoized hdfs
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: empty
The amount of time between attempts to perform Kerberos ticket renewals. This does not equate to how often tickets are actually renewed (which is performed at 80% of the ticket lifetime).
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: no
\n-Default Value: 30s
Use the old metric infrastructure configured by accumulo-metrics.xml, instead of Hadoop Metrics2
\n-Type: BOOLEAN
\n-Zookeeper Mutable: no
\n-Default Value: false
The maximum amount of time that a Scanner should wait before retrying a failed RPC
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: no
\n-Default Value: 5s
Time to wait on I/O for simple, short RPC calls
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: no
\n-Default Value: 120s
Comma-separated list of paths to CredentialProviders
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: empty
The maximum size of a message that can be sent to a server.
\n-Type: MEMORY
\n-Zookeeper Mutable: no
\n-Default Value: 1G
The number of threads to use for server-internal scheduled tasks
\n-Type: COUNT
\n-Zookeeper Mutable: no
\n-Default Value: 1
Directory to use for the vfs cache. The cache will keep a soft reference to all of the classes loaded in the VM. This should be on local disk on each node with sufficient space. It defaults to ${java.io.tmpdir}/accumulo-vfs-cache-${user.name}
\n-Type: ABSOLUTEPATH
\n-Zookeeper Mutable: no
\n-Default Value: ${java.io.tmpdir}/accumulo-vfs-cache-${user.name}
Configuration for a system level vfs classloader. Accumulo jar can be configured here and loaded out of HDFS.
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: empty
Properties in this category affect the behavior of the master server
\n-The number of threads to use when moving user files to bulk ingest directories under accumulo control
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 20
The number of attempts to bulk-load a file before giving up.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 3
The number of threads to use when coordinating a bulk-import.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 5
The time to wait for a tablet server to process a bulk import request
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 5m
Enable reporting of FATE metrics in JMX (and logging with Hadoop Metrics2
\n-Type: BOOLEAN
\n-Zookeeper Mutable: yes
\n-Default Value: false
Limit calls from metric sinks to zookeeper to update interval
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 60s
The number of threads used to run FAult-Tolerant Executions. These are primarily table operations like merge.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 4
The amount of time to wait after requesting a WAL file to be recovered
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 5s
Allow tablets for the accumulo.metadata table to be suspended via table.suspend.duration.
\n-Type: BOOLEAN
\n-Zookeeper Mutable: yes
\n-Default Value: false
The port used for handling client connections on the master
\n-Type: PORT
\n-Zookeeper Mutable: yes but requires restart of the master
\n-Default Value: 9999
When a tablet server’s lock is deleted, it takes time for it to completely quit. This delay gives it time before log recoveries begin.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 10s
Recovery files older than this age will be removed.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 60m
The maximum time to attempt recovery before giving up
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 30m
Minimum number of threads dedicated to answering coordinator requests
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 4
Port for the replication coordinator service
\n-Type: PORT
\n-Zookeeper Mutable: yes
\n-Default Value: 10001
The time between adjustments of the coordinator thread pool
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 5s
Amount of time to sleep before scanning the status section of the replication table for new data
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 30s
The time between adjustments of the server thread pool.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 1s
The minimum number of threads to use to handle incoming requests.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 20
Maximum time master will wait for tserver available threshold to be reached before continuing. When set to 0 or less, will block indefinitely. Default is 0 to block indefinitely. Only valid when tserver available threshold is set greater than 0. Added with version 1.10
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 0
Minimum number of tservers that need to be registered before master will start tablet assignment - checked at master initialization, when master gets lock. When set to 0 or less, no blocking occurs. Default is 0 (disabled) to keep original behaviour. Added with version 1.10
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 0
The number of threads to use when fetching the tablet server status for balancing. Zero indicates an unlimited number of threads will be used.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 0
The balancer class that accumulo will use to make tablet assignment and migration decisions.
\n-Type: CLASSNAME
\n-Zookeeper Mutable: yes
\n-Default Value: org.apache.accumulo.server.master.balancer.TableLoadBalancer
A class that implements a mechansim to steal write access to a file
\n-Type: CLASSNAME
\n-Zookeeper Mutable: yes
\n-Default Value: org.apache.accumulo.server.master.recovery.HadoopLogCloser
Properties in this category affect the behavior of the tablet servers
\n-Keep copies of the WALOGs for debugging purposes
\n-Type: BOOLEAN
\n-Zookeeper Mutable: yes
\n-Default Value: false
The number of threads available to load tablets. Recoveries are still performed serially.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 2
The amount of time an assignment can run before the server will print a warning along with the current stack trace. Meant to help debug stuck assignments
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 10m
The number of concurrent threads that will load bloom filters in the background. Setting this to zero will make bloom filters load in the foreground.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 4
The master delegates bulk file processing and assignment to tablet servers. After the bulk file has been processed, the tablet server will assign the file to the appropriate tablets on all servers. This property controls the number of threads used to communicate to the other servers.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 1
The master will task a tablet server with pre-processing a bulk file prior to assigning it to the appropriate tablet servers. This configuration value controls the number of threads used to process the files.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 1
The number of times the tablet server will attempt to assign a file to a tablet as it migrates and splits.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 5
The time to wait for a tablet server to process a bulk import request.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 5m
Specifies the size of the cache for file data blocks.
\n-Type: MEMORY
\n-Zookeeper Mutable: yes
\n-Default Value: 128M
Specifies the size of the cache for file indices.
\n-Type: MEMORY
\n-Zookeeper Mutable: yes
\n-Default Value: 512M
Time to wait for clients to continue scans before closing a session.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 3s
The maximum number of concurrent major compactions for a tablet server
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 3
Time a tablet server will sleep between checking which tablets need compaction.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 30s
Max number of files a major compaction thread can open at once.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 10
Maximum number of bytes to read or write per second over all major compactions on a TabletServer, or 0B for unlimited.
\n-Type: MEMORY
\n-Zookeeper Mutable: yes
\n-Default Value: 0B
The percent of major compactions to trace
\n-Type: FRACTION
\n-Zookeeper Mutable: yes
\n-Default Value: 0.1
The maximum number of concurrent minor compactions for a tablet server
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 4
The percent of minor compactions to trace
\n-Type: FRACTION
\n-Zookeeper Mutable: yes
\n-Default Value: 0.1
When a compaction has not made progress for this time period, a warning will be logged
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 10m
Specifies a default blocksize for the tserver caches
\n-Type: MEMORY
\n-Zookeeper Mutable: yes
\n-Default Value: 1M
A long running scan could possibly hold memory that has been minor compacted. To prevent this, the in memory map is dumped to a local file and the scan is switched to that local file. We can not switch to the minor compacted file because it may have been modified by iterators. The file dumped to the local dir is an exact copy of what was in memory.
\n-Type: PATH
\n-Zookeeper Mutable: yes
\n-Default Value: /tmp
Tablet servers leave previously used files open for future queries. This setting determines how much time an unused file should be kept open until it is closed.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 1m
The maximum time for a tablet server to be in the \"memory full\" state. If the tablet server cannot write out memory in this much time, it will assume there is some failure local to its node, and quit. A value of zero is equivalent to forever.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 5m
Number of busiest tablets to log. Logged at interval controlled by tserver.log.busy.tablets.interval. If ⇐ 0, logging of busy tablets is disabled
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 0
Time interval between logging out busy tablets information.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 1h
An implementation of MemoryManger that accumulo will use.
\n-Type: CLASSNAME
\n-Zookeeper Mutable: yes
\n-Default Value: org.apache.accumulo.server.tabletserver.LargestFirstMemoryManager
Maximum amount of memory that can be used to buffer data written to a tablet server. There are two other properties that can effectively limit memory usage table.compaction.minor.logs.threshold and tserver.walog.max.size. Ensure that table.compaction.minor.logs.threshold * tserver.walog.max.size >= this property.
\n-Type: MEMORY
\n-Zookeeper Mutable: yes
\n-Default Value: 1G
An in-memory data store for accumulo implemented in c++ that increases the amount of data accumulo can hold in memory and avoids Java GC pauses.
\n-Type: BOOLEAN
\n-Zookeeper Mutable: yes but requires restart of the tserver
\n-Default Value: true
The maximum number of concurrent metadata read ahead that will execute.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 8
The maximum number of concurrent tablet migrations for a tablet server
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 1
When enabled the tserver will monitor file systems and kill itself when one switches from rw to ro. This is usually and indication that Linux has detected a bad disk.
\n-Type: BOOLEAN
\n-Zookeeper Mutable: yes
\n-Default Value: true
Deprecated. This setting is deprecated. See tserver.total.mutation.queue.max. The amount of memory to use to store write-ahead-log mutations-per-session before flushing them. Since the buffer is per write session, consider the max number of concurrent writer when configuring. When using Hadoop 2, Accumulo will call hsync() on the WAL. For a small number of concurrent writers, increasing this buffer size decreases the frequncy of hsync calls. For a large number of concurrent writers a small buffers size is ok because of group commit.
\n-Type: MEMORY
\n-Zookeeper Mutable: yes
\n-Default Value: 1M
The port used for handling client connections on the tablet servers
\n-Type: PORT
\n-Zookeeper Mutable: yes but requires restart of the tserver
\n-Default Value: 9997
if the ports above are in use, search higher ports until one is available
\n-Type: BOOLEAN
\n-Zookeeper Mutable: yes
\n-Default Value: false
The maximum number of concurrent read ahead that will execute. This effectively limits the number of long running scans that can run concurrently per tserver.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 16
The maximum number of threads to use to sort logs during recovery
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 2
Memory to provide to batchwriter to replay mutations for replication
\n-Type: MEMORY
\n-Zookeeper Mutable: yes
\n-Default Value: 50M
Default AccumuloReplicationReplayer implementation
\n-Type: CLASSNAME
\n-Zookeeper Mutable: yes
\n-Default Value: org.apache.accumulo.tserver.replication.BatchWriterReplicationReplayer
Maximum total files that all tablets in a tablet server can open for scans.
\n-Type: COUNT
\n-Zookeeper Mutable: yes but requires restart of the tserver
\n-Default Value: 100
The maximum size of a message that can be sent to a tablet server.
\n-Type: MEMORY
\n-Zookeeper Mutable: yes
\n-Default Value: 1G
The time between adjustments of the server thread pool.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 1s
The minimum number of threads to use to handle incoming requests.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 20
When a tablet server’s SimpleTimer thread triggers to check idle sessions, this configurable option will be used to evaluate scan sessions to determine if they can be closed due to inactivity
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 1m
When a tablet server’s SimpleTimer thread triggers to check idle sessions, this configurable option will be used to evaluate update sessions to determine if they can be closed due to inactivity
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 1m
If a thread blocks more than this period of time waiting to get file permits, debugging information will be written.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 100ms
If a flush to the write-ahead log takes longer than this period of time, debugging information will written, and may result in a log rollover.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 100ms
The amount of memory to use when sorting logs during recovery.
\n-Type: MEMORY
\n-Zookeeper Mutable: yes
\n-Default Value: 200M
To find a tablets split points, all index files are opened. This setting determines how many index files can be opened at once. When there are more index files than this setting multiple passes must be made, which is slower. However opening too many files at once can cause problems.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 300
The amount of memory used to store write-ahead-log mutations before flushing them.
\n-Type: MEMORY
\n-Zookeeper Mutable: yes
\n-Default Value: 50M
The size of the HDFS blocks used to write to the Write-Ahead log. If zero, it will be 110% of tserver.walog.max.size (that is, try to use just one block)
\n-Type: MEMORY
\n-Zookeeper Mutable: yes
\n-Default Value: 0
The replication to use when writing the Write-Ahead log to HDFS. If zero, it will use the HDFS default replication setting.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 0
Use the SYNC_BLOCK create flag to sync WAL writes to disk. Prevents problems recovering from sudden system resets.
\n-Type: BOOLEAN
\n-Zookeeper Mutable: yes
\n-Default Value: true
Deprecated. This property is deprecated. Use table.durability instead.
\n-Type: STRING
\n-Zookeeper Mutable: yes
\n-Default Value: hsync
The maximum age for each write-ahead log.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 24h
The maximum size for each write-ahead log. See comment for tserver.memory.maps.max
\n-Type: MEMORY
\n-Zookeeper Mutable: yes
\n-Default Value: 1G
The maximum amount of time to wait after a failure to create or write a WAL file.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 5m
The maximum number of failures tolerated when creating a new WAL file. Negative values will allow unlimited creation failures. Exceeding this number of failures consecutively trying to create a new WAL causes the TabletServer to exit.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 50
The amount of time to wait between failures to create or write a WALog.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 1000ms
The number of threads for the distributed work queue. These threads are used for copying failed bulk files.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 2
Allows configuration of implementation used to apply replicated data
\n-Properties in this category affect the behavior of the accumulo garbage collector.
\n-Time between garbage collection cycles. In each cycle, old files no longer in use are removed from the filesystem.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 5m
Time to wait before attempting to garbage collect any old files.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 30s
Archive any files/directories instead of moving to the HDFS trash or deleting.
\n-Type: BOOLEAN
\n-Zookeeper Mutable: yes
\n-Default Value: false
Enable detailed gc metrics reporting with hadoop metrics.
\n-Type: BOOLEAN
\n-Zookeeper Mutable: yes
\n-Default Value: false
The listening port for the garbage collector’s monitor service
\n-Type: PORT
\n-Zookeeper Mutable: yes but requires restart of the gc
\n-Default Value: 9998
When the gc runs it can make a lot of changes to the metadata, on completion, to force the changes to be written to disk, the metadata and root tables can be flushed and possibly compacted. Legal values are: compact - which both flushes and compacts the metadata; flush - which flushes only (compactions may be triggered if required); or none
\n-Type: GC_POST_ACTION
\n-Zookeeper Mutable: yes
\n-Default Value: compact
The number of threads used to delete files
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 16
Percent of gc cycles to trace
\n-Type: FRACTION
\n-Zookeeper Mutable: yes
\n-Default Value: 0.01
Do not use the Trash, even if it is configured.
\n-Type: BOOLEAN
\n-Zookeeper Mutable: yes
\n-Default Value: false
Properties in this category affect the behavior of the monitor web server.
\n-The background color of the banner text displayed on the monitor page.
\n-Type: STRING
\n-Zookeeper Mutable: yes
\n-Default Value: #304065
The color of the banner text displayed on the monitor page.
\n-Type: STRING
\n-Zookeeper Mutable: yes
\n-Default Value: #c4c4c4
The banner text displayed on the monitor page.
\n-Type: STRING
\n-Zookeeper Mutable: yes
\n-Default Value: empty
The amount of time to sleep between checking for the Montior ZooKeeper lock
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: no
\n-Default Value: 5s
The SimpleDateFormat string used to configure the date shown on the 'Recent Logs' monitor page
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: yyyy/MM/dd HH:mm:ss,SSS
The listening port for the monitor’s http service
\n-Type: PORT
\n-Zookeeper Mutable: no
\n-Default Value: 9995
The listening port for the monitor’s log4j logging collection.
\n-Type: PORT
\n-Zookeeper Mutable: no
\n-Default Value: 4560
A comma-separated list of disallowed SSL Ciphers, see monitor.ssl.include.ciphers to allow ciphers
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: empty
A comma-separated list of allows SSL Ciphers, see monitor.ssl.exclude.ciphers to disallow ciphers
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: empty
A comma-separate list of allowed SSL protocols
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: TLSv1.2
Optional: the password for the private key in the keyStore. When not provided, this defaults to the keystore password.
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: empty
The keystore for enabling monitor SSL.
\n-Type: PATH
\n-Zookeeper Mutable: no
\n-Default Value: empty
The keystore password for enabling monitor SSL.
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: empty
Type of SSL keystore
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: jks
The truststore for enabling monitor SSL.
\n-Type: PATH
\n-Zookeeper Mutable: no
\n-Default Value: empty
The truststore password for enabling monitor SSL.
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: empty
Type of SSL truststore
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: jks
Properties in this category affect the behavior of distributed tracing.
\n-The password for the user used to store distributed traces
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: secret
The listening port for the trace server
\n-Type: PORT
\n-Zookeeper Mutable: no
\n-Default Value: 12234
A list of span receiver classes to send trace spans
\n-Type: CLASSNAMELIST
\n-Zookeeper Mutable: no
\n-Default Value: org.apache.accumulo.tracer.ZooTraceClient
The name of the table to store distributed traces
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: trace
An AuthenticationToken type supported by the authorizer
\n-Type: CLASSNAME
\n-Zookeeper Mutable: no
\n-Default Value: org.apache.accumulo.core.client.security.tokens.PasswordToken
The name of the user to store distributed traces
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: root
The zookeeper node where tracers are registered
\n-Type: STRING
\n-Zookeeper Mutable: no
\n-Default Value: /tracers
Prefix for span receiver configuration properties
\n-The prefix used to create a token for storing distributed traces. For each propetry required by trace.token.type, place this prefix in front of it.
\n-Properties in this category affect tablet server treatment of tablets, but can be configured on a per-table basis. Setting these properties in the site file will override the default globally for all tables and not any specific table. However, both the default and the global setting can be overridden per table using the table operations API or in the shell, which sets the overridden value in zookeeper. Restarting accumulo tablet servers after setting these properties in the site file will cause the global setting to take effect. However, you must use the API or the shell to change properties in zookeeper that are set on a table.
\n-This property can be set to allow the LoadBalanceByTable load balancer to change the called Load Balancer for this table
\n-Type: STRING
\n-Zookeeper Mutable: yes
\n-Default Value: org.apache.accumulo.server.master.balancer.DefaultLoadBalancer
Use bloom filters on this table.
\n-Type: BOOLEAN
\n-Zookeeper Mutable: yes
\n-Default Value: false
Bloom filter error rate.
\n-Type: FRACTION
\n-Zookeeper Mutable: yes
\n-Default Value: 0.5%
The bloom filter hash type
\n-Type: STRING
\n-Zookeeper Mutable: yes
\n-Default Value: murmur
A function that can transform the key prior to insertion and check of bloom filter. org.apache.accumulo.core.file.keyfunctor.RowFunctor, org.apache.accumulo.core.file.keyfunctor.ColumnFamilyFunctor, and org.apache.accumulo.core.file.keyfunctor.ColumnQualifierFunctor are allowable values. One can extend any of the above mentioned classes to perform specialized parsing of the key.
\n-Type: CLASSNAME
\n-Zookeeper Mutable: yes
\n-Default Value: org.apache.accumulo.core.file.keyfunctor.RowFunctor
This number of seeks that would actually use a bloom filter must occur before a file’s bloom filter is loaded. Set this to zero to initiate loading of bloom filters when a file is opened.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 1
Bloom filter size, as number of keys.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 1048576
Determines whether file block cache is enabled.
\n-Type: BOOLEAN
\n-Zookeeper Mutable: yes
\n-Default Value: false
Determines whether index cache is enabled.
\n-Type: BOOLEAN
\n-Zookeeper Mutable: yes
\n-Default Value: true
Per table classpath context
\n-Type: STRING
\n-Zookeeper Mutable: yes
\n-Default Value: empty
After a tablet has been idle (no mutations) for this time period it may have all of its files compacted into one. There is no guarantee an idle tablet will be compacted. Compactions of idle tablets are only started when regular compactions are not running. Idle compactions only take place for tablets that have one or more files.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 1h
minimum ratio of total input size to maximum input file size for running a major compactionWhen adjusting this property you may want to also adjust table.file.max. Want to avoid the situation where only merging minor compactions occur.
\n-Type: FRACTION
\n-Zookeeper Mutable: yes
\n-Default Value: 3
After a tablet has been idle (no mutations) for this time period it may have its in-memory map flushed to disk in a minor compaction. There is no guarantee an idle tablet will be compacted.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 5m
When there are more than this many write-ahead logs against a tablet, it will be minor compacted. See comment for property tserver.memory.maps.max
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 3
The max file size used for a merging minor compaction. The default value of 0 disables a max file size.
\n-Type: MEMORY
\n-Zookeeper Mutable: yes
\n-Default Value: 0
The durability used to write to the write-ahead log. Legal values are: none, which skips the write-ahead log; log, which sends the data to the write-ahead log, but does nothing to make it durable; flush, which pushes data to the file system; and sync, which ensures the data is written to disk.
\n-Type: DURABILITY
\n-Zookeeper Mutable: yes
\n-Default Value: sync
If you want queries for your table to hang or fail when data is missing from the system, then set this to false. When this set to true missing data will be reported but queries will still run possibly returning a subset of the data.
\n-Type: BOOLEAN
\n-Zookeeper Mutable: yes
\n-Default Value: false
Overrides the hadoop dfs.block.size setting so that files have better query performance. The maximum value for this is 2147483647
\n-Type: MEMORY
\n-Zookeeper Mutable: yes
\n-Default Value: 0B
Similar to the hadoop io.seqfile.compress.blocksize setting, so that files have better query performance. The maximum value for this is 2147483647. (This setting is the size threshold prior to compression, and applies even compression is disabled.)
\n-Type: MEMORY
\n-Zookeeper Mutable: yes
\n-Default Value: 100K
Determines how large index blocks can be in files that support multilevel indexes. The maximum value for this is 2147483647. (This setting is the size threshold prior to compression, and applies even compression is disabled.)
\n-Type: MEMORY
\n-Zookeeper Mutable: yes
\n-Default Value: 128K
One of gz,snappy,lzo,none
\n-Type: STRING
\n-Zookeeper Mutable: yes
\n-Default Value: gz
Determines the max # of files each tablet in a table can have. When adjusting this property you may want to consider adjusting table.compaction.major.ratio also. Setting this property to 0 will make it default to tserver.scan.files.open.max-1, this will prevent a tablet from having more files than can be opened. Setting this property low may throttle ingest and increase query performance.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 15
Determines how many replicas to keep of a tables' files in HDFS. When this value is LTE 0, HDFS defaults are used.
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 0
Change the type of file a table writes
\n-Type: STRING
\n-Zookeeper Mutable: yes
\n-Default Value: rf
The Formatter class to apply on results in the shell
\n-Type: STRING
\n-Zookeeper Mutable: yes
\n-Default Value: org.apache.accumulo.core.util.format.DefaultFormatter
A comma separated list of locality group names to enable for this table.
\n-Type: STRING
\n-Zookeeper Mutable: yes
\n-Default Value: empty
The ScanInterpreter class to apply on scan arguments in the shell
\n-Type: STRING
\n-Zookeeper Mutable: yes
\n-Default Value: org.apache.accumulo.core.util.interpret.DefaultScanInterpreter
A customizable major compaction strategy.
\n-Type: CLASSNAME
\n-Zookeeper Mutable: yes
\n-Default Value: org.apache.accumulo.tserver.compaction.DefaultCompactionStrategy
Is replication enabled for the given table
\n-Type: BOOLEAN
\n-Zookeeper Mutable: yes
\n-Default Value: false
The name of a class that implements org.apache.accumulo.core.Sampler. Setting this option enables storing a sample of data which can be scanned. Always having a current sample can useful for query optimization and data comprehension. After enabling sampling for an existing table, a compaction is needed to compute the sample for existing data. The compact command in the shell has an option to only compact files without sample data.
\n-Type: CLASSNAME
\n-Zookeeper Mutable: yes
\n-Default Value: empty
The maximum amount of memory that will be used to cache results of a client query/scan. Once this limit is reached, the buffered data is sent to the client.
\n-Type: MEMORY
\n-Zookeeper Mutable: yes
\n-Default Value: 512K
The security label that will be assumed at scan time if an entry does not have a visibility expression.\n-Note: An empty security label is displayed as []. The scan results will show an empty visibility even if the visibility from this setting is applied to the entry.\n-CAUTION: If a particular key has an empty security label AND its table’s default visibility is also empty, access will ALWAYS be granted for users with permission to that table. Additionally, if this field is changed, all existing data with an empty visibility label will be interpreted with the new label on the next scan.
\n-Type: STRING
\n-Zookeeper Mutable: yes
\n-Default Value: empty
Maximum size of end row
\n-Type: MEMORY
\n-Zookeeper Mutable: yes
\n-Default Value: 10K
When combined size of files exceeds this amount a tablet is split.
\n-Type: MEMORY
\n-Zookeeper Mutable: yes
\n-Default Value: 1G
For tablets belonging to this table: When a tablet server dies, allow the tablet server this duration to revive before reassigning its tablets to other tablet servers.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 0s
Deprecated. This setting is deprecated. Use table.durability=none instead.
\n-Type: BOOLEAN
\n-Zookeeper Mutable: yes
\n-Default Value: true
Prefix to be used for user defined arbitrary properties.
\n-Properties in this category are per-table properties that add constraints to a table. These properties start with the category prefix, followed by a number, and their values correspond to a fully qualified Java class that implements the Constraint interface.\n-For example:\n-table.constraint.1 = org.apache.accumulo.core.constraints.MyCustomConstraint\n-and:\n- table.constraint.2 = my.package.constraints.MySecondConstraint
\n-Properties in this category specify iterators that are applied at various stages (scopes) of interaction with a table. These properties start with the category prefix, followed by a scope (minc, majc, scan, etc.), followed by a period, followed by a name, as in table.iterator.scan.vers, or table.iterator.scan.custom. The values for these properties are a number indicating the ordering in which it is applied, and a class name such as:\n-table.iterator.scan.vers = 10,org.apache.accumulo.core.iterators.VersioningIterator\n-These iterators can take options if additional properties are set that look like this property, but are suffixed with a period, followed by 'opt' followed by another period, and a property name.\n-For example, table.iterator.minc.vers.opt.maxVersions = 3
\n-Convenience prefix to find options for the scan iterator scope
\n-Convenience prefix to find options for the minc iterator scope
\n-Convenience prefix to find options for the majc iterator scope
\n-Properties in this category are per-table properties that define locality groups in a table. These properties start with the category prefix, followed by a name, followed by a period, and followed by a property for that group.\n-For example table.group.group1=x,y,z sets the column families for a group called group1. Once configured, group1 can be enabled by adding it to the list of groups in the table.groups.enabled property.\n-Additional group options may be specified for a named group by setting table.group.<name>.opt.<key>=<value>.
\n-Properties in this category are used to configure the compaction strategy.
\n-Enumerate a mapping of other systems which this table should replicate their data to. The key suffix is the identifying cluster name and the value is an identifier for a location on the target system, e.g. the ID of the table on the target to replicate to
\n-The property is used to set options for a sampler. If a sample had two options like hasher and modulous, then the two properties table.sampler.opt.hasher=${hash algorithm} and table.sampler.opt.modulous=${mod} would be set.
\n-Properties in this category are define a classpath. These properties start with the category prefix, followed by a context name. The value is a comma seperated list of URIs. Supports full regex on filename alone. For example, general.vfs.context.classpath.cx1=hdfs://nn1:9902/mylibdir/*.jar. You can enable post delegation for a context, which will load classes from the context first instead of the parent first. Do this by setting general.vfs.context.classpath.<name>.delegation=post, where <name> is your context name. If delegation is not specified, it defaults to loading from parent classloader first.
\n-Properties in this category affect the replication of data to other Accumulo instances.
\n-Amount of time to wait before the replication work loop begins in the master.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 0s
Maximum size of data to send in a replication message
\n-Type: MEMORY
\n-Zookeeper Mutable: yes
\n-Default Value: 64M
Upper bound of the number of files queued for replication
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 1000
Name of this cluster with respect to replication. Used to identify this instance from other peers
\n-Type: STRING
\n-Zookeeper Mutable: yes
\n-Default Value: empty
Listen port used by thrift service in tserver listening for replication
\n-Type: PORT
\n-Zookeeper Mutable: yes
\n-Default Value: 10002
Minimum number of threads for replication
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 1
The time between adjustments of the replication thread pool.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 30s
Amount of time for a single replication RPC call to last before failing the attempt. See replication.work.attempts.
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 2m
The sampling percentage to use for replication traces
\n-Type: FRACTION
\n-Zookeeper Mutable: yes
\n-Default Value: 0.1
Replication WorkAssigner implementation to use
\n-Type: CLASSNAME
\n-Zookeeper Mutable: yes
\n-Default Value: org.apache.accumulo.master.replication.UnorderedWorkAssigner
Amount of time to sleep between replication work assignment
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 30s
Number of attempts to try to replicate some data before giving up and letting it naturally be retried later
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 10
Amount of time to wait before first checking for replication work, not useful outside of tests
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 0s
Amount of time to wait before re-checking for replication work, not useful outside of tests
\n-Type: TIMEDURATION
\n-Zookeeper Mutable: yes
\n-Default Value: 0s
Size of the threadpool that each tabletserver devotes to replicating data
\n-Type: COUNT
\n-Zookeeper Mutable: yes
\n-Default Value: 4
Properties in this category control what systems data can be replicated to
\n-The username to provide when authenticating with the given peer
\n-The password to provide when authenticating with the given peer
\n-The keytab to use when authenticating with the given peer
\n-A non-negative integer optionally followed by a unit of time (whitespace disallowed), as in 30s.\n-If no unit of time is specified, seconds are assumed. Valid units are 'ms', 's', 'm', 'h' for milliseconds, seconds, minutes, and hours.\n-Examples of valid durations are '600', '30s', '45m', '30000ms', '3d', and '1h'.\n-Examples of invalid durations are '1w', '1h30m', '1s 200ms', 'ms', '', and 'a'.\n-Unless otherwise stated, the max value for the duration represented in milliseconds is 9223372036854775807
\n-A positive integer optionally followed by a unit of memory (whitespace disallowed), as in 2G.\n-If no unit is specified, bytes are assumed. Valid units are 'B', 'K', 'M', 'G', for bytes, kilobytes, megabytes, and gigabytes.\n-Examples of valid memories are '1024', '20B', '100K', '1500M', '2G'.\n-Examples of invalid memories are '1M500K', '1M 2K', '1MB', '1.5G', '1,024K', '', and 'a'.\n-Unless otherwise stated, the max value for the memory represented in bytes is 9223372036854775807
\n-A comma-separated list of hostnames or ip addresses, with optional port numbers.\n-Examples of valid host lists are 'localhost:2000,www.example.com,10.10.1.1:500' and 'localhost'.\n-Examples of invalid host lists are '', ':1000', and 'localhost:80000'
\n-An positive integer in the range 1024-65535 (not already in use or specified elsewhere in the configuration),\n-zero to indicate any open ephemeral port, or a range of positive integers specified as M-N
\n-A non-negative integer in the range of 0-2147483647
\n-A floating point number that represents either a fraction or, if suffixed with the '%' character, a percentage.\n-Examples of valid fractions/percentages are '10', '1000%', '0.05', '5%', '0.2%', '0.0005'.\n-Examples of invalid fractions/percentages are '', '10 percent', 'Hulk Hogan'
\n-A string that represents a filesystem path, which can be either relative or absolute to some directory. The filesystem depends on the property. The following environment variables will be substituted: [ACCUMULO_HOME, ACCUMULO_CONF_DIR]
\n-An absolute filesystem path. The filesystem depends on the property. This is the same as path, but enforces that its root is explicitly specified.
\n-A fully qualified java class name representing a class on the classpath.\n-An example is 'java.lang.String', rather than 'String'
\n-A list of fully qualified java class names representing classes on the classpath.\n-An example is 'java.lang.String', rather than 'String'
\n-One of 'none', 'log', 'flush' or 'sync'.
\n-One of 'none', 'flush', or 'compact'.
\n-An arbitrary string of characters whose format is unspecified and interpreted based on the context of the property to which it applies.
\n-Has a value of either 'true' or 'false' (case-insensitive)
\n-A valid URI
\n-Unresolved directive in accumulo_user_manual.asciidoc - include::appendices/config.txt[]
\n