Re: All clear to import dtest

Will the Github repo continue to get updates (perhaps as a mirror of the ASF one)? Just checking to see if any changes need to be made in the near future for an in-house CI pipeline running dtests. On Fri, 16 Jun 2017 at 09:39 Nate McCall wrote: > We got through all the

All clear to import dtest

We got through all the legal shenanigans necessary to import dtest into the project: https://issues.apache.org/jira/browse/CASSANDRA-13584 This is just a heads up that I have created CASSANDRA-13613 for tracking the actual import and will be adding some sub-tasks next week for the actual

Re: New contribution - Burst Hour Compaction Strategy

Hi Thanks for engaging in this discussion! Cameron, regarding the benchmark, I need to spend some time exploring the stress tool options, but I aim to create a stress test that goes on for a period of at least 48 hours, and then run it for all strategies (with a 24-hour burst for BHCS). I want

Re: Is concurrent_batchlog_writes option used/implemented?

The project hosted docs can be found here: http://cassandra.apache.org/doc/latest/configuration/cassandra_config_file.html If you find something wrong in those open a JIRA. DataStax has a documentation feedback

Re: Is concurrent_batchlog_writes option used/implemented?

Hey Tomas, Thanks for finding these errors. Unfortunately, those are problems on the Datastax-hosted documentation, not the docs hosted by the Apache project. To fix those problems you should contact Datastax (I don't have a URL handy rn, but if one of the DS folks who follow this list can add

Re: Is concurrent_batchlog_writes option used/implemented?

And yet another glitch in the documentation at: https://docs.datastax.com/en/cassandra/3.0/cassandra/configuration/configCassandra_yaml.html#configCassandra_yaml__cqlTruncateequest_timeout_in_ms I guess it should be truncate_timeout_in_ms instead. Is there a more proper way I should use to