[VOTE RESULT] Release Apache Cassandra 3.0.0-beta2
With 5 binding +1 and no -1 the vote passes. I'll publish shortly. On Sun, Sep 6, 2015 at 7:51 AM, Aleksey Yeschenko wrote: > +1 > > -- > AY > > On September 5, 2015 at 01:58:05, Jake Luciani (j...@apache.org) wrote: > > I propose the following artifacts for release as 3.0.0-beta2. > > sha1: 17528910b82391bd834f1fddce4ff7c9b34ad452 > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.0-beta2-tentative > Artifacts: > > https://repository.apache.org/content/repositories/orgapachecassandra-1077/org/apache/cassandra/apache-cassandra/3.0.0-beta2/ > Staging repository: > https://repository.apache.org/content/repositories/orgapachecassandra-1077/ > > The artifacts as well as the debian package are also available here: > http://people.apache.org/~jake > > The vote will be open for 48 hours (longer if needed). > > [1]: http://goo.gl/h3McOM (CHANGES.txt) > [2]: http://goo.gl/WGb5qo (NEWS.txt) > -- http://twitter.com/tjake
[RELEASE] Apache Cassandra 3.0.0-beta2 released
The Cassandra team is pleased to announce the release of Apache Cassandra version 3.0.0-beta2. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source and binary distributions are listed in our download section: http://cassandra.apache.org/download/ This version is a *beta* release[1] on the 3.0 series. As always, please pay attention to the release notes[2] and Let us know[3] if you were to encounter any problem. Enjoy! [1]: http://goo.gl/UWe5yb (CHANGES.txt) [2]: http://goo.gl/xWOSDa (NEWS.txt) [3]: https://issues.apache.org/jira/browse/CASSANDRA
Re: [RELEASE] Apache Cassandra 3.0.0-beta2 released
It’s so nice to see a marketing message in an email from apache…. Come on guys, you almost sound like you’re begging, are sales *that* bad? — Colin Clark co...@clark.ws +1 612-859-6129 skype colin.p.clark > On Sep 8, 2015, at 8:00 PM, Jake Luciani wrote: > > The Cassandra team is pleased to announce the release of Apache Cassandra > version 3.0.0-beta2. > > Apache Cassandra is a fully distributed database. It is the right choice > when you need scalability and high availability without compromising > performance. > > http://cassandra.apache.org/ > > Downloads of source and binary distributions are listed in our download > section: > > http://cassandra.apache.org/download/ > > This version is a *beta* release[1] on the 3.0 series. As always, please pay > attention to the release notes[2] and Let us know[3] if you were to > encounter > any problem. > > Enjoy! > > [1]: http://goo.gl/UWe5yb (CHANGES.txt) > [2]: http://goo.gl/xWOSDa (NEWS.txt) > [3]: https://issues.apache.org/jira/browse/CASSANDRA
End June retrospective, July retrospective will start @ C* summit
Hi all, I am closing out July retrospective now. The retrospective doc has a single author (me) which kind of says that doing this asynchronously by email isn't working. At least not as a starting point. I am not super surprised nor am I disappointed. Trying and failing is part of eventually trying and succeeding. Process and iterating on process is a skill you have to develop and it's hard to do when you don't have dedicated time in your schedule for it. I'm an advocate for retrospectives and I still don't send out the emails out on time. We are going to have a butts in seats retrospective at summit and I will take notes and make that available. We'll have a chance to discuss where to go from there. Regards, Ariel
Re: End June retrospective, July retrospective will start @ C* summit
Hi, I a mistake in the original email. This is actually the end of the July retrospective. The August retrospective will start @ C* summit. Regards, Ariel On Tue, Sep 8, 2015 at 2:36 PM, Ariel Weisberg wrote: > Hi all, > > I am closing out July retrospective now. The retrospective doc has a > single author (me) which kind of says that doing this asynchronously by > email isn't working. At least not as a starting point. > > I am not super surprised nor am I disappointed. Trying and failing is part > of eventually trying and succeeding. Process and iterating on process is a > skill you have to develop and it's hard to do when you don't have dedicated > time in your schedule for it. I'm an advocate for retrospectives and I > still don't send out the emails out on time. > > We are going to have a butts in seats retrospective at summit and I will > take notes and make that available. We'll have a chance to discuss where to > go from there. > > Regards, > Ariel >
Reproduce stale read in Cassandra
Hi there, I currently research on the improvement of consistency level of Cassandra. Since I am new to C*, does anyone know how to reproduce the stale reads on the cluster? Is there a transaction lib that can be loaded into it and reproduce the stale reads? ***TEST environment*** AWS 3 instances(nodes) + Ubuntu 14.04 + Cassandra 2.2.1 I plan to reproduce the stale reads first and then take a look at the source code trying to find out a way for improvement. Thanks so much. Any of your help is highly appreciated!!! Best, Xindi
Re: Reproduce stale read in Cassandra
2 node cluster. RF=2. Take one node down. Do a write. Take the other node down. Do a read. It will be stale since the node that is up missed the original write, and you took the node that did see the write down before it could replay to it. This is by design though so I'm curious what kind of improvement you are looking for. On Tue, Sep 8, 2015 at 3:57 PM, Cindy Wang wrote: > Hi there, > > I currently research on the improvement of consistency level of Cassandra. > Since I am new to C*, does anyone know how to reproduce the stale reads on > the cluster? Is there a transaction lib that can be loaded into it and > reproduce the stale reads? > > ***TEST environment*** > > AWS 3 instances(nodes) + Ubuntu 14.04 + Cassandra 2.2.1 > > I plan to reproduce the stale reads first and then take a look at the > source code trying to find out a way for improvement. > > Thanks so much. Any of your help is highly appreciated!!! > > Best, > Xindi > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Reproduce stale read in Cassandra
Hello Jonathan, Thanks for your quick reply. Since consistency is tunable by making tradeoffs with latency and availability, it lead me to think about how to improve the consistency level (better than eventual consistency) while guarantee that latency and availability won't be affected much. So now I am working on Cassandra and trying to make some contribution on this. Although there are some approaches that already been done, I would just like to figure out another approach. I understand it theoretically, yet couldn't find a way to reproduce it by a large set of transaction, for example, 10,000 operations.. Do you have any comments? Thank you so much! Best, Xindi 2015-09-08 18:08 GMT-04:00 Jonathan Ellis : > 2 node cluster. RF=2. Take one node down. Do a write. Take the other > node down. Do a read. It will be stale since the node that is up missed > the original write, and you took the node that did see the write down > before it could replay to it. > > This is by design though so I'm curious what kind of improvement you are > looking for. > > On Tue, Sep 8, 2015 at 3:57 PM, Cindy Wang > wrote: > > > Hi there, > > > > I currently research on the improvement of consistency level of > Cassandra. > > Since I am new to C*, does anyone know how to reproduce the stale reads > on > > the cluster? Is there a transaction lib that can be loaded into it and > > reproduce the stale reads? > > > > ***TEST environment*** > > > > AWS 3 instances(nodes) + Ubuntu 14.04 + Cassandra 2.2.1 > > > > I plan to reproduce the stale reads first and then take a look at the > > source code trying to find out a way for improvement. > > > > Thanks so much. Any of your help is highly appreciated!!! > > > > Best, > > Xindi > > > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder, http://www.datastax.com > @spyced >
[GitHub] cassandra pull request:
Github user Achowdhe commented on the pull request: https://github.com/apache/cassandra/commit/ea6081216f1a1e5cfa1505982e86da036dbec558#commitcomment-13127782 Hi Joshua, As per my understanding , if we are disabling the GC_WARN_THRESHOLD_IN_MS (i.e making 0 ms) then in src/java/org/apache/cassandra/service/GCInspector.java for below code : if (durationPerCollection > GC_WARN_THRESHOLD_IN_MS) StatusLogger.log(); will result is printing statuslogger everytime , may be causing mess to some users. can we have look on this ? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
