Re: [VOTE] Release Apache Cassandra 3.0.14
+1 On 2017-06-19 22:37, Michael Shuler wrote: I propose the following artifacts for release as 3.0.14. sha1: f3e38cb638113c2a23855a104d6082da5bc10ddb Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.14-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1143/org/apache/cassandra/apache-cassandra/3.0.14/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-1143/ The Debian and RPM packages are available here: http://people.apache.org/~mshuler The vote will be open for 72 hours (longer if needed). [1]: (CHANGES.txt) https://goo.gl/VdkHQH [2]: (NEWS.txt) https://goo.gl/Qkknas - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: Repairing question
> This attribute seems to be only modified when executing "nodetool repair > [keyspace] [table]", but not when executing with other options like > --in-local-dc or --pr. This is correct behavior because this metric actually represent the percentage of SSTables incrementally repaired - and marked as repaired - which doesn't happen when you execute a non-incremental repair (--full, --in-local-dc, --pr). When you perform a non-incremental repair data is repaired but not marked as repaired since this require anti-compaction to be run. Actually this "percent repaired" display name is a bit misleading, since it sounds like data needs to be repaired while you could be running non-incremental repairs and still have data 100% repaired, so we should probably open a ticket to rename that to "Percent incrementally repaired" or similar. 2017-06-22 14:38 GMT-05:00 Javier Canillas : > Hi, > > I have been thinking about scheduling a daily routine to force repairs on a > cluster to maintain its health. > > I saw that by running a nodetool tablestats [keyspace] there is an attribute > called "Percent repaired" that show the percentage of data repaired on the > each table. > > This attribute seems to be only modified when executing "nodetool repair > [keyspace] [table]", but not when executing with other options like > --in-local-dc or --pr. > > My main concern is about building the whole MERKLE tree for a big table. I > have also check to repair by token ranges, but this also seems not to modify > this attribute of the table. > > Is this an expected behavior? Or there is something missing on the code that > needs to be fixed? > > My "maintenance" script would be calling nodetool tablestats per each > keyspace that has replication_factor > 0 to check for the value of the > "Percent repaired" of each table and, in case it is below some threshold, I > would execute a repair on it. > > Any ideas? > > Thanks in advance. > > Javier. - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: Repairing question
Paulo, Thanks for your explanation. 2017-06-22 17:30 GMT-03:00 Paulo Motta : > > This attribute seems to be only modified when executing "nodetool repair > [keyspace] [table]", but not when executing with other options like > --in-local-dc or --pr. > > This is correct behavior because this metric actually represent the > percentage of SSTables incrementally repaired - and marked as repaired > - which doesn't happen when you execute a non-incremental repair > (--full, --in-local-dc, --pr). When you perform a non-incremental > repair data is repaired but not marked as repaired since this require > anti-compaction to be run. > > Actually this "percent repaired" display name is a bit misleading, > since it sounds like data needs to be repaired while you could be > running non-incremental repairs and still have data 100% repaired, so > we should probably open a ticket to rename that to "Percent > incrementally repaired" or similar. > > > 2017-06-22 14:38 GMT-05:00 Javier Canillas : > > Hi, > > > > I have been thinking about scheduling a daily routine to force repairs > on a > > cluster to maintain its health. > > > > I saw that by running a nodetool tablestats [keyspace] there is an > attribute > > called "Percent repaired" that show the percentage of data repaired on > the > > each table. > > > > This attribute seems to be only modified when executing "nodetool repair > > [keyspace] [table]", but not when executing with other options like > > --in-local-dc or --pr. > > > > My main concern is about building the whole MERKLE tree for a big table. > I > > have also check to repair by token ranges, but this also seems not to > modify > > this attribute of the table. > > > > Is this an expected behavior? Or there is something missing on the code > that > > needs to be fixed? > > > > My "maintenance" script would be calling nodetool tablestats per each > > keyspace that has replication_factor > 0 to check for the value of the > > "Percent repaired" of each table and, in case it is below some > threshold, I > > would execute a repair on it. > > > > Any ideas? > > > > Thanks in advance. > > > > Javier. >
