[VOTE SUCCESS] Release Apache Cassandra 1.1.12 (Strike 2)

[Sylvain Lebresne]

Including my own vote I count 5 binding +1, 2 other +1 and no -1's.
The vote passes.
I'll get the artifact published.

--
Sylvain


On Thu, May 23, 2013 at 9:52 PM, Brandon Williams  wrote:

> +1
>
> On Thu, May 23, 2013 at 3:03 AM, Sylvain Lebresne  >wrote:
>
> > I propose the following artifacts for release as 1.1.12 (now with more
> > #5488 fixes inside).
> >
> > sha1: 2dd73d171068d743befcd445a14751032d232e4e
> > Git:
> >
> >
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.1.12-tentative
> > Artifacts:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-035/org/apache/cassandra/apache-cassandra/1.1.12/
> > Staging repository:
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-035/
> >
> > The artifacts as well as the debian package are also available here:
> > http://people.apache.org/~slebresne/
> >
> > The vote will be open for 72 hours (longer if needed).
> >
> > [1]: http://goo.gl/jm5Hz (CHANGES.txt)
> > [2]: http://goo.gl/AQ3OP (NEWS.txt)
> >
>

manifest fsync

[Radim Kolar]

should be fine, the manifest is not rewritten that often
its rewritten after each sstable flush? databases should do fsync only 
in checkpoint.


Fsync scenario in WAFL is that hard checkpoint is done after predefined 
number of log segments. On checkpoint fsync everything and then write 
checkpoint marker to log, then remove checkpointed logs.