Re: 4.0 Testing Signup

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 Lync

Re: 4.0 Testing Signup

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

Re: Jepsen testing

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年

Re: 4.0 Testing Signup

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 J

Re: 4.0 Testing Signup

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 your

Re: Jepsen testing

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

Re: 4.0 Testing Signup

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 Toolin

Feedback request for Message Flusher bug found in 3.0.17

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 (includ

Re: Jepsen testing

[- 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/cassand

Re: 4.0 Testing Signup

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,

Jepsen testing

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

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

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 (includ

Re: 4.0 Testing Signup

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