[jira] [Commented] (CASSANDRA-12971) Add CAS option to WRITE test to stress tool
[ https://issues.apache.org/jira/browse/CASSANDRA-12971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273986#comment-16273986 ] Vladimir Yudovin commented on CASSANDRA-12971: -- I guess yes. > Add CAS option to WRITE test to stress tool > --- > > Key: CASSANDRA-12971 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12971 > Project: Cassandra > Issue Type: New Feature > Components: Stress, Tools >Reporter: Vladimir Yudovin >Assignee: Vladimir Yudovin > Attachments: stress-cass.patch > > > If -cas option is present each UPDATE is performed with true IF condition, > thus data is inserted anyway. > It's implemented, if it's needed I proceed with the patch. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-13695) ReadStage threads have no timeout
Vladimir Yudovin created CASSANDRA-13695: Summary: ReadStage threads have no timeout Key: CASSANDRA-13695 URL: https://issues.apache.org/jira/browse/CASSANDRA-13695 Project: Cassandra Issue Type: Bug Reporter: Vladimir Yudovin Following this discussion: [High CPU after read timeout|https://lists.apache.org/thread.html/e22a2a77634f9228bf1d5474cc77ea461262f2e125cd2fa21a17f7a2@%3Cdev.cassandra.apache.org%3E] Currently ReadStage threads have no timeout and continue to run without limitation after xxx_request_timeout_in_ms expired. Thus single bad request like SELECT ... ALLOW FILTERING can paralyze the whole cluster for hours and even more. I guess that read request should include a kind *timeout *or *expired_at parameter* and handling thread will check it and stop processing after expiration time. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-8596) Display datacenter/rack info for offline nodes - PropertyFileSnitch
[ https://issues.apache.org/jira/browse/CASSANDRA-8596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Yudovin updated CASSANDRA-8596: Status: Patch Available (was: Open) > Display datacenter/rack info for offline nodes - PropertyFileSnitch > --- > > Key: CASSANDRA-8596 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8596 > Project: Cassandra > Issue Type: Improvement >Reporter: Vladimir Yudovin >Priority: Minor > Attachments: ByteBufferUtils.diff, file_snitch.patch > > > When using GossipPropertyFileSnitch "nodetool status" shows default (from > cassandra-topology.properties ) datacenter/rack for offline nodes. > It happens because offline nodes are not in endpointMap, and thus > getRawEndpointInfo returns default DC/rack is returned > (PropertyFileSnitch.java). > I suggest to take info for those nodes from system.peers tables - just like > SELECT data_center,rack FROM system.peers WHERE peer='10.0.0.1' > Patch attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-8596) Display datacenter/rack info for offline nodes - PropertyFileSnitch
[ https://issues.apache.org/jira/browse/CASSANDRA-8596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Yudovin updated CASSANDRA-8596: Flags: Patch Attachment: file_snitch.patch -AbstractEndpointSnitch might be a better choice This class has no getDC/Rack methods. AbstractNetworkTopologySnitch has, but different snitches have their own implementations, like EC2Snitch. I uploaded new patch *file_snitch.patch*, with simpler implementation, like EC2Snitch. > Display datacenter/rack info for offline nodes - PropertyFileSnitch > --- > > Key: CASSANDRA-8596 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8596 > Project: Cassandra > Issue Type: Improvement >Reporter: Vladimir Yudovin >Priority: Minor > Attachments: ByteBufferUtils.diff, file_snitch.patch > > > When using GossipPropertyFileSnitch "nodetool status" shows default (from > cassandra-topology.properties ) datacenter/rack for offline nodes. > It happens because offline nodes are not in endpointMap, and thus > getRawEndpointInfo returns default DC/rack is returned > (PropertyFileSnitch.java). > I suggest to take info for those nodes from system.peers tables - just like > SELECT data_center,rack FROM system.peers WHERE peer='10.0.0.1' > Patch attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-12971) Add CAS option to WRITE test to stress tool
[ https://issues.apache.org/jira/browse/CASSANDRA-12971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Yudovin updated CASSANDRA-12971: - Status: Patch Available (was: Open) > Add CAS option to WRITE test to stress tool > --- > > Key: CASSANDRA-12971 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12971 > Project: Cassandra > Issue Type: New Feature > Components: Stress, Tools >Reporter: Vladimir Yudovin >Assignee: Vladimir Yudovin > Attachments: stress-cass.patch > > > If -cas option is present each UPDATE is performed with true IF condition, > thus data is inserted anyway. > It's implemented, if it's needed I proceed with the patch. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-12971) Add CAS option to WRITE test to stress tool
[ https://issues.apache.org/jira/browse/CASSANDRA-12971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Yudovin updated CASSANDRA-12971: - Flags: Patch Attachment: stress-cass.patch Merges in 3.11 and trunk > Add CAS option to WRITE test to stress tool > --- > > Key: CASSANDRA-12971 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12971 > Project: Cassandra > Issue Type: New Feature > Components: Stress, Tools >Reporter: Vladimir Yudovin >Assignee: Vladimir Yudovin > Attachments: stress-cass.patch > > > If -cas option is present each UPDATE is performed with true IF condition, > thus data is inserted anyway. > It's implemented, if it's needed I proceed with the patch. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-12972) Print stress-tool output header about each 30 secs.
[ https://issues.apache.org/jira/browse/CASSANDRA-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086891#comment-16086891 ] Vladimir Yudovin edited comment on CASSANDRA-12972 at 7/14/17 6:03 AM: --- Patch attached, actually it can be applied to 3.0 (with path change), 3.11 and trunk as well. was (Author: vovodroid): Patch attached, actually it can be applied to 3.0, 3.11 and trunk as well. > Print stress-tool output header about each 30 secs. > --- > > Key: CASSANDRA-12972 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12972 > Project: Cassandra > Issue Type: Improvement > Components: Stress, Tools >Reporter: Vladimir Yudovin >Assignee: Vladimir Yudovin >Priority: Minor > Labels: lhf > Attachments: 3.11.patch > > > Currently header with columns meaning is printed only on test beginning. If > test is long it's not handy to interpret rows with numbers only. > I propose to repeatably print headers each half-minute or so. > Patch is available, is this improvement needed? > Thanks. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-12972) Print stress-tool output header about each 30 secs.
[ https://issues.apache.org/jira/browse/CASSANDRA-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Yudovin updated CASSANDRA-12972: - Summary: Print stress-tool output header about each 30 secs. (was: Print stress-tool ouput header about each 30 secs.) > Print stress-tool output header about each 30 secs. > --- > > Key: CASSANDRA-12972 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12972 > Project: Cassandra > Issue Type: Improvement > Components: Stress, Tools >Reporter: Vladimir Yudovin >Assignee: Vladimir Yudovin >Priority: Minor > Labels: lhf > Attachments: 3.11.patch > > > Currently header with columns meaning is printed only on test beginning. If > test is long it's not handy to interpret rows with numbers only. > I propose to repeatably print headers each half-minute or so. > Patch is available, is this improvement needed? > Thanks. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-12972) Print stress-tool ouput header about each 30 secs.
[ https://issues.apache.org/jira/browse/CASSANDRA-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Yudovin updated CASSANDRA-12972: - Attachment: 3.11.patch > Print stress-tool ouput header about each 30 secs. > -- > > Key: CASSANDRA-12972 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12972 > Project: Cassandra > Issue Type: Improvement > Components: Stress, Tools >Reporter: Vladimir Yudovin >Assignee: Vladimir Yudovin >Priority: Minor > Labels: lhf > Attachments: 3.11.patch > > > Currently header with columns meaning is printed only on test beginning. If > test is long it's not handy to interpret rows with numbers only. > I propose to repeatably print headers each half-minute or so. > Patch is available, is this improvement needed? > Thanks. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-12972) Print stress-tool ouput header about each 30 secs.
[ https://issues.apache.org/jira/browse/CASSANDRA-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Yudovin updated CASSANDRA-12972: - Attachment: (was: 3.11.patch) > Print stress-tool ouput header about each 30 secs. > -- > > Key: CASSANDRA-12972 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12972 > Project: Cassandra > Issue Type: Improvement > Components: Stress, Tools >Reporter: Vladimir Yudovin >Assignee: Vladimir Yudovin >Priority: Minor > Labels: lhf > Attachments: 3.11.patch > > > Currently header with columns meaning is printed only on test beginning. If > test is long it's not handy to interpret rows with numbers only. > I propose to repeatably print headers each half-minute or so. > Patch is available, is this improvement needed? > Thanks. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-12972) Print stress-tool ouput header about each 30 secs.
[ https://issues.apache.org/jira/browse/CASSANDRA-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Yudovin updated CASSANDRA-12972: - Status: Patch Available (was: Open) > Print stress-tool ouput header about each 30 secs. > -- > > Key: CASSANDRA-12972 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12972 > Project: Cassandra > Issue Type: Improvement > Components: Stress, Tools >Reporter: Vladimir Yudovin >Assignee: Vladimir Yudovin >Priority: Minor > Labels: lhf > Attachments: 3.11.patch > > > Currently header with columns meaning is printed only on test beginning. If > test is long it's not handy to interpret rows with numbers only. > I propose to repeatably print headers each half-minute or so. > Patch is available, is this improvement needed? > Thanks. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-12972) Print stress-tool ouput header about each 30 secs.
[ https://issues.apache.org/jira/browse/CASSANDRA-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Yudovin updated CASSANDRA-12972: - Flags: Patch Attachment: 3.11.patch Patch attached, actually it can be applied to 3.0, 3.11 and trunk as well. > Print stress-tool ouput header about each 30 secs. > -- > > Key: CASSANDRA-12972 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12972 > Project: Cassandra > Issue Type: Improvement > Components: Stress, Tools >Reporter: Vladimir Yudovin >Assignee: Vladimir Yudovin >Priority: Minor > Labels: lhf > Attachments: 3.11.patch > > > Currently header with columns meaning is printed only on test beginning. If > test is long it's not handy to interpret rows with numbers only. > I propose to repeatably print headers each half-minute or so. > Patch is available, is this improvement needed? > Thanks. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-12972) Print stress-tool ouput header about each 30 secs.
[ https://issues.apache.org/jira/browse/CASSANDRA-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082648#comment-16082648 ] Vladimir Yudovin commented on CASSANDRA-12972: -- For which branch supply patch - 3.11 or trunk? > Print stress-tool ouput header about each 30 secs. > -- > > Key: CASSANDRA-12972 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12972 > Project: Cassandra > Issue Type: Improvement > Components: Stress, Tools >Reporter: Vladimir Yudovin >Assignee: Vladimir Yudovin >Priority: Minor > Labels: lhf > > Currently header with columns meaning is printed only on test beginning. If > test is long it's not handy to interpret rows with numbers only. > I propose to repeatably print headers each half-minute or so. > Patch is available, is this improvement needed? > Thanks. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-12972) Print stress-tool ouput header about each 30 secs.
[ https://issues.apache.org/jira/browse/CASSANDRA-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Yudovin updated CASSANDRA-12972: - Description: Currently header with columns meaning is printed only on test beginning. If test is long it's not handy to interpret rows with numbers only. I propose to repeatably print headers each half-minute or so. Patch is available, is this improvement needed? Thanks. was: Currently header with columns meaning is printed only on test beginning. If test is long it's not handy to interpret rows with numbers only. I propose to repeatably print headers each half-minute or so. Path is available, is this improvement needed? Thanks. > Print stress-tool ouput header about each 30 secs. > -- > > Key: CASSANDRA-12972 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12972 > Project: Cassandra > Issue Type: Improvement > Components: Stress, Tools >Reporter: Vladimir Yudovin >Assignee: Vladimir Yudovin >Priority: Minor > Labels: lhf > > Currently header with columns meaning is printed only on test beginning. If > test is long it's not handy to interpret rows with numbers only. > I propose to repeatably print headers each half-minute or so. > Patch is available, is this improvement needed? > Thanks. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13079) Repair doesn't work after several replication factor changes
[
https://issues.apache.org/jira/browse/CASSANDRA-13079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15794367#comment-15794367
]
Vladimir Yudovin commented on CASSANDRA-13079:
--
"Increased" should also include adding new DC (no matter existing or new) for
replication , even if current factor for other DC is decreased, so total sum if
unchanged or even decreased.
May be for simplicity we can reset repair state on any replication factor or
class change. It's not often operation, besides maybe system_auth, but it's
usually small keyspace.
> Repair doesn't work after several replication factor changes
>
>
> Key: CASSANDRA-13079
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13079
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: Debian
>Reporter: Vladimir Yudovin
>Priority: Critical
>
> Scenario:
> Start two nodes cluster.
> Create keyspace with rep.factor *one*:
> CREATE KEYSPACE rep WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': 1};
> CREATE TABLE rep.data (str text PRIMARY KEY );
> INSERT INTO rep.data (str) VALUES ( 'qwerty');
> Run *nodetool flush* on all nodes. On one of them table files are created.
> Change replication factor to *two*:
> ALTER KEYSPACE rep WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': 2};
> Run repair, then *nodetool flush* on all nodes. On all nodes table files are
> created.
> Change replication factor to *one*:
> ALTER KEYSPACE rep WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': 1};
> Then *nodetool cleanup*, only on initial node remained data files.
> Change replication factor to *two* again:
> ALTER KEYSPACE rep WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': 2};
> Run repair, then *nodetool flush* on all nodes. No data files on second node
> (though expected, as after first repair/flush).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-13079) Repair doesn't work after several replication factor changes
[
https://issues.apache.org/jira/browse/CASSANDRA-13079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15780332#comment-15780332
]
Vladimir Yudovin commented on CASSANDRA-13079:
--
Well, indeed, --full helps.
And this rise a question - shouldn't replication factor change also reset
repair state for this keyspace?
> Repair doesn't work after several replication factor changes
>
>
> Key: CASSANDRA-13079
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13079
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: Debian
>Reporter: Vladimir Yudovin
>Priority: Critical
>
> Scenario:
> Start two nodes cluster.
> Create keyspace with rep.factor *one*:
> CREATE KEYSPACE rep WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': 1};
> CREATE TABLE rep.data (str text PRIMARY KEY );
> INSERT INTO rep.data (str) VALUES ( 'qwerty');
> Run *nodetool flush* on all nodes. On one of them table files are created.
> Change replication factor to *two*:
> ALTER KEYSPACE rep WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': 2};
> Run repair, then *nodetool flush* on all nodes. On all nodes table files are
> created.
> Change replication factor to *one*:
> ALTER KEYSPACE rep WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': 1};
> Then *nodetool cleanup*, only on initial node remained data files.
> Change replication factor to *two* again:
> ALTER KEYSPACE rep WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': 2};
> Run repair, then *nodetool flush* on all nodes. No data files on second node
> (though expected, as after first repair/flush).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CASSANDRA-13079) Repair doesn't work after several replication factor changes
Vladimir Yudovin created CASSANDRA-13079:
Summary: Repair doesn't work after several replication factor
changes
Key: CASSANDRA-13079
URL: https://issues.apache.org/jira/browse/CASSANDRA-13079
Project: Cassandra
Issue Type: Bug
Components: Core
Environment: Debian
Reporter: Vladimir Yudovin
Priority: Critical
Scenario:
Start two nodes cluster.
Create keyspace with rep.factor *one*:
CREATE KEYSPACE rep WITH replication = {'class': 'SimpleStrategy',
'replication_factor': 1};
CREATE TABLE rep.data (str text PRIMARY KEY );
INSERT INTO rep.data (str) VALUES ( 'qwerty');
Run *nodetool flush* on all nodes. On one of them table files are created.
Change replication factor to *two*:
ALTER KEYSPACE rep WITH replication = {'class': 'SimpleStrategy',
'replication_factor': 2};
Run repair, then *nodetool flush* on all nodes. On all nodes table files are
created.
Change replication factor to *one*:
ALTER KEYSPACE rep WITH replication = {'class': 'SimpleStrategy',
'replication_factor': 1};
Then *nodetool cleanup*, only on initial node remained data files.
Change replication factor to *two* again:
ALTER KEYSPACE rep WITH replication = {'class': 'SimpleStrategy',
'replication_factor': 2};
Run repair, then *nodetool flush* on all nodes. No data files on second node
(though expected, as after first repair/flush).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12624) Add cassandra.yaml overlay capabilities (can issue pull request now)
[ https://issues.apache.org/jira/browse/CASSANDRA-12624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15715234#comment-15715234 ] Vladimir Yudovin commented on CASSANDRA-12624: -- Hi Craig, there are some fields that contradict one to another and can't be used simultaneously, e.g. listen_address and listen_interface. If one of them is set in main file and other in overlay Cassandra start will fail. Such exclusion should be handled individually. Also I used simpler approach for CASSANDRA-12970, simple concatenation of YAML file in memory. Thus new values overrides old ones. May be we can combine our solutions in some way. > Add cassandra.yaml overlay capabilities (can issue pull request now) > > > Key: CASSANDRA-12624 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12624 > Project: Cassandra > Issue Type: Improvement > Components: Configuration > Environment: OSX but should work on any OS. >Reporter: Craig McConomy >Priority: Minor > Labels: configuration, configuration-addition > Fix For: 3.x > > Original Estimate: 0h > Remaining Estimate: 0h > > Adds a new file "conf/cassandra-overlay.yaml" that can contain any settings > found in cassandra.yaml. Any settings, if found, override whatever is found > in cassandra.yaml > A different overlay file can be specified using > -Dcassandra.config.overlay=your_file_name > Overlay processing can be disabled with > -Dcassandra.config.overlay.disable=true > Rationale: When administering cassandra nodes, I have found it quite common > to want to distribute a common "golden" cassandra.yaml. This is challenging > where you have a configuration value or two that needs to be modified per > node. In this case, ops needs to know which lines of cassandra.yaml to ignore > (because it's the same on all nodes) so that they can focus on what's > uniquely configured for a particular node. > By specifying an additional overlay file, cassandra admins have the > flexibility to decide what is configured on a per-node basis, and can make it > extremely clear. > Source can be found in > https://github.com/cmcconomy/cassandra/tree/config-overlay -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CASSANDRA-12974) Stress-tool: print total operation rate on each row.
Vladimir Yudovin created CASSANDRA-12974: Summary: Stress-tool: print total operation rate on each row. Key: CASSANDRA-12974 URL: https://issues.apache.org/jira/browse/CASSANDRA-12974 Project: Cassandra Issue Type: Improvement Components: Tools Reporter: Vladimir Yudovin Assignee: Vladimir Yudovin Priority: Minor Now operation rate is printed for latest second, value that can fluctuate and hard to estimate from the glance. For more handy usage we can print total (from test starting) on each row. Patch is available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CASSANDRA-12973) Set amount of tables for stress-tool test
Vladimir Yudovin created CASSANDRA-12973: Summary: Set amount of tables for stress-tool test Key: CASSANDRA-12973 URL: https://issues.apache.org/jira/browse/CASSANDRA-12973 Project: Cassandra Issue Type: New Feature Components: Tools Reporter: Vladimir Yudovin Assignee: Vladimir Yudovin Currently all test are performed with single table standard1. It can be useful to allow setting any numbers of tables, for both WRITE and READ operations. Can go on with patch if this feature is needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CASSANDRA-12972) Print stress-tool ouput header about each 30 secs.
Vladimir Yudovin created CASSANDRA-12972: Summary: Print stress-tool ouput header about each 30 secs. Key: CASSANDRA-12972 URL: https://issues.apache.org/jira/browse/CASSANDRA-12972 Project: Cassandra Issue Type: Improvement Components: Tools Reporter: Vladimir Yudovin Assignee: Vladimir Yudovin Priority: Minor Currently header with columns meaning is printed only on test beginning. If test is long it's not handy to interpret rows with numbers only. I propose to repeatably print headers each half-minute or so. Path is available, is this improvement needed? Thanks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12970) Use conf.d style: combine cassandra.yaml with conf.d/*.yaml files
[ https://issues.apache.org/jira/browse/CASSANDRA-12970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Yudovin updated CASSANDRA-12970: - Summary: Use conf.d style: combine cassandra.yaml with conf.d/*.yaml files (was: Use conf.d style: combine cassandra.yaml with conf.d/*yaml files) > Use conf.d style: combine cassandra.yaml with conf.d/*.yaml files > - > > Key: CASSANDRA-12970 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12970 > Project: Cassandra > Issue Type: New Feature > Components: Configuration >Reporter: Vladimir Yudovin >Assignee: Vladimir Yudovin >Priority: Minor > > Read and merge main cassandra.yaml with YAMLs from folder conf/conf.d > First cassandra.yaml is read, than files from conf/conf.d are read in > alphabetical order. This allows handy creation/edit of host/deployment > specific configurations. > I already have implementation, if this feature is needed, I go on with patch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CASSANDRA-12971) Add CAS option to WRITE test to stress tool
Vladimir Yudovin created CASSANDRA-12971: Summary: Add CAS option to WRITE test to stress tool Key: CASSANDRA-12971 URL: https://issues.apache.org/jira/browse/CASSANDRA-12971 Project: Cassandra Issue Type: New Feature Components: Tools Reporter: Vladimir Yudovin Assignee: Vladimir Yudovin If -cas option is present each UPDATE is performed with true IF condition, thus data is inserted anyway. It's implemented, if it's needed I proceed with the patch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CASSANDRA-12970) Use conf.d style: combine cassandra.yaml with conf.d/*yaml files
Vladimir Yudovin created CASSANDRA-12970: Summary: Use conf.d style: combine cassandra.yaml with conf.d/*yaml files Key: CASSANDRA-12970 URL: https://issues.apache.org/jira/browse/CASSANDRA-12970 Project: Cassandra Issue Type: New Feature Components: Configuration Reporter: Vladimir Yudovin Assignee: Vladimir Yudovin Priority: Minor Read and merge main cassandra.yaml with YAMLs from folder conf/conf.d First cassandra.yaml is read, than files from conf/conf.d are read in alphabetical order. This allows handy creation/edit of host/deployment specific configurations. I already have implementation, if this feature is needed, I go on with patch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
