Re: Proposals for releases - 4.0 and beyond
Hi, I do like Sylvain's proposal too. And, from a user perspective, I agree with Kurt that having (at least) 2 "bug fixing only" branches instead of 1 would be great. De :kurt Greaves A : dev@cassandra.apache.org, Date : 19/11/2016 07:42 Objet : Re: Proposals for releases - 4.0 and beyond Option 3 seems the most reasonable and the clearest from a user perspective. The main thing I'd be concerned about with a 6 month cycle would be how short a branch is supported for. Most users will be bound to a specific release for at least 2 years, and we still find bugs in 2.1 2 years since release. The only adjustment I would make would be to support branches for 1.5 - 2 years before EOL.
AUTO : Samuel CARRIERE is out of the office (retour 22/04/2013)
Je suis absent(e) du bureau jusqu'au 22/04/2013 Remarque : ceci est une réponse automatique à votre message "Re: Rename failed while cassandra is starting up" envoyé le 15/04/2013 3:57:50. C'est la seule notification que vous recevrez pendant l'absence de cette personne.
AUTO : Samuel CARRIERE is out of the office (retour 07/08/2013)
Je suis absent(e) du bureau jusqu'au 07/08/2013 Remarque : ceci est une réponse automatique à votre message "wiki bootstrap doc" envoyé le 13/07/2013 2:13:10. C'est la seule notification que vous recevrez pendant l'absence de cette personne.
AUTO : Samuel CARRIERE is out of the office (retour 28/10/2013)
Je suis absent(e) du bureau jusqu'au 28/10/2013 Remarque : ceci est une réponse automatique à votre message "[VOTE] Release Apache Cassandra 2.0.2" envoyé le 22/10/2013 18:59:30. C'est la seule notification que vous recevrez pendant l'absence de cette personne.
AUTO : Samuel CARRIERE is out of the office (retour 25/11/2013)
Je suis absent(e) du bureau jusqu'au 25/11/2013 Remarque : ceci est une réponse automatique à votre message "Lifecycle of paged queries" envoyé le 18/11/2013 21:52:11. C'est la seule notification que vous recevrez pendant l'absence de cette personne.
RE: [VOTE] Release Apache Cassandra 1.2.14
CHANGES.txt * Nodetool upgradesstables includes secondary indexes (CASSANDRA-6589) should be CASSANDRA-6598 instead of CASSANDRA-6589 I think De :Sylvain Lebresne A : "dev@cassandra.apache.org" , Date : 31/01/2014 12:35 Objet : [VOTE] Release Apache Cassandra 1.2.14 I propose the following artifacts for release as 1.2.14. sha1: 6a9314408cbd69ce26c2ba04bf49df7809a911bf Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.14-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1000/org/apache/cassandra/apache-cassandra/1.2.14/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-1000/ 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/MpQunt (CHANGES.txt) [2]: http://goo.gl/VLWyfI (NEWS.txt)
AUTO : Samuel CARRIERE is out of the office (retour 09/03/2014)
Je suis absent(e) du bureau jusqu'au 09/03/2014 Remarque : ceci est une réponse automatique à votre message "[GitHub] cassandra pull request: updated artifacts to strip DOS crlf" envoyé le 04/03/2014 15:51:12. C'est la seule notification que vous recevrez pendant l'absence de cette personne.
AUTO : Samuel CARRIERE is out of the office (retour 05/05/2014)
Je suis absent(e) du bureau jusqu'au 05/05/2014 Remarque : ceci est une réponse automatique à votre message "Re: Request: easy access to local data features" envoyé le 25/04/2014 15:28:55. C'est la seule notification que vous recevrez pendant l'absence de cette personne.
RE: Things that are about 1M big
Hi, This is arena allocation of memtables. See here for more infos : http://www.datastax.com/dev/blog/whats-new-in-cassandra-1-0-performance De :graham sanderson A : dev@cassandra.apache.org, Date : 16/05/2014 14:03 Objet : Things that are about 1M big So just throwing this out there for those for whom this might ring a bell. I?m debugging some CMS memory fragmentation issues on 2.0.5 - and interestingly enough most of the objects giving us promotion failures are of size 131074 (dwords) - GC logging obviously doesn?t say what those are, but I?d wager money they are either 1M big byte arrays, or less likely 256k entry object arrays backing large maps So not strictly critical to solving my problem, but I was wondering if anyone can think of any heap allocated C* objects which are (with no significant changes to standard cassandra config) allocated in 1M chunks. (It would save me scouring the code, or a 9 gig heap dump if I need to figure it out!) Thanks, Graham