[docs] Fix bad subsection and relocate "Disk Issues" section The section on rebuilding a Kudu filesystem layout was improperly a subsection of the majority recovery section.
The performance section of the troubleshooting page had a "Disk Issues" section describing a failure to startup due to a partial Kudu fs or a non-empty initial set of fs directories. I moved this to be a child section of the "Startup Errors" section. I changed the title as well, but left the id the same so old links will still work. Change-Id: Ia2e2abc1359e0a0fd968fe1a85073714af1ee695 Reviewed-on: http://gerrit.cloudera.org:8080/9816 Tested-by: Kudu Jenkins Reviewed-by: Adar Dembo <[email protected]> Project: http://git-wip-us.apache.org/repos/asf/kudu/repo Commit: http://git-wip-us.apache.org/repos/asf/kudu/commit/43bc1abe Tree: http://git-wip-us.apache.org/repos/asf/kudu/tree/43bc1abe Diff: http://git-wip-us.apache.org/repos/asf/kudu/diff/43bc1abe Branch: refs/heads/master Commit: 43bc1abe282c5cab5b6e9956b0cae98750ec7cd3 Parents: 8728dfc Author: Will Berkeley <[email protected]> Authored: Mon Mar 26 22:06:22 2018 -0700 Committer: Will Berkeley <[email protected]> Committed: Tue Mar 27 17:18:10 2018 +0000 ---------------------------------------------------------------------- docs/administration.adoc | 2 +- docs/troubleshooting.adoc | 32 ++++++++++++++++---------------- 2 files changed, 17 insertions(+), 17 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/kudu/blob/43bc1abe/docs/administration.adoc ---------------------------------------------------------------------- diff --git a/docs/administration.adoc b/docs/administration.adoc index cdc8128..6cfd4df 100644 --- a/docs/administration.adoc +++ b/docs/administration.adoc @@ -876,7 +876,7 @@ replicas will be tombstoned by the master, causing their remaining data to be deleted. [[rebuilding_kudu]] -==== Rebuilding a Kudu Filesystem Layout +=== Rebuilding a Kudu Filesystem Layout In the event that critical files are lost, i.e. WALs or tablet-specific metadata, all Kudu directories on the server must be deleted and rebuilt to http://git-wip-us.apache.org/repos/asf/kudu/blob/43bc1abe/docs/troubleshooting.adoc ---------------------------------------------------------------------- diff --git a/docs/troubleshooting.adoc b/docs/troubleshooting.adoc index 73cd530..ef6ad15 100644 --- a/docs/troubleshooting.adoc +++ b/docs/troubleshooting.adoc @@ -66,6 +66,22 @@ manager. WARNING: The file block manager is known to scale and perform poorly, and should only be used for small-scale evaluation and development. +[[disk_issues]] +=== Already present: FS layout already exists + +When Kudu starts, it checks each configured data directory, expecting either for all to be +initialized or for all to be empty. If a server fails to start with a log message like + +---- +Check failed: _s.ok() Bad status: Already present: FS layout already exists; not overwriting existing layout: FSManager roots already exist: /data0/kudu/data +---- + +then this precondition has failed. This could be because Kudu was configured with non-empty data +directories on first startup, or because a previously-running, healthy Kudu process was restarted +and at least one data directory was deleted or is somehow corrupted, perhaps because of a disk +error. If in the latter situation, consult the +link:administration.html#change_dir_config[Changing Directory Configurations] documentation. + [[ntp]] === NTP Clock Synchronization @@ -531,22 +547,6 @@ TIP: Heap samples contain only summary information about allocations and do not _data_ from the heap. It is safe to share heap samples in public without fear of exposing confidential or sensitive data. -[[disk_issues]] -=== Disk Issues - -When Kudu starts, it checks each configured data directory, expecting either for all to be -initialized or for all to be empty. If a server fails to start with a log message like - ----- -Check failed: _s.ok() Bad status: Already present: FS layout already exists; not overwriting existing layout: FSManager roots already exist: /data0/kudu/data ----- - -then this precondition has failed. This could be because Kudu was configured with non-empty data -directories on first startup, or because a previously-running, healthy Kudu process was restarted -and at least one data directory was deleted or is somehow corrupted, perhaps because of a disk -error. If in the latter situation, consult the -link:administration.html#change_dir_config[Changing Directory Configurations] documentation. - == Issues using Kudu [[hive_handler]]
