Repository: cassandra Updated Branches: refs/heads/cassandra-2.1 4a6525655 -> 3ac261431 refs/heads/trunk 3e91cb6d7 -> 49dd289ed
emphasize using sstablerepairedset with LCS Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/3ac26143 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/3ac26143 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/3ac26143 Branch: refs/heads/cassandra-2.1 Commit: 3ac26143107189d7329f7638c67d1ab78c412e7b Parents: 4a65256 Author: Jonathan Ellis <jbel...@apache.org> Authored: Wed May 28 12:35:14 2014 +0200 Committer: Jonathan Ellis <jbel...@apache.org> Committed: Wed May 28 12:35:14 2014 +0200 ---------------------------------------------------------------------- NEWS.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/cassandra/blob/3ac26143/NEWS.txt ---------------------------------------------------------------------- diff --git a/NEWS.txt b/NEWS.txt index ff7b98d..ab47576 100644 --- a/NEWS.txt +++ b/NEWS.txt @@ -29,7 +29,9 @@ New features repaired are marked with a timestamp and not included in the next repair session. Use nodetool repair -par -inc to use this feature. A tool to manually mark/unmark sstables as repaired is available in - tools/bin/sstablerepairedset. + tools/bin/sstablerepairedset. This is particularly important when + using LCS, or any data not repaired in your first incremental repair + will be put back in L0. - Bootstrapping now ensures that range movements are consistent, meaning the data for the new node is taken from the node that is no longer a responsible for that range of keys.