From 9f9eb47d3c5d764ac96822c84c6cefdd4c2c1813 Mon Sep 17 00:00:00 2001 From: Mike Miller Date: Fri, 9 Sep 2016 11:41:41 -0400 Subject: [PATCH] Corrected chapter numbering in 1.6 manual --- 1.6/accumulo_user_manual.html | 106 +++++++++++++++++----------------- 1 file changed, 53 insertions(+), 53 deletions(-) diff --git a/1.6/accumulo_user_manual.html b/1.6/accumulo_user_manual.html index fa4faa43b65..f36e4d16062 100644 --- a/1.6/accumulo_user_manual.html +++ b/1.6/accumulo_user_manual.html @@ -4911,7 +4911,7 @@

12.12. Migrating Accumulo from non-HA Name
-

13. Multi-Volume Installations

+

14. Multi-Volume Installations

This is an advanced configuration setting for very large clusters @@ -4994,10 +4994,10 @@

13. Multi-Volume Installations

-

14. Troubleshooting

+

15. Troubleshooting

-

14.1. Logs

+

15.1. Logs

Q: The tablet server does not seem to be running!? What happened?

@@ -5025,7 +5025,7 @@

14.1. Logs

-

14.2. Monitor

+

15.2. Monitor

Q: Accumulo is not working, what’s wrong?

@@ -5083,7 +5083,7 @@

14.2. Monitor

-

14.3. HDFS

+

15.3. HDFS

Accumulo reads and writes to the Hadoop Distributed File System. Accumulo needs this file system available at all times for normal operations.

@@ -5131,7 +5131,7 @@

14.3. HDFS

-

14.4. Zookeeper

+

15.4. Zookeeper

Q: accumulo init is hanging. It says something about talking to zookeeper.

@@ -5213,7 +5213,7 @@

14.4. Zookeeper

zookeeper.

-

14.4.1. Keeping the tablet server lock

+

15.4.1. Keeping the tablet server lock

Q: My tablet server lost its lock. Why?

@@ -5298,7 +5298,7 @@

14.4.1. Keeping the tablet server lock<

-

14.5. Tools

+

15.5. Tools

The accumulo script can be used to run classes from the command line. This section shows how a few of the utilities work, but there are many @@ -5532,7 +5532,7 @@

14.5. Tools

-

14.6. System Metadata Tables

+

15.6. System Metadata Tables

Accumulo tracks information about tables in metadata tables. The metadata for most tables is contained within the metadata table in the accumulo namespace, @@ -5679,7 +5679,7 @@

14.6. System Metadata Tables

-

14.7. Simple System Recovery

+

15.7. Simple System Recovery

Q: One of my Accumulo processes died. How do I bring it back?

@@ -5726,9 +5726,9 @@

14.7. Simple System Recovery

-

14.8. Advanced System Recovery

+

15.8. Advanced System Recovery

-

14.8.1. HDFS Failure

+

15.8.1. HDFS Failure

Q: I had disasterous HDFS failure. After bringing everything back up, several tablets refuse to go online.

@@ -5913,7 +5913,7 @@

14.8.1. HDFS Failure

-

14.8.2. ZooKeeper Failure

+

15.8.2. ZooKeeper Failure

Q: I lost my ZooKeeper quorum (hardware failure), but HDFS is still intact. How can I recover my Accumulo instance?

@@ -5985,7 +5985,7 @@

14.8.2. ZooKeeper Failure

-

14.9. Upgrade Issues

+

15.9. Upgrade Issues

Q: I upgrade from 1.4 to 1.5 to 1.6 but still have some WAL files on local disk. Do I have any way to recover them?

@@ -6003,7 +6003,7 @@

14.9. Upgrade Issues

-

14.10. File Naming Conventions

+

15.10. File Naming Conventions

Q: Why are files named like they are? Why do some start with C and others with F?

@@ -6056,10 +6056,10 @@

14.10. File Naming Conventions

-

15. Appendix A: Configuration Management

+

16. Appendix A: Configuration Management

-

15.1. Configuration Overview

+

16.1. Configuration Overview

All accumulo properties have a default value in the source code. Properties can also be set in accumulo-site.xml and in zookeeper on per-table or system-wide basis. If properties are set in more than one location, @@ -6067,7 +6067,7 @@

15.1. Configuration Overview

below (from highest to lowest):

-

15.1.1. Zookeeper table properties

+

16.1.1. Zookeeper table properties

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

@@ -6081,7 +6081,7 @@

15.1.1. Zookeeper table properties

-

15.1.2. Zookeeper system properties

+

16.1.2. Zookeeper system properties

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:

@@ -6098,7 +6098,7 @@

15.1.2. Zookeeper system properties

-

15.1.3. accumulo-site.xml

+

16.1.3. accumulo-site.xml

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.

@@ -6107,7 +6107,7 @@

15.1.3. accumulo-site.xml

-

15.1.4. Default Values

+

16.1.4. Default Values

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.

@@ -6117,7 +6117,7 @@

15.1.4. Default Values

-

15.2. Configuration in the Shell

+

16.2. Configuration in the Shell

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:

@@ -6160,13 +6160,13 @@

15.2. Configuration in the Shell

-

15.3. Available Properties

+

16.3. Available Properties

Jump to: rpc.* | instance.* | general.* | master.* | tserver.* | logger.* | gc.* | monitor.* | trace.* | trace.token.property.* | table.* | table.constraint.* | table.iterator.* | table.group.* | table.majc.compaction.strategy.opts.* | general.vfs.context.classpath.*

