You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Jeremy Hanna <je...@gmail.com> on 2010/12/01 22:24:57 UTC
Coordinated testing for 0.7
I was wondering if there was a coordinated plan for testing the 0.7 release. I realize that testing is ultimately up to the individual team. However, with 0.7 there are a _lot_ of significant changes and I wondered if there was interest in coordinating efforts to do more extensive testing above and beyond the integration tests and things built into the source tree currently.
I think https://issues.apache.org/jira/browse/CASSANDRA-874 is also relevant for furthering the integration tests.
Any thoughts?
Re: Coordinated testing for 0.7
Posted by Ryan King <ry...@twitter.com>.
On Thu, Dec 2, 2010 at 10:57 AM, Paul Querna <pa...@querna.org> wrote:
> On Wed, Dec 1, 2010 at 10:48 PM, Jeremy Hanna
> <je...@gmail.com> wrote:
>> Along with Ryan's SF thing I could help organize something in the
>> Austin area if there is interest.
>>
>> Would people like to do a Cassandra test-athon a week from Friday
>> (December 10th)? That might give people some more time to finish up
>> with remaining bug fixes of known bugs. Also hopefully counters would
>> be worked out and committed by then.
>>
>> So node movement. What about bootstrapping in a cluster (various
>> scenarios)? How about random partitioner specific tests (which were
>> started a while back)? Or maybe doing a bunch of tests with online
>> schema changes? How about making these tests repeatable in the
>> integration tests - are multiple-node tests on a single machine
>> feasible or is that better suited for manual running of scripts not as
>> part of the build?
>
>
> +1, December 10th works; I'm in SF too and would love to get some of
> the 0.7 stuff actually tested :-)
Cool. The 10th wouldn't work as well for us. Would the 9th work for people?
-ryan
Re: Coordinated testing for 0.7
Posted by Paul Querna <pa...@querna.org>.
On Wed, Dec 1, 2010 at 10:48 PM, Jeremy Hanna
<je...@gmail.com> wrote:
> Along with Ryan's SF thing I could help organize something in the
> Austin area if there is interest.
>
> Would people like to do a Cassandra test-athon a week from Friday
> (December 10th)? That might give people some more time to finish up
> with remaining bug fixes of known bugs. Also hopefully counters would
> be worked out and committed by then.
>
> So node movement. What about bootstrapping in a cluster (various
> scenarios)? How about random partitioner specific tests (which were
> started a while back)? Or maybe doing a bunch of tests with online
> schema changes? How about making these tests repeatable in the
> integration tests - are multiple-node tests on a single machine
> feasible or is that better suited for manual running of scripts not as
> part of the build?
+1, December 10th works; I'm in SF too and would love to get some of
the 0.7 stuff actually tested :-)
Re: Coordinated testing for 0.7
Posted by Jeremy Hanna <je...@gmail.com>.
Along with Ryan's SF thing I could help organize something in the
Austin area if there is interest.
Would people like to do a Cassandra test-athon a week from Friday
(December 10th)? That might give people some more time to finish up
with remaining bug fixes of known bugs. Also hopefully counters would
be worked out and committed by then.
So node movement. What about bootstrapping in a cluster (various
scenarios)? How about random partitioner specific tests (which were
started a while back)? Or maybe doing a bunch of tests with online
schema changes? How about making these tests repeatable in the
integration tests - are multiple-node tests on a single machine
feasible or is that better suited for manual running of scripts not as
part of the build?
On Dec 1, 2010, at 11:30 PM, Jonathan Ellis <jb...@gmail.com> wrote:
> It will not surprise most people who have deployed Cassandra that
> there are still dragons in the node movement code. That is the
> primary place I would like to see more testing.
>
> On Wed, Dec 1, 2010 at 3:24 PM, Jeremy Hanna <je...@gmail.com> wrote:
>> I was wondering if there was a coordinated plan for testing the 0.7 release. I realize that testing is ultimately up to the individual team. However, with 0.7 there are a _lot_ of significant changes and I wondered if there was interest in coordinating efforts to do more extensive testing above and beyond the integration tests and things built into the source tree currently.
>>
>> I think https://issues.apache.org/jira/browse/CASSANDRA-874 is also relevant for furthering the integration tests.
>>
>> Any thoughts?
>
>
>
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of Riptano, the source for professional Cassandra support
> http://riptano.com
Re: Coordinated testing for 0.7
Posted by Jonathan Ellis <jb...@gmail.com>.
It will not surprise most people who have deployed Cassandra that
there are still dragons in the node movement code. That is the
primary place I would like to see more testing.
On Wed, Dec 1, 2010 at 3:24 PM, Jeremy Hanna <je...@gmail.com> wrote:
> I was wondering if there was a coordinated plan for testing the 0.7 release. I realize that testing is ultimately up to the individual team. However, with 0.7 there are a _lot_ of significant changes and I wondered if there was interest in coordinating efforts to do more extensive testing above and beyond the integration tests and things built into the source tree currently.
>
> I think https://issues.apache.org/jira/browse/CASSANDRA-874 is also relevant for furthering the integration tests.
>
> Any thoughts?
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com
Re: Coordinated testing for 0.7
Posted by Dave Revell <da...@meebo-inc.com>.
I'd go to that, schedule permitting. My knowledge of the source is not very
deep, but I could be useful in some way.
We obviously have a lot to gain from a well-tested 0.7 release.
- Dave
On Wed, Dec 1, 2010 at 8:49 PM, Ryan King <ry...@twitter.com> wrote:
> I'd be happy to host a hackathon at Twitter HQ in SF for this. Anyone
> interested in that?
>
> -ryan
>
> On Wed, Dec 1, 2010 at 7:18 PM, Jeremy Hanna <je...@gmail.com>
> wrote:
> > Perhaps the time could be better spent trying to beef up the integration
> tests and looking for ways to root out potential regressions...
> >
>
Re: Coordinated testing for 0.7
Posted by Ryan King <ry...@twitter.com>.
I'd be happy to host a hackathon at Twitter HQ in SF for this. Anyone
interested in that?
-ryan
On Wed, Dec 1, 2010 at 7:18 PM, Jeremy Hanna <je...@gmail.com> wrote:
> Perhaps the time could be better spent trying to beef up the integration tests and looking for ways to root out potential regressions...
>
> Back in September a handful of us in the Austin/San Antonio area did an Avro hackathon to get functional parity between thrift and avro. I wonder if there could be a day set aside to do something to contribute to testing out 0.7 - unit/integration test additions would be beneficial long-term.
>
> Anyway, it could be coordinated by one or a small number of people so that there isn't duplication - something like that.
>
> I know several have spent long hours already making it solid. Just trying to brainstorm ways to get some additional good contributions in the core for making for a more solid 0.7.0 release.
>
> Again... any thoughts?
>
> On Dec 1, 2010, at 3:24 PM, Jeremy Hanna wrote:
>
>> I was wondering if there was a coordinated plan for testing the 0.7 release. I realize that testing is ultimately up to the individual team. However, with 0.7 there are a _lot_ of significant changes and I wondered if there was interest in coordinating efforts to do more extensive testing above and beyond the integration tests and things built into the source tree currently.
>>
>> I think https://issues.apache.org/jira/browse/CASSANDRA-874 is also relevant for furthering the integration tests.
>>
>> Any thoughts?
>
>
Re: Coordinated testing for 0.7
Posted by Jeremy Hanna <je...@gmail.com>.
Perhaps the time could be better spent trying to beef up the integration tests and looking for ways to root out potential regressions...
Back in September a handful of us in the Austin/San Antonio area did an Avro hackathon to get functional parity between thrift and avro. I wonder if there could be a day set aside to do something to contribute to testing out 0.7 - unit/integration test additions would be beneficial long-term.
Anyway, it could be coordinated by one or a small number of people so that there isn't duplication - something like that.
I know several have spent long hours already making it solid. Just trying to brainstorm ways to get some additional good contributions in the core for making for a more solid 0.7.0 release.
Again... any thoughts?
On Dec 1, 2010, at 3:24 PM, Jeremy Hanna wrote:
> I was wondering if there was a coordinated plan for testing the 0.7 release. I realize that testing is ultimately up to the individual team. However, with 0.7 there are a _lot_ of significant changes and I wondered if there was interest in coordinating efforts to do more extensive testing above and beyond the integration tests and things built into the source tree currently.
>
> I think https://issues.apache.org/jira/browse/CASSANDRA-874 is also relevant for furthering the integration tests.
>
> Any thoughts?