+1. I'll cook up the artifacts and call for a vote.
On Wed, May 22, 2013 at 7:35 AM, Radim Kolar h...@filez.com 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
Regarding fork sticking, it'd be great if we knew the scope of this:
https://issues.apache.org/jira/browse/CASSANDRA-5374
which I have a snapshot for, but not yet checked if I can reproduce.
On Tue, May 21, 2013 at 8:59 PM, Jonathan Ellis jbel...@gmail.com wrote:
CHANGES:
* Remove buggy
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
+1
On Tue, May 21, 2013 at 1:43 PM, Brandon Williams dri...@gmail.com wrote:
+1
On Tue, May 21, 2013 at 1:59 PM, Jonathan Ellis jbel...@gmail.com wrote:
CHANGES:
* Remove buggy thrift max message length option (CASSANDRA-5529)
* Add retry mechanism to OTC for non-droppable_verbs
+1
On Tue, May 21, 2013 at 2:10 PM, Carl Yeksigian c...@yeksigian.com wrote:
+1 on the release, and +1 on the fork sticking :)
On Tue, May 21, 2013 at 2:59 PM, Jonathan Ellis jbel...@gmail.com wrote:
CHANGES:
* Remove buggy thrift max message length option (CASSANDRA-5529)
* Add
* 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.
