cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben Slater (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11914) Provide option for cassandra-stress to dump all settings
Date Tue, 02 Aug 2016 02:29:20 GMT


Ben Slater commented on CASSANDRA-11914:

Turns out the "create schema" problem is not so much that it doesn't create the schema but
rather that trying to do the calcs to display the "Generating batches with x partitions and
x rows ..." message results in a call to maybeLoadSchemaInfo() which fails if the schema doesn't
exist (creating the schema still works if you don't do print-settings).

So, I think the alternatives to fix are either (a) create the schema (if necessary) at the
time printSettings() is called, (b) put the "Generating batches ..." message back where is
was in getInsert() at the start of the run or (c) move printSettings() until after the run
is complete.

I think my preference is (b) as creating a schema sounds like a very unexpected side effect
of printSettings() and you probably want to be able to print settings without completing a
full run (ruling out (c)). However, let me know if you can see a different solution or prefer
a different option.


> Provide option for cassandra-stress to dump all settings
> --------------------------------------------------------
>                 Key: CASSANDRA-11914
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Ben Slater
>            Assignee: Ben Slater
>            Priority: Minor
>             Fix For: 3.x
> cassandra-stress has quite a lot of default settings and settings that are derived as
side effects of explicit options. For people learning the tool and saving a clear record of
what was run, I think it would be useful if there was an option to have the tool print all
its settings at the start of a run.

This message was sent by Atlassian JIRA

View raw message