Re: [VOTE CLOSED] Release Apache Cassandra 1.2.13 (Strike 2)
Well. I feel stupid now :) On Dec 16, 2013, at 10:49 PM, Sylvain Lebresne sylv...@datastax.com wrote: On Tue, Dec 17, 2013 at 7:43 AM, Michael Kjellman mkjell...@barracuda.comwrote: I¹ve also seen behavior where prepared statements are lost during a rolling restart..haven¹t had a chance to debug/git bisect yet. Anyone else seen anything similar? I'd be somewhat surprised if someone hasn't. We don't persists prepared statements over node restart. it's supposed to be the client job to re-prepare statements when a node is restarted. -- Sylvain On 12/16/13, 10:40 PM, Sylvain Lebresne sylv...@datastax.com wrote: Alright, this vote is thus close. I'll re-roll when we've made sure we fixed all the regressions so we'll see when that is. -- Sylvain On Tue, Dec 17, 2013 at 1:01 AM, Brandon Williams dri...@gmail.com wrote: Or rather: https://issues.apache.org/jira/browse/CASSANDRA-6493 I would still prefer a 24h vote after resolution though. On Mon, Dec 16, 2013 at 5:56 PM, Brandon Williams dri...@gmail.com wrote: Changing to -1 as https://issues.apache.org/jira/browse/CASSANDRA-6488seems to be a real problem. On Mon, Dec 16, 2013 at 12:12 PM, Brandon Williams dri...@gmail.com wrote: +1 On Mon, Dec 16, 2013 at 3:38 AM, Sylvain Lebresne sylv...@datastax.com wrote: So now that CASSANDRA-6485 has been committed, I propose the following artifacts for release as 1.2.13. sha1: 4be9e6720d9f94a83aa42153c3e71ae1e557d2d9 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/ tags/1.2.13-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-050 /org/apache/cassandra/apache-cassandra/1.2.13/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-050 / The artifacts as well as the debian package are also available here: http://people.apache.org/~slebresne/ Since it is a re-roll, I propose an expedited vote so the vote will be open for 24 hours (but longer if needed). [1]: http://goo.gl/j4xUAK (CHANGES.txt) [2]: http://goo.gl/iu5Og9 (NEWS.txt) === Find out how eSigning generates significant financial benefit. Read the Barracuda SignNow ROI whitepaper at https://signnow.com/l/business/esignature_roi === Find out how eSigning generates significant financial benefit. Read the Barracuda SignNow ROI whitepaper at https://signnow.com/l/business/esignature_roi
[VOTE CLOSED] Release Apache Cassandra 1.2.13 (Strike 2)
Alright, this vote is thus close. I'll re-roll when we've made sure we fixed all the regressions so we'll see when that is. -- Sylvain On Tue, Dec 17, 2013 at 1:01 AM, Brandon Williams dri...@gmail.com wrote: Or rather: https://issues.apache.org/jira/browse/CASSANDRA-6493 I would still prefer a 24h vote after resolution though. On Mon, Dec 16, 2013 at 5:56 PM, Brandon Williams dri...@gmail.com wrote: Changing to -1 as https://issues.apache.org/jira/browse/CASSANDRA-6488seems to be a real problem. On Mon, Dec 16, 2013 at 12:12 PM, Brandon Williams dri...@gmail.com wrote: +1 On Mon, Dec 16, 2013 at 3:38 AM, Sylvain Lebresne sylv...@datastax.com wrote: So now that CASSANDRA-6485 has been committed, I propose the following artifacts for release as 1.2.13. sha1: 4be9e6720d9f94a83aa42153c3e71ae1e557d2d9 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.13-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-050/org/apache/cassandra/apache-cassandra/1.2.13/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-050/ The artifacts as well as the debian package are also available here: http://people.apache.org/~slebresne/ Since it is a re-roll, I propose an expedited vote so the vote will be open for 24 hours (but longer if needed). [1]: http://goo.gl/j4xUAK (CHANGES.txt) [2]: http://goo.gl/iu5Og9 (NEWS.txt)
Re: [VOTE CLOSED] Release Apache Cassandra 1.2.13 (Strike 2)
I¹ve also seen behavior where prepared statements are lost during a rolling restart..haven¹t had a chance to debug/git bisect yet. Anyone else seen anything similar? On 12/16/13, 10:40 PM, Sylvain Lebresne sylv...@datastax.com wrote: Alright, this vote is thus close. I'll re-roll when we've made sure we fixed all the regressions so we'll see when that is. -- Sylvain On Tue, Dec 17, 2013 at 1:01 AM, Brandon Williams dri...@gmail.com wrote: Or rather: https://issues.apache.org/jira/browse/CASSANDRA-6493 I would still prefer a 24h vote after resolution though. On Mon, Dec 16, 2013 at 5:56 PM, Brandon Williams dri...@gmail.com wrote: Changing to -1 as https://issues.apache.org/jira/browse/CASSANDRA-6488seems to be a real problem. On Mon, Dec 16, 2013 at 12:12 PM, Brandon Williams dri...@gmail.com wrote: +1 On Mon, Dec 16, 2013 at 3:38 AM, Sylvain Lebresne sylv...@datastax.com wrote: So now that CASSANDRA-6485 has been committed, I propose the following artifacts for release as 1.2.13. sha1: 4be9e6720d9f94a83aa42153c3e71ae1e557d2d9 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/ tags/1.2.13-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-050 /org/apache/cassandra/apache-cassandra/1.2.13/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-050 / The artifacts as well as the debian package are also available here: http://people.apache.org/~slebresne/ Since it is a re-roll, I propose an expedited vote so the vote will be open for 24 hours (but longer if needed). [1]: http://goo.gl/j4xUAK (CHANGES.txt) [2]: http://goo.gl/iu5Og9 (NEWS.txt) === Find out how eSigning generates significant financial benefit. Read the Barracuda SignNow ROI whitepaper at https://signnow.com/l/business/esignature_roi
Re: [VOTE CLOSED] Release Apache Cassandra 1.2.13 (Strike 2)
On Tue, Dec 17, 2013 at 7:43 AM, Michael Kjellman mkjell...@barracuda.comwrote: I¹ve also seen behavior where prepared statements are lost during a rolling restart..haven¹t had a chance to debug/git bisect yet. Anyone else seen anything similar? I'd be somewhat surprised if someone hasn't. We don't persists prepared statements over node restart. it's supposed to be the client job to re-prepare statements when a node is restarted. -- Sylvain On 12/16/13, 10:40 PM, Sylvain Lebresne sylv...@datastax.com wrote: Alright, this vote is thus close. I'll re-roll when we've made sure we fixed all the regressions so we'll see when that is. -- Sylvain On Tue, Dec 17, 2013 at 1:01 AM, Brandon Williams dri...@gmail.com wrote: Or rather: https://issues.apache.org/jira/browse/CASSANDRA-6493 I would still prefer a 24h vote after resolution though. On Mon, Dec 16, 2013 at 5:56 PM, Brandon Williams dri...@gmail.com wrote: Changing to -1 as https://issues.apache.org/jira/browse/CASSANDRA-6488seems to be a real problem. On Mon, Dec 16, 2013 at 12:12 PM, Brandon Williams dri...@gmail.com wrote: +1 On Mon, Dec 16, 2013 at 3:38 AM, Sylvain Lebresne sylv...@datastax.com wrote: So now that CASSANDRA-6485 has been committed, I propose the following artifacts for release as 1.2.13. sha1: 4be9e6720d9f94a83aa42153c3e71ae1e557d2d9 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/ tags/1.2.13-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-050 /org/apache/cassandra/apache-cassandra/1.2.13/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-050 / The artifacts as well as the debian package are also available here: http://people.apache.org/~slebresne/ Since it is a re-roll, I propose an expedited vote so the vote will be open for 24 hours (but longer if needed). [1]: http://goo.gl/j4xUAK (CHANGES.txt) [2]: http://goo.gl/iu5Og9 (NEWS.txt) === Find out how eSigning generates significant financial benefit. Read the Barracuda SignNow ROI whitepaper at https://signnow.com/l/business/esignature_roi
