[GitHub] cassandra pull request:

Github user yukim commented on the pull request: https://github.com/apache/cassandra/commit/2384bfb026ef9fb6756a3100ae9653a52b68e43e#commitcomment-15924257 In src/java/org/apache/cassandra/io/sstable/SSTableSimpleIterator.java: In

[VOTE] Release Apache Cassandra 3.3

I propose the following artifacts for release as 3.3. sha1: 5669c6967bbdd540f27aeebf5a2c258bc4defbe3 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.3-tentative Artifacts:

Write latency metric

Hi, I noticed that the write latency metric includes only memtable and rowcache updates, but not sync to a commitlog. I am looking at ColumnFamilyStore.apply() and KeySpace.apply(). Is my understanding correct? Is this an intended design? I guess sync to a commitlog is the most time consuming

Re: [VOTE] Release Apache Cassandra 3.3

+1 On Fri, Feb 5, 2016 at 9:11 PM, Jake Luciani wrote: > I propose the following artifacts for release as 3.3. > > sha1: 5669c6967bbdd540f27aeebf5a2c258bc4defbe3 > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.3-tentative > Artifacts:

Re: [VOTE] Release Apache Cassandra 3.3

+1 On Fri, Feb 5, 2016 at 9:11 PM, Jake Luciani wrote: > I propose the following artifacts for release as 3.3. > > sha1: 5669c6967bbdd540f27aeebf5a2c258bc4defbe3 > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.3-tentative > Artifacts: