Time to roll 1.1.12?
CHANGES: * Remove buggy thrift max message length option (CASSANDRA-5529) * Add retry mechanism to OTC for non-droppable_verbs (CASSANDRA-5393) * Use allocator information to improve memtable memory usage estimate (CASSANDRA-5497) * fsync leveled manifest to avoid corruption (CASSANDRA-5535) * Fix Bound intersection computation (CASSANDRA-5551) * Fix NPE in Pig's widerow mode (CASSANDRA-5488) I'm feeling lucky that we're ready to stick a fork in 1.1. -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Time to roll 1.1.12?
+1 On Tue, May 21, 2013 at 1:59 PM, Jonathan Ellis wrote: > CHANGES: > * Remove buggy thrift max message length option (CASSANDRA-5529) > * Add retry mechanism to OTC for non-droppable_verbs (CASSANDRA-5393) > * Use allocator information to improve memtable memory usage estimate >(CASSANDRA-5497) > * fsync leveled manifest to avoid corruption (CASSANDRA-5535) > * Fix Bound intersection computation (CASSANDRA-5551) > * Fix NPE in Pig's widerow mode (CASSANDRA-5488) > > I'm feeling lucky that we're ready to stick a fork in 1.1. > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder, http://www.datastax.com > @spyced >
Re: Time to roll 1.1.12?
+1 On Tue, May 21, 2013 at 1:43 PM, Brandon Williams wrote: > +1 > > On Tue, May 21, 2013 at 1:59 PM, Jonathan Ellis wrote: > > > CHANGES: > > * Remove buggy thrift max message length option (CASSANDRA-5529) > > * Add retry mechanism to OTC for non-droppable_verbs (CASSANDRA-5393) > > * Use allocator information to improve memtable memory usage estimate > >(CASSANDRA-5497) > > * fsync leveled manifest to avoid corruption (CASSANDRA-5535) > > * Fix Bound intersection computation (CASSANDRA-5551) > > * Fix NPE in Pig's widerow mode (CASSANDRA-5488) > > > > I'm feeling lucky that we're ready to stick a fork in 1.1. > > > > -- > > Jonathan Ellis > > Project Chair, Apache Cassandra > > co-founder, http://www.datastax.com > > @spyced > > >
Re: Time to roll 1.1.12?
+1 on the release, and +1 on the fork sticking :) On Tue, May 21, 2013 at 2:59 PM, Jonathan Ellis wrote: > CHANGES: > * Remove buggy thrift max message length option (CASSANDRA-5529) > * Add retry mechanism to OTC for non-droppable_verbs (CASSANDRA-5393) > * Use allocator information to improve memtable memory usage estimate >(CASSANDRA-5497) > * fsync leveled manifest to avoid corruption (CASSANDRA-5535) > * Fix Bound intersection computation (CASSANDRA-5551) > * Fix NPE in Pig's widerow mode (CASSANDRA-5488) > > I'm feeling lucky that we're ready to stick a fork in 1.1. > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder, http://www.datastax.com > @spyced >
Re: Time to roll 1.1.12?
+1 On Tue, May 21, 2013 at 2:10 PM, Carl Yeksigian wrote: > +1 on the release, and +1 on the fork sticking :) > > > On Tue, May 21, 2013 at 2:59 PM, Jonathan Ellis wrote: > > > CHANGES: > > * Remove buggy thrift max message length option (CASSANDRA-5529) > > * Add retry mechanism to OTC for non-droppable_verbs (CASSANDRA-5393) > > * Use allocator information to improve memtable memory usage estimate > >(CASSANDRA-5497) > > * fsync leveled manifest to avoid corruption (CASSANDRA-5535) > > * Fix Bound intersection computation (CASSANDRA-5551) > > * Fix NPE in Pig's widerow mode (CASSANDRA-5488) > > > > I'm feeling lucky that we're ready to stick a fork in 1.1. > > > > -- > > Jonathan Ellis > > Project Chair, Apache Cassandra > > co-founder, http://www.datastax.com > > @spyced > > >
Re: Time to roll 1.1.12?
* fsync leveled manifest to avoid corruption (CASSANDRA-5535) you sure that this does not have performance impact? most filesystems sync all their data not just one file. write to .new file and then do rename.
cassie
http://wiki.apache.org/cassandra/ClientOptionsThrift add cassie - https://github.com/twitter/cassie
Re: Time to roll 1.1.12?
+1. I'll cook up the artifacts and call for a vote. On Wed, May 22, 2013 at 7:35 AM, Radim Kolar wrote: > >* fsync leveled manifest to avoid corruption (CASSANDRA-5535) >> > you sure that this does not have performance impact? most filesystems sync > all their data not just one file. write to .new file and then do rename. >