Re: 4.0 Testing Signup

[Tommy Stendahl]

Hi,

I like to add myself as contributor under Cluster Upgrade but I could 
not edit the page, could you please help.

I have already done some testing in this are lately and created a few 
jiras, two remains open CASSANDRA-14842 and CASSANDRA-14848.

Thanks, Tommy

On 2018-11-08 23:30, Joseph Lynch wrote:
> On Thu, Nov 8, 2018 at 11:04 AM Romain Hardouin 
> wrote:
>
>> Hi,
>> I'm volunteer to be contributor on Metrics or Tooling component. Are we
>> supposed/allowed to edit Confluence page directly?Btw I think that tooling
>> should be split, maybe one ticket per tool?
>>
> Awesome! Yes feel free to add yourself as a contributor to whichever
> component you can contribute testing to (I think you need to make an Apache
> confluence account to do so), if it isn't working let me know and I'll add
> your contact information. Right now we don't have a shepherd for either
> component yet but I think it's pretty reasonable to have a tracking ticket
> that either has subtasks for each tool (e.g. CASSANDRA-14746) or just use
> linking (e.g. CASSANDRA-14697). Just try to describe in the tickets what
> kinds of tests you're running and make sure they're tagged with 4.0-QA
> label if possible.
>
> Thanks!
> - Joey
>

Re: 4.0 Testing Signup

[Scott Andreas]

Joey, thanks for starting this document!

I’ve updated it to add several leads/contributors, and will probably have a few 
minor updates to add soon.


On November 8, 2018 at 2:49:52 PM, Joseph Lynch 
(joe.e.ly...@gmail.com) wrote:

On Thu, Nov 8, 2018 at 1:42 PM kurt greaves  wrote:

> Been thinking about this for a while and agree it's how we should approach
> it. BIkeshedding but seems like a nice big table would be suitable here,
> and I think rather than a separate confluence page per component we just
> create separate JIRA tickets that detail what's being tested and the
> approach, and discussion can be kept in JIRA.
>
Can we let each component group figure out how they want to do project
management with the one caveat that they list the component on the page and
have a tracking ticket with the right label? I think that's the lightest
touch process that will work.


> I'm happy to volunteer for testing repair. I can also add lots of different
> components to the list if you're happy for me to attack the page.
>
Go for it! I just jotted down some seed topics to get it started. Please do
edit and refactor to make it better.

-Joey

Re: Jepsen testing

[Yuji Ito]

Thank you for the suggestion.

I haven't tried Cassandra 4.0 yet.
For now, the testing supports only released versions which are distributed
at http://www.us.apache.org/dist/cassandra/ .

I have to modify the installation code and verify also the wrapper.
It's a good next step.

Thanks,
Yuji

2018年11月9日(金) 7:47 sankalp kohli :

> Should we use confluence page to sign them up for this testing?
>
> https://cwiki.apache.org/confluence/display/CASSANDRA/4.0+QA+Signup
>
> On Thu, Nov 8, 2018 at 2:07 PM Nate McCall  wrote:
>
> > [- cassandra-users]
> > Hi Yuji,
> > Thanks so much for working on this! Any fault injection testing is
> > certainly worth the effort.
> >
> > Thanks,
> > -Nate
> > On Thu, Nov 8, 2018 at 1:36 PM Yuji Ito  wrote:
> > >
> > > Hi,
> > >
> > > We are working on Jepsen testing for Cassandra.
> > > https://github.com/scalar-labs/jepsen/tree/cassandra/cassandra
> > >
> > > As you may know, Jepsen is a framework for distributed systems
> > verification.
> > > It can inject network failure and so on and check data consistency.
> > > https://github.com/jepsen-io/jepsen
> > >
> > > Our tests are based on riptano's great work.
> > > https://github.com/riptano/jepsen/tree/cassandra/cassandra
> > >
> > > I refined it for the latest Jepsen and removed some tests.
> > > Next, I'll fix clock-drift tests.
> > >
> > > I would like to get your feedback.
> > >
> > > Thanks,
> > > Yuji Ito
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
> >
>

Re: 4.0 Testing Signup

[Joseph Lynch]

On Thu, Nov 8, 2018 at 1:42 PM kurt greaves  wrote:

> Been thinking about this for a while and agree it's how we should approach
> it. BIkeshedding but seems like a nice big table would be suitable here,
> and I think rather than a separate confluence page per component we just
> create separate JIRA tickets that detail what's being tested and the
> approach, and discussion can be kept in JIRA.
>
Can we let each component group figure out how they want to do project
management with the one caveat that they list the component on the page and
have a tracking ticket with the right label? I think that's the lightest
touch process that will work.


> I'm happy to volunteer for testing repair. I can also add lots of different
> components to the list if you're happy for me to attack the page.
>
Go for it! I just jotted down some seed topics to get it started. Please do
edit and refactor to make it better.

-Joey

Re: 4.0 Testing Signup

[Joseph Lynch]

On Thu, Nov 8, 2018 at 11:04 AM Romain Hardouin 
wrote:

>
> Hi,
> I'm volunteer to be contributor on Metrics or Tooling component. Are we
> supposed/allowed to edit Confluence page directly?Btw I think that tooling
> should be split, maybe one ticket per tool?
>

Awesome! Yes feel free to add yourself as a contributor to whichever
component you can contribute testing to (I think you need to make an Apache
confluence account to do so), if it isn't working let me know and I'll add
your contact information. Right now we don't have a shepherd for either
component yet but I think it's pretty reasonable to have a tracking ticket
that either has subtasks for each tool (e.g. CASSANDRA-14746) or just use
linking (e.g. CASSANDRA-14697). Just try to describe in the tickets what
kinds of tests you're running and make sure they're tagged with 4.0-QA
label if possible.

Thanks!
- Joey

Re: Jepsen testing

[sankalp kohli]

Should we use confluence page to sign them up for this testing?

https://cwiki.apache.org/confluence/display/CASSANDRA/4.0+QA+Signup

On Thu, Nov 8, 2018 at 2:07 PM Nate McCall  wrote:

> [- cassandra-users]
> Hi Yuji,
> Thanks so much for working on this! Any fault injection testing is
> certainly worth the effort.
>
> Thanks,
> -Nate
> On Thu, Nov 8, 2018 at 1:36 PM Yuji Ito  wrote:
> >
> > Hi,
> >
> > We are working on Jepsen testing for Cassandra.
> > https://github.com/scalar-labs/jepsen/tree/cassandra/cassandra
> >
> > As you may know, Jepsen is a framework for distributed systems
> verification.
> > It can inject network failure and so on and check data consistency.
> > https://github.com/jepsen-io/jepsen
> >
> > Our tests are based on riptano's great work.
> > https://github.com/riptano/jepsen/tree/cassandra/cassandra
> >
> > I refined it for the latest Jepsen and removed some tests.
> > Next, I'll fix clock-drift tests.
> >
> > I would like to get your feedback.
> >
> > Thanks,
> > Yuji Ito
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

Re: 4.0 Testing Signup

[Nate McCall]

Thanks Romain!

Let's keep a top level ticket for the/a component, but add child tasks
as needed. I think child tickets are a little easier to manage than
using a tag or similar.
On Thu, Nov 8, 2018 at 11:04 AM Romain Hardouin
 wrote:
>
>
> Hi,
> I'm volunteer to be contributor on Metrics or Tooling component. Are we 
> supposed/allowed to edit Confluence page directly?Btw I think that tooling 
> should be split, maybe one ticket per tool?
> Thanks,
> RomainLe mercredi 7 novembre 2018 à 22:51:30 UTC+1, sankalp kohli 
>  a écrit :
>
>  This is good start and we should use this approach each component. Once we
> have volunteers for each area, it will be important to also publish a
> confluence page per component by the volunteer so we can know/discuss how
> it was tested.
>
> On Wed, Nov 7, 2018 at 12:14 PM Joseph Lynch  wrote:
>
> > Following up on Jon's call
> > <
> > https://lists.apache.org/thread.html/17e57d1666393d961a15502a648a1174a1b145a4bf0a8e07fd8bb760@%3Cdev.cassandra.apache.org%3E
> > >
> > for QA, I put together the start of a confluence page
> > for
> > people to list out important components that they think should be tested
> > before 4.0 releases and hopefully committers and contributors can signup
> > and present their progress to the community. I've certainly missed a ton of
> > components that need testing but I figured that it may be good to get the
> > conversation started and moving forward.
> >
> > What do people think? Is there a more effective way to list these out or if
> > people like this maybe folks can start contributing sections and
> > volunteering to shepherd or test them?
> >
> > Let me know,
> > -Joey
> >
>

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Feedback request for Message Flusher bug found in 3.0.17

[Sumanth Pasupuleti]

Hi,

We recently found this issue on one of our 3.0.17 clusters, where the
Message Flusher falls off the event loop, eventually resulting in OOM on a
bunch of nodes. We saw this happen twice so far.

CASSANDRA-14855  has
all the details (including heap dump analysis). Backported ImmediateFlusher
from trunk as a fix for this. Would like to get feedback (on the JIRA) if
this fix is recommended, or if there is a suggestion for a better fix.

Thanks,
Sumanth

Re: Jepsen testing

[Nate McCall]

[- cassandra-users]
Hi Yuji,
Thanks so much for working on this! Any fault injection testing is
certainly worth the effort.

Thanks,
-Nate
On Thu, Nov 8, 2018 at 1:36 PM Yuji Ito  wrote:
>
> Hi,
>
> We are working on Jepsen testing for Cassandra.
> https://github.com/scalar-labs/jepsen/tree/cassandra/cassandra
>
> As you may know, Jepsen is a framework for distributed systems verification.
> It can inject network failure and so on and check data consistency.
> https://github.com/jepsen-io/jepsen
>
> Our tests are based on riptano's great work.
> https://github.com/riptano/jepsen/tree/cassandra/cassandra
>
> I refined it for the latest Jepsen and removed some tests.
> Next, I'll fix clock-drift tests.
>
> I would like to get your feedback.
>
> Thanks,
> Yuji Ito

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Feedback request for Message Flusher bug found in 3.0.17 (CASSANDRA-14855)

[Sumanth Pasupuleti]

Hi,

We recently found this issue on one of our 3.0.17 clusters, where the
Message Flusher falls off the event loop, eventually resulting in OOM on a
bunch of nodes. We saw this happen twice so far.

CASSANDRA-14855  has
all the details (including heap dump analysis). Backported ImmediateFlusher
from trunk as a fix for this. Would like to get feedback (on the JIRA) if
this fix is recommended, or if there is a suggestion for a better fix.

Thanks,
Sumanth

Re: 4.0 Testing Signup

[Romain Hardouin]

 
Hi,
I'm volunteer to be contributor on Metrics or Tooling component. Are we 
supposed/allowed to edit Confluence page directly?Btw I think that tooling 
should be split, maybe one ticket per tool?
Thanks,
RomainLe mercredi 7 novembre 2018 à 22:51:30 UTC+1, sankalp kohli 
 a écrit :  
 
 This is good start and we should use this approach each component. Once we
have volunteers for each area, it will be important to also publish a
confluence page per component by the volunteer so we can know/discuss how
it was tested.

On Wed, Nov 7, 2018 at 12:14 PM Joseph Lynch  wrote:

> Following up on Jon's call
> <
> https://lists.apache.org/thread.html/17e57d1666393d961a15502a648a1174a1b145a4bf0a8e07fd8bb760@%3Cdev.cassandra.apache.org%3E
> >
> for QA, I put together the start of a confluence page
> for
> people to list out important components that they think should be tested
> before 4.0 releases and hopefully committers and contributors can signup
> and present their progress to the community. I've certainly missed a ton of
> components that need testing but I figured that it may be good to get the
> conversation started and moving forward.
>
> What do people think? Is there a more effective way to list these out or if
> people like this maybe folks can start contributing sections and
> volunteering to shepherd or test them?
>
> Let me know,
> -Joey
>