Failing tests 2016-10-05
trunk: === testall: 2 failures org.apache.cassandra.service.RemoveTest .testLocalHostId CASSANDRA-9541. org.apache.cassandra.dht.tokenallocator.ReplicationAwareTokenAllocatorTest .testNewClusterWithMurmur3Partitioner This times out every time. Someone should take a look === dtest: All passed! === upgrade: All passed! === novnode: 8 failures Still the 8 paging failures from CASSANDRA-12666. Seriously, someone review this.
[VOTE] Release Apache Cassandra 2.1.16
I propose the following artifacts for release as 2.1.16. sha1: 87034cd05964e64c6c925597279865a40a8c152f Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.16-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1129/org/apache/cassandra/apache-cassandra/2.1.16/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-1129/ The Debian 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/xc7jn6 [2]: (NEWS.txt) https://goo.gl/O0C3Gb
Re: [VOTE] Release Apache Cassandra 2.1.16
+1 On Oct 5, 2016 6:10 PM, "Michael Shuler" wrote: > I propose the following artifacts for release as 2.1.16. > > sha1: 87034cd05964e64c6c925597279865a40a8c152f > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/2.1.16-tentative > Artifacts: > https://repository.apache.org/content/repositories/ > orgapachecassandra-1129/org/apache/cassandra/apache-cassandra/2.1.16/ > Staging repository: > https://repository.apache.org/content/repositories/ > orgapachecassandra-1129/ > > The Debian 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/xc7jn6 > [2]: (NEWS.txt) https://goo.gl/O0C3Gb >
Re: [VOTE] Release Apache Cassandra 2.1.16
+1 On Thu, Oct 6, 2016 at 12:09 PM, Michael Shuler wrote: > I propose the following artifacts for release as 2.1.16. > > sha1: 87034cd05964e64c6c925597279865a40a8c152f > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.16-tentative > Artifacts: > https://repository.apache.org/content/repositories/orgapachecassandra-1129/org/apache/cassandra/apache-cassandra/2.1.16/ > Staging repository: > https://repository.apache.org/content/repositories/orgapachecassandra-1129/ > > The Debian 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/xc7jn6 > [2]: (NEWS.txt) https://goo.gl/O0C3Gb
Re: [VOTE] Release Apache Cassandra 2.1.16
+1 On 2016-10-05 16:09 (-0700), Michael Shuler wrote: > I propose the following artifacts for release as 2.1.16. > > sha1: 87034cd05964e64c6c925597279865a40a8c152f > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.16-tentative > Artifacts: > https://repository.apache.org/content/repositories/orgapachecassandra-1129/org/apache/cassandra/apache-cassandra/2.1.16/ > Staging repository: > https://repository.apache.org/content/repositories/orgapachecassandra-1129/ > > The Debian 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/xc7jn6 > [2]: (NEWS.txt) https://goo.gl/O0C3Gb >
Counter global logical clock
Hi all Developers, Recently I was restoring some sstables by changing their timestamp. But in case of counter It's different there are few things I'd like to ask:- * What is the maximum value of global logical clock? *Long.MAX_VALUE* ? ** what will happen If updates hit this MAX_VALUE value ?* I read rule of merging of counter columns:- - global + global = keep the shard with the highest logical clock - global + local = keep the global one - global + remote = keep the global one - local + local = sum counts (and logical clocks) - local + remote = keep the local one - remote + remote = keep the shard with the highest logical clock So in my case :: ** Can I change to 'set as global and set logical clock to maximum to make sure it always win when merge' ? * How can we modify a counter column so it will always win when merge?* I'm using *ka* sstable version. Thanking You!! Regards, Varun Barala
