Re: Committing `CASSANDRA-13701 Lower default num_tokens` and the dtest slowdown…

[Jordan West]

What sort of commitment is there to the follow-up tickets? Are the
follow-ups "make this faster" or are there specific tasks we know will
help? I'm concerned by the increase in testing run times on circle but
don't think that should prevent a good/decided upon default from merging.

Jordan

On Wed, Aug 19, 2020 at 9:49 AM Mick Semb Wever  wrote:

> It was agreed¹ that 4.0 should have the new configuration defaults of
>   num_tokens: 16
>   allocate_tokens_for_local_replication_factor: 3
>
> 13701's patches: against cassandra, cassandra-builds, cassandra-dtest, ccm;
> are reviewed, tested, and ready to commit. But the ccm and dtest patches
> required ccm having to now start nodes sequentially, and adding some longer
> timeout values in the dtests.
>
> The consequence of this is CI runs now take longer. ci-cassandra.a.o's
> dtests take ~30% longer, and circleci's dtests (with vnodes) have gone from
> ~22 to ~43 minutes. The general opinion (on slack²) is to commit, and work
> on improving ccm and dtest startup times in a subsequent ticket.
>
> 13701 was intended to be committed before the first beta release because of
> its user-facing changes. But these numbers are significant enough it makes
> sense to touch base with dev@
>
> Does anyone (strongly) object to the "commit + follow up ticket" approach?
>
> regards,
> Mick
>
>
> ¹ –
>
> https://lists.apache.org/thread.html/ra829084fcf344e9e96fa5c61cb31e909c8629091993471594b65ea89%40%3Cdev.cassandra.apache.org%3E
> ² – https://the-asf.slack.com/archives/CK23JSY2K/p1597747395032600 and
>
> https://the-asf.slack.com/archives/CK23JSY2K/p1597849774078200?thread_ts=1597762085.048300&cid=CK23JSY2K
>

Re: [DISCUSS] Revisiting Java 11's experimental status

[Joshua McKenzie]

Another interesting data point from our site:
https://cassandra.apache.org/doc/latest/new/java11.html?highlight=support

Support Matrix


The support matrix for the Java versions for compiling and running Apache
Cassandra 4.0 is detailed in Table 1. The build version is along the
vertical axis and the run version is along the horizontal axis.

Table 1 : Support Matrix for Java
  Java 8 (Run) Java 11 (Run)
Java 8 (Build) Supported Supported
Java 11(Build) Not Supported SupportedI'm sure the ASF ML is going to
butcher this, but right now our site seems to state that running on Java 11
is supported.

On Wed, Aug 19, 2020 at 11:23 PM  wrote:

> Should clarify - not saying automated tests are enough. Thinking we should
> articulate better what supported means (all tools work, etc - manually
> checking the swath of stuff that’s lacking automated testing assuming we
> even have a good idea of that scope).
>
> If we’re committing to all automated suites work on 11 and we’ll block 4.0
> on bugs we find in jdk11, I think we should do the last small pct of work
> to formally support it.
>
> > On Aug 19, 2020, at 11:18 PM, Joshua McKenzie 
> wrote:
> >
>

Re: [DISCUSS] Updating the C* website design

[Anthony Grasso]

Hi Lorina and Mick,

I've raised CASSANDRA-16066
 to capture the
effort required to carry out the work of converting the markdown to
asciidoc. As part of the work, I think all content files should be moved to
cassandra/doc. This would give a clear separation of concerns;
 - cassandra/doc contains the material (asciidoc) that is converted to the
website content.
 - cassandra-website hosts the live content and contains all the UI
resources (html templates, css, js, images) that style the content.

Document authors only need to touch one repository to make content edits.
It also means they only need to run Antora in one location to generate the
content.

The proposal is a fairly common way of publishing content with Antora and
there are a number of examples out there of how to do this. Note, there
would be no alteration to design/content/layout of the website itself. The
only things changing would be the layout of the repositories and the tools
generating the content.

I'm happy to help with the changes if we think this is a good way to go.

Regards,
Anthony

On Thu, 6 Aug 2020 at 05:33, Lorina Poland  wrote:

> The one issue I see with your suggestion about versioned/non-versioned docs
> is that the cassandra/doc repo will have asciidoc files, and currently, all
> the items in the cassandra-website repo are in markdown. There are possible
> solutions (use antora for the website, put the non-versioned docs in their
> own repo which antora can use for building, for example), but that needs
> exploration.
>
> Lorina Poland
>
>
>
>
> On Wed, Aug 5, 2020 at 12:06 PM Michael Semb Wever  wrote:
>
> >
> >
> > > See that here:
> > >
> >
> https://docs.google.com/document/d/1aeNtgyPAsKcNa0GSKvl2ywlFEj30714ry4Sb5turWeE/edit?usp=sharing
> > >
> > > This outline is not complete, just my initial scribblings. Certainly
> > > collaboration would be welcome.
> >
> >
> > This is awesome Lorina. It would also be great to see all non-versioned
> > docs moved out of the cassandra repository and into the cassandra-website
> > repository (where they become easier to update).
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
> >
>