non-binding +1
Here's the testing summary on the 3.0.9-tentative tag:
http://12.am/tmp/3.0.9-tests.png
--
Michael
On 09/15/2016 01:57 PM, Jake Luciani wrote:
> I propose the following artifacts for release as 3.0.9.
>
> sha1: d600f51ee1a3eb7b30ce3c409129567b70c22012
> Git:
>
What's preventing the use of the 3.6 or 3.7 releases where this bug is
already fixed? This is also fixed in the 3.0.6/7/8 releases.
Michael
On 09/14/2016 08:30 PM, Jonathan Haddad wrote:
> Unfortunately CASSANDRA-11618 was fixed in 3.6 but was not back ported to
> 3.5 as well, and it makes
On 09/09/2016 02:31 PM, Jeff Jirsa wrote:
> Can you describe the size and number of slaves we need to do things "right"?
>
> How many cores? How much ram? How many slaves?
We currently run all unit test jobs on m3.xlarge instances, which seems
to work fine. (Almost all the dtest jobs run OK on
I have an ongoing INFRA ticket with the testing issues we've seen when
utilizing the ASF's Jenkins infrastructure. Basically, the results are
erratic, due to other project (and Cassandra) concurrent test runs. Our
testing on CassCI is pretty stable, since we do not run any concurrent
tests.
On 09/02/2016 05:19 AM, Andy Cobley wrote:
> However I’ve just tried apache-cassandra-3.10-SNAPSHOT and am
> still getting
>
> "Cassandra 3.0 and later require Java 8u40 or later.”
What is the git sha of your 3.10-SNAPSHOT build?
I see this was committed to trunk Jul 27, so perhaps your build
Another couple ABORT examples have presented themselves, tonight, one
that has logs.
Usually we'll see unit tests finish similar to:
01:57:39 [junit] Testsuite:
org.apache.cassandra.cql3.statements.PropertyDefinitionsTest
01:57:39 [junit] Testsuite:
Jenkins jobs in ABORTED status are bad. A lot of times they tend to be
ignored/re-run to get completed results, which is OK, only if the reason
is due to server setup or configuration problems. There's a relatively
recent pattern of o.a.c.cql3.validation test hanging up jobs, and I've
been unable
It looks like Dave replied to your first email that he added your wiki
user to be able to edit pages. Did your login not work properly, or did
you get some sort of error editing the wiki?
(cc'ed directly, too)
--
Kind regards,
Michael
On 08/18/2016 08:15 AM, Danielle Blake wrote:
> Hi,
>
> I
On 08/16/2016 10:52 AM, Aleksey Yeschenko wrote:
> No objections, the plan sounds good to me.
>
> In addition to that, prep for pushing 3.0.9 out with 3.9.
Thanks. Yes, 3.0.9 is also up for release, without any branch song and
dance :)
--
Michael
On 08/15/2016 01:12 PM, Chris Mattmann wrote:
> How is it harder to point someone to mail?
Mailing lists can be simple to join and converse. Like some other folks,
I'm on a large number of lists and get massive amounts of mail.
Extremely busy mailing lists need user-level care for them to be
On 08/03/2016 03:31 PM, Kant Kodali wrote:
> when are we moving from SEDA to TPC? any timeline or something that I can
> look out for?
>
You could follow the JIRA ticket parent and children, review patches,
etc. :) https://issues.apache.org/jira/browse/CASSANDRA-10989
--
Kind regards,
Michael
n changes
>>> in it. So does 3.0.9. The sooner we can get those into people’s hands,
>> the
>>> better.
>>> 3.8 is ultimately unimportant. Even if we release 3.8 and 3.9 on the same
>>> date, it’s not a huge deal.
>>>
>>
s in-flight
> queries during upgrade *and* the fact the vast majority of our
> upgrade tests are failing is not _obviously_ enough to hold a
> release, without the need for further considerations. This speaks imo
> poorly of the PMC attachment to release quality.
>
> But you are correct on the
Thanks for the clarity, Jonathan. I agree that an August 3.8 release
target sounds like the most reasonable option, at this point in time.
With Sylvain's binding -1, this vote has failed.
--
Kind regards,
Michael Shuler
On 07/21/2016 05:33 PM, Jonathan Ellis wrote:
> I feel like the calen
I propose the following artifacts for release as 3.8.
sha1: c3ded0551f538f7845602b27d53240cd8129265c
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.8-tentative
Artifacts:
On 07/11/2016 02:40 AM, Vlad wrote:
>
> I see 3.0.8 tag (8b21d9) at
> https://git1-us-west.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/cassandra-3.0.8
> but not on https://github.com/apache/cassandra/commits/cassandra-3.0
Tag mirroring to github is sometimes a little slow, but
On 06/27/2016 09:59 AM, Jonathan Ellis wrote:
> How would I deploy a cluster with Snap?
>
> With the package I can pre-deploy my configuration to the node with cluster
> name, seeds, etc. With Snap do I have to build a custom container to do
> that? Or is there some way to pull in config from
On 06/26/2016 11:03 AM, Jonathan Ellis wrote:
>
> Is Snap a new packaging format like deb/rpm, or does it consume the
> existing deb package?
It's an LXD container delivery system.
--
Kind regards,
Michael
On 06/20/2016 01:16 PM, Will Hayworth wrote:
> Hey all--I didn't want to add more heat than light to this, but I think at
> this point I'm behooved to speak up. :) I'm a developer at Atlassian (the
> folks who make JIRA); I don't work on JIRA itself but have some familiarity
> with its mechanics
On 04/11/2016 12:42 PM, Anuj Wadehra wrote:
> Can someone help me with this one?
This is the type of question you should ask the user@ list. The dev@
list is specifically for the development *of* Cassandra.
> What should be a resonable criteria for taking 3.x releases in
> production?
Short
This mailing list is for discussing the development of Apache Cassandra.
Either talk to your support folks at DataStax or try the user@ list for
help installing (which is probably also inappropriate for DSE).
FWIW, this is a simple user issue with multiple versions of the same
software in apt
On 11/25/2015 07:36 PM, Michael Edge wrote:
> I'd like to update the read/write path description on the wiki (see link
> below) by adding a couple of UML sequence diagrams I drew a while ago. I
> think they are much better than long textual descriptions for describing
> the order of operations on
non-binding +1
--
Michael
On 11/06/2015 03:34 PM, Jake Luciani wrote:
I propose the following artifacts for release as 3.0.0.
sha1: 96f407bce56b98cd824d18e32ee012dbb99a0286
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.0-tentative
Artifacts:
non-binding +1
On 09/19/2015 01:42 PM, Jake Luciani wrote:
I propose the following artifacts for release as 3.0.0-rc1.
sha1: c95a7098cf77b5b8e96feb7c39aca8fec3a02f9c
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.0-rc1-tentative
Artifacts:
This is a prompt for Cassandra developers to discuss the alternatives
and let Test Engineering know what you desire.
As discussed a few times in person, on irc, etc., there are a couple
different ways we can run tests in Jenkins, particularly
cassandra-dtest. The Cassandra developers are the
+1 (non-binding)
On 07/31/2015 08:42 AM, Jake Luciani wrote:
I propose the following artifacts for release as 3.0.0-alpha1.
sha1: b090ed6938c0fad792e51757384bd5ac7f35a301
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.0-alpha1-tentative
Artifacts:
+1 non-binding
On 07/06/2015 01:47 PM, Jake Luciani wrote:
I propose the following artifacts for release as 2.2.0-rc2.
sha1: ebc50d783505854f04f183297ad3009b9095b07e
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.0-rc2-tentative
Artifacts:
+1 non-binding
On 07/06/2015 12:04 PM, Jake Luciani wrote:
I propose the following artifacts for release as 2.1.8.
sha1: db39257c34152f6ccf8d53784cea580dbfe1edad
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.8-tentative
Artifacts:
When we set up autojobs for the dev branches, I did some digging around
the jenkins / githubPR integration, similar to what spark is doing. I'd
be completely on board with working through that setup, if it helps this
workflow.
Michael
On 07/08/2015 03:02 PM, Carl Yeksigian wrote:
Spark has
+1 non-binding
On 06/05/2015 10:27 AM, Jake Luciani wrote:
I propose the following artifacts for release as 2.2.0-rc1.
sha1: b0ae285bdc7377a64ed92f01c67ff46b40ecaac0
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.0-rc1-tentative
Artifacts:
On 06/10/2015 07:20 AM, Amit Singh F wrote:
Could anybody please provide any possible solution for this or some pointers to
get it done.
Run tests on the cassandra-2.0 branch HEAD.
Feel free to discuss issues when running on the latest branch commit.
There have been lots of test problems
non-binding +1
--
Michael
On 04/27/2015 09:46 AM, Jake Luciani wrote:
I propose the following artifacts for release as 2.1.5.
sha1: 3c0a337ebc90b0d99349d0aa152c92b5b3494d8c
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.5-tentative
Artifacts:
Will we need to create new 3.0, 3.1, 3.2, ... deb repositories for each
monthly release? I'm not intimately familiar with the bintray redirects
that ASF Infra set up, recently, but we did have a few issues at first.
I'm wondering if this will require a redirect addition request to Infra
for
On 03/13/2015 05:58 PM, Joe Fasano wrote:
I'm not familiar with opening a JIRA, but would be great to open a general
incident for updating all dependencies in 3.0.
Just a quick follow up - a JIRA was opened on the topic:
https://issues.apache.org/jira/browse/CASSANDRA-8974
On Fri, Mar 13,
I'm a -1.
CASSANDRA-7688 caused this regression:
from:
http://cassci.datastax.com/job/cassandra-2.1_novnode_dtest/470/testReport/
to:
http://cassci.datastax.com/job/cassandra-2.1_novnode_dtest/472/testReport/
--
Michael
On 02/09/2015 10:50 AM, Jake Luciani wrote:
I propose the following
A few JIRA users are using the Start/Stop Progress triggers to show In
Progress status on tickets, and this has been very useful to ticket
watchers. If you have a ticket or two that you are actively working on,
even if it is sort of working on, if you could try to mash the
Start/Stop Progress
/%3CCALdd-zjmvp7JOtguZ_k951RQHDtFt1cthX%3DRnHQ332C%3DgAZbjw%40mail.gmail.com%3E
[1] http://wiki.apache.org/cassandra/CodeStyle
--
Warm regards,
Michael Shuler
On 12/02/2014 01:04 PM, Michael Shuler wrote:
There are currently 64 patches available, which is awesome! ..and
unfortunate when they wait for review. The project is aware of the
backlog[0] and it takes time to dig through them all. Everyone can help.
Since I was looking to see what old
On 11/22/2014 05:58 PM, Rajanarayanan Thottuvaikkatumana wrote:
A huge number of tests are failing with the same error message. Reproducing one
of such errors.
testlist:
[echo] running test bucket 0 tests
[mkdir] Created dir:
On 11/11/2014 03:35 PM, oded peer wrote:
I submitted patches for Cassandra-7304 (a month ago) and for Cassandra-4476
(a week ago).
Both patches are waiting to be reviewed.
These are my first patches in the Cassandra project.
Can anyone explain and how the review process works?
How long does it
On 10/06/2014 04:36 AM, Vishanth Balasubramaniam wrote:
root@instance-0001:/opt/cassandra/bin# cassandra
root@instance-0001:/opt/cassandra/bin# Exception in thread main
java.lang.NoClassDefFoundError: org/apache/cassandra/service/CassandraDaemon
Caused by:
On 08/11/2014 09:50 AM, horschi wrote:
Would it be possible to have CASSANDRA-7511 reviewed also?
commit 60eab4e45e18d6b08350187acf56deed9654fda7
Author: Jake Luciani j...@apache.org
Date: Fri Aug 1 10:30:48 2014 -0400
Fix truncate to always call flush on table
Patch by Jeremiah
On 08/11/2014 04:21 PM, Michael Shuler wrote:
On 08/11/2014 09:50 AM, horschi wrote:
Would it be possible to have CASSANDRA-7511 reviewed also?
That was committed to the c*-2.0 branch prior to the vote and was in the
tentative-2.0.10 CHANGES.txt:
* Fix truncate to always flush (CASSANDRA
non-binding +1
On 08/08/2014 05:03 AM, Sylvain Lebresne wrote:
I propose the following artifacts for release as 2.0.10.
sha1: cd37d07baf5394d9bac6763de4556249e9837bb0
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.10-tentative
Artifacts:
It seems a bit of a flaw in our test builds allowed us to miss a problem
with this release. Cassandra 1.2.x is intended to remain java_1.6
compatible, to the best of my knowledge. Unfortunately, CASSANDRA-7147
includes a bit of code that breaks the build when using Oracle JDK 1.6.
Should this
(this is probably a better question for the user list - cc/reply-to set)
Allow more files to be open :)
http://www.datastax.com/documentation/cassandra/1.2/cassandra/install/installRecommendSettings.html
--
Kind regards,
Michael
On 06/04/2014 12:15 PM, Florian Dambrine wrote:
Hi every
On 05/12/2014 11:58 AM, Maciej Miklas wrote:
I’ve tried to subscribe to user-subscr...@cassandra.apache.org, it
takes one day to receive confirmation, and later on nothing - no
emails, I’ve been waiting for two days. Could someone check it out?
https://blogs.apache.org/infra/entry/mail_outage
Then you likely need to fix your I/O problem. The most recent error you
posted is an EOFException - the file being read ended unexpectedly.
Probably when you ran out of disk space.
--
Michael
On 04/29/2014 07:48 PM, Yatong Zhang wrote:
Here is another type of exception, seems all are I/O
On 04/15/2014 08:28 AM, Benedict Elliott Smith wrote:
It's only been six months since the last performance drive, and 2.1 is now
around the corner. But I'm hoping we can push performance even further for
3.0. With that in mind, I've picked out what I think are the nearest term
wins to focus on.
non-binding +1
--
Michael
On 04/14/2014 10:38 AM, Sylvain Lebresne wrote:
sha1: 7dbbe9233ce83c2a473ba2510c827a661de99400
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.7-tentative
Artifacts:
Here is the current state of unit and dtest results for the
cassandra-2.1 branch, from the commit I started with this morning.
origin/cassandra-2.1
commit 0fa5cba35b9c97ad34dedbbd89a933f5b9d156e9
Date: Tue Apr 8 12:26:09 2014 -0500
Unit Tests Failing:
On 04/08/2014 03:50 PM, Jonathan Ellis wrote:
How many of these are bisect-able?
Many are test implementation errors, and may not be directly related to
c* errors. They may need to be fixed in ccm or the dtest is just wrong.
I'll keep after these tickets, and bisect c* for ones that look
On 04/08/2014 04:04 PM, Michael Shuler wrote:
On 04/08/2014 03:50 PM, Jonathan Ellis wrote:
How many of these are bisect-able?
Many are test implementation errors, and may not be directly related to
c* errors. They may need to be fixed in ccm or the dtest is just wrong.
I'll keep after
non-binding +1 - looks good to me
--
Michael
On 02/03/2014 03:07 AM, Sylvain Lebresne wrote:
With typo introduced by CASSANDRA-6505 fixed, I propose the following
artifacts
for release as 2.0.5.
sha1: b71372146135fdcee6353ec8254ebfd87c42f907
Git:
non-binding +1 - unit, distributed, and upgrade testing looks good to me.
--
Michael
On 01/31/2014 05:33 AM, Sylvain Lebresne wrote:
I propose the following artifacts for release as 1.2.14.
sha1: 6a9314408cbd69ce26c2ba04bf49df7809a911bf
Git:
, Michael Shuler mich...@pbandjelly.org wrote:
On 12/13/2013 11:28 PM, graham sanderson wrote:
This seemed to get introduced (by mistake?) in ef33f9543
Would there be any issues with adding a .gitignore to the repository? I
could work one up.
--
Kind regards,
Michael
--
Jonathan Ellis
Project
On 12/19/2013 05:46 PM, Jacob Rhoden wrote:
Your missing netbeans includes. I also include the following for
anything java related.
.*.swo
Thumbs.db
Added.
# Maven and other build system/IDE artifacts
bin
build
out/*
target/*
We can't exclude bin/, since it's under revision control and
On 12/18/2013 03:46 AM, Sylvain Lebresne wrote:
Third time's the charm, I propose the following artifacts for release as
1.2.13.
sha1: 1b4c9b45cbf32a72318c42c1ec6154dc1371e8e2
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.13-tentative
Artifacts:
On 12/13/2013 11:28 PM, graham sanderson wrote:
This seemed to get introduced (by mistake?) in ef33f9543
Would there be any issues with adding a .gitignore to the repository? I
could work one up.
--
Kind regards,
Michael
On 11/11/2013 08:59 PM, Shinpei Nakata wrote:
On Tue, Nov 12, 2013 at 12:46 AM, Michael Shuler mich...@pbandjelly.org
wrote:
https://issues.apache.org/jira/browse/CASSANDRA-6321
Okay, I relieved. Exactly same failures (TIMEOUT) happening in my
local environment.
Shinpei, a fix
On 11/10/2013 08:21 PM, Shinpei Nakata wrote:
I've been working on writing a patch for Cassandra recently on the
latest git trunk
(http://git-wip-us.apache.org/repos/asf/cassandra.git). However, from
last week, I got many unit tests error/failure from 'ant test' result.
I'm wondering that
in the DataStax init and pass it along upstream.
--
Kind regards,
Michael Shuler
301 - 362 of 362 matches
Mail list logo
