kudu-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ale...@apache.org
Subject [2/4] kudu git commit: release notes: update_dirs and fs_metadata_dir
Date Tue, 13 Mar 2018 00:05:09 GMT
release notes: update_dirs and fs_metadata_dir

This patch adds release notes for support of data dir removal via the
`kudu fs update_dirs` tool and for the configuration of the metadata

Note: These blurbs are taken from the configuration docs.

Change-Id: I87f0857c3e7d9d98865fbb50e5e69b78e03c6fe2
Reviewed-on: http://gerrit.cloudera.org:8080/9581
Reviewed-by: Adar Dembo <adar@cloudera.com>
Reviewed-by: Alexey Serbin <aserbin@cloudera.com>
Tested-by: Andrew Wong <awong@cloudera.com>

Project: http://git-wip-us.apache.org/repos/asf/kudu/repo
Commit: http://git-wip-us.apache.org/repos/asf/kudu/commit/cda07be9
Tree: http://git-wip-us.apache.org/repos/asf/kudu/tree/cda07be9
Diff: http://git-wip-us.apache.org/repos/asf/kudu/diff/cda07be9

Branch: refs/heads/master
Commit: cda07be91bdb9ea537dc19768db54fd345ce7bf0
Parents: 06704ec
Author: Andrew Wong <awong@cloudera.com>
Authored: Mon Mar 12 11:18:57 2018 -0700
Committer: Andrew Wong <awong@cloudera.com>
Committed: Mon Mar 12 23:40:48 2018 +0000

 docs/release_notes.adoc | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/docs/release_notes.adoc b/docs/release_notes.adoc
index c965829..445ae33 100644
--- a/docs/release_notes.adoc
+++ b/docs/release_notes.adoc
@@ -50,6 +50,20 @@
 == New features
+* The `kudu fs update_dirs` tool now supports removing directories. Unless the
+  `--force` flag is specified, Kudu will not allow the removal of a directory
+  across which tablets are configured to spread data. If specified, all tablet
+  replicas configured to use that directory will fail upon starting up and be
+  replicated elsewhere, provided a majority exists elsewhere.
+* Users can use the new `--fs_metadata_dir` to specify the directory in which
+  to place tablet-specific metadata. It is recommended, although not
+  necessary, that this be placed on a high-performance drive with high
+  bandwidth and low latency, e.g. a solid-state drive. If not specified,
+  metadata will be placed in the directory specified by `--fs_wal_dir`, or in
+  the directory specified by the first entry of `--fs_data_dirs` if metadata
+  already exists there from a pre-Kudu 1.7 deployment. Kudu will not
+  automatically move existing metadata based on this configuration.
 == Optimizations and improvements

View raw message