I know non members aren¹t supposed to comment on these votes, but I was actually throwing 1.2.6 Strike 2ish into production when 3/4 of the way thru I got Jason¹s email as I was debugging Gossip issues across the cluster. It didn¹t appear to just break repair, but it also broke Gossip (makes since given the scope of the patch). gossipinfo showed all nodes as normal for what it¹s worth, but it required a complete cluster shutdown to get rid of the bad state where some nodes believed other nodes were down as it continued to propagate around the ring. that¹s life on the bleeding edge. :(
I built the equivalent of what Sylvan proposed here and things are running smoothly for what it¹s worth, so +1. -michael On 6/25/13, 2:58 AM, "Carl Yeksigian" <c...@yeksigian.com> wrote: >+1 >On Jun 25, 2013 10:42 AM, "Sylvain Lebresne" <sylv...@datastax.com> wrote: > >> After having reverted CASSANDRA-5665, I propose the following artifacts >>for >> release as 1.2.6. >> >> sha1: a6ca5d496facf79c187310e81b3eeba3e6bc4b43 >> Git: >> >> >>http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/ >>tags/1.2.6-tentative >> Artifacts: >> >> >>https://repository.apache.org/content/repositories/orgapachecassandra-068 >>/org/apache/cassandra/apache-cassandra/1.2.6/ >> Staging repository: >> >>https://repository.apache.org/content/repositories/orgapachecassandra-068 >>/ >> >> The artifacts as well as the debian package are also available here: >> http://people.apache.org/~slebresne/ >> >> Since that release has already received quite a bit of testing, I >>propose >> to do >> a short vote period and so the vote will be open for 24 hours (but >>longer >> if >> needed). >> >> [1]: http://goo.gl/8Ih7f (CHANGES.txt) >> [2]: http://goo.gl/nFiZc (NEWS.txt) >>