-

15.3.1. rpc.*

+

16.3.1. rpc.*

Properties in this category related to the configuration of SSL keys for RPC. See also instance.ssl.enabled

@@ -6249,7 +6249,7 @@
rpc.useJsse
-

15.3.2. instance.*

+

16.3.2. instance.*

Properties in this category must be consistent throughout a cloud. This is enforced and servers won’t be able to communicate if these differ.

@@ -6387,7 +6387,7 @@
instance.zookeeper.timeout
-

15.3.3. general.*

+

16.3.3. general.*

Properties in this category affect the behavior of accumulo overall, but do not have to be consistent throughout a cloud.

@@ -6511,7 +6511,7 @@
general.vfs.classpaths
-

15.3.4. master.*

+

16.3.4. master.*

Properties in this category affect the behavior of the master server

@@ -6660,7 +6660,7 @@
master.walog.closer.implementation<
-

15.3.5. tserver.*

+

16.3.5. tserver.*

Properties in this category affect the behavior of the tablet servers

@@ -7117,7 +7117,7 @@
tserver.workq.threads
-

15.3.6. logger.*

+

16.3.6. logger.*

Properties in this category affect the behavior of the write-ahead logger servers

@@ -7134,7 +7134,7 @@
logger.dir.walog
-

15.3.7. gc.*

+

16.3.7. gc.*

Properties in this category affect the behavior of the accumulo garbage collector.

@@ -7195,7 +7195,7 @@
gc.trash.ignore
-

15.3.8. monitor.*

+

16.3.8. monitor.*

Properties in this category affect the behavior of the monitor web server.

@@ -7267,7 +7267,7 @@
monitor.port.log4j
-

15.3.9. trace.*

+

16.3.9. trace.*

Properties in this category affect the behavior of distributed tracing.

@@ -7328,13 +7328,13 @@
trace.user
-

15.3.10. trace.token.property.*

+

16.3.10. trace.token.property.*

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.

-

15.3.11. table.*

+

16.3.11. table.*

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.

@@ -7672,7 +7672,7 @@
table.walog.enabled
-

15.3.12. table.constraint.*

+

16.3.12. table.constraint.*

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. For example: @@ -7682,7 +7682,7 @@

15.3.12. table.constraint.*

-

15.3.13. table.iterator.*

+

16.3.13. table.iterator.*

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: table.iterator.scan.vers = 10,org.apache.accumulo.core.iterators.VersioningIterator @@ -7691,7 +7691,7 @@

15.3.13. table.iterator.*

-

15.3.14. table.group.*

+

16.3.14. table.group.*

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. 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. @@ -7699,22 +7699,22 @@

15.3.14. table.group.*

-

15.3.15. table.majc.compaction.strategy.opts.*

+

16.3.15. table.majc.compaction.strategy.opts.*

Properties in this category are used to configure the compaction strategy.

-

15.3.16. general.vfs.context.classpath.*

+

16.3.16. general.vfs.context.classpath.*

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 nameIf delegation is not specified, it defaults to loading from parent classloader first.

-

15.4. Property Types

+

16.4. Property Types

-

15.4.1. duration

+

16.4.1. duration

A non-negative integer optionally followed by a unit of time (whitespace disallowed), as in 30s. If no unit of time is specified, seconds are assumed. Valid units are ms, s, m, h for milliseconds, seconds, minutes, and hours. @@ -7724,13 +7724,13 @@

15.4.1. duration

-

15.4.2. date/time

+

16.4.2. date/time

A date/time string in the format: YYYYMMDDhhmmssTTT where TTT is the 3 character time zone

-

15.4.3. memory

+

16.4.3. memory

A positive integer optionally followed by a unit of memory (whitespace disallowed), as in 2G. If no unit is specified, bytes are assumed. Valid units are B, K, M, G, for bytes, kilobytes, megabytes, and gigabytes. @@ -7740,7 +7740,7 @@

15.4.3. memory

-

15.4.4. host list

+

16.4.4. host list

A comma-separated list of hostnames or ip addresses, with optional port numbers. Examples of valid host lists are localhost:2000,www.example.com,10.10.1.1:500 and localhost. @@ -7748,19 +7748,19 @@

15.4.4. host list

-

15.4.5. port

+

16.4.5. port

An positive integer in the range 1024-65535, not already in use or specified elsewhere in the configuration

-

15.4.6. count

+

16.4.6. count

A non-negative integer in the range of 0-2147483647

-

15.4.7. fraction/percentage

+

16.4.7. fraction/percentage

A floating point number that represents either a fraction or, if suffixed with the % character, a percentage. Examples of valid fractions/percentages are 10, 1000%, 0.05, 5%, 0.2%, 0.0005. @@ -7768,38 +7768,38 @@

15.4.7. fraction/percentage

-

15.4.8. path

+

16.4.8. path

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]

-

15.4.9. absolute path

+

16.4.9. absolute path

An absolute filesystem path. The filesystem depends on the property. This is the same as path, but enforces that its root is explicitly specified.

-

15.4.10. java class

+

16.4.10. java class

A fully qualified java class name representing a class on the classpath. An example is java.lang.String, rather than String

-

15.4.11. string

+

16.4.11. string

An arbitrary string of characters whose format is unspecified and interpreted based on the context of the property to which it applies.

-

15.4.12. boolean

+

16.4.12. boolean

Has a value of either true or false

-

15.4.13. uri

+

16.4.13. uri

A valid URI