[jira] [Updated] (CASSANDRA-15281) help for clearsnapshot needs to be updated to indicate requirement for --all

2019-08-30 Thread Josh Turner (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Turner updated CASSANDRA-15281:

Attachment: 15281.trunk

> help for clearsnapshot needs to be updated to indicate requirement for --all
> 
>
> Key: CASSANDRA-15281
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15281
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tool/nodetool
>Reporter: DeepakVohra
>Assignee: Josh Turner
>Priority: Normal
> Fix For: 4.x
>
> Attachments: 15281.trunk
>
>
> According to _CASSANDRA-13391_
> _nodetool clearsnapshot should require --all to clear all snapshots_
> But the help for clearsnapshot does not indicate the same.
> {code:java}
> [ec2-user@ip-10-0-2-238 ~]$ nodetool help clearsnapshot
>  NAME nodetool clearsnapshot - Remove the snapshot with the given name from 
> the given keyspaces. If no snapshotName is specified we will remove all 
> snapshots{code}
> The help for clearsnapshot needs to be updated to indicate requirement for 
> --all to remove all snapshots.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-15281) help for clearsnapshot needs to be updated to indicate requirement for --all

2019-08-30 Thread Josh Turner (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Turner updated CASSANDRA-15281:

Test and Documentation Plan: Updated help message to match functionality.
 Status: Patch Available  (was: Open)

> help for clearsnapshot needs to be updated to indicate requirement for --all
> 
>
> Key: CASSANDRA-15281
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15281
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tool/nodetool
>Reporter: DeepakVohra
>Assignee: Josh Turner
>Priority: Normal
> Fix For: 4.x
>
> Attachments: 15281.trunk
>
>
> According to _CASSANDRA-13391_
> _nodetool clearsnapshot should require --all to clear all snapshots_
> But the help for clearsnapshot does not indicate the same.
> {code:java}
> [ec2-user@ip-10-0-2-238 ~]$ nodetool help clearsnapshot
>  NAME nodetool clearsnapshot - Remove the snapshot with the given name from 
> the given keyspaces. If no snapshotName is specified we will remove all 
> snapshots{code}
> The help for clearsnapshot needs to be updated to indicate requirement for 
> --all to remove all snapshots.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-15281) help for clearsnapshot needs to be updated to indicate requirement for --all

2019-08-30 Thread Josh Turner (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Turner updated CASSANDRA-15281:

Component/s: (was: CQL/Syntax)
 Tool/nodetool

> help for clearsnapshot needs to be updated to indicate requirement for --all
> 
>
> Key: CASSANDRA-15281
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15281
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tool/nodetool
>Reporter: DeepakVohra
>Assignee: Josh Turner
>Priority: Normal
> Fix For: 4.x
>
>
> According to _CASSANDRA-13391_
> _nodetool clearsnapshot should require --all to clear all snapshots_
> But the help for clearsnapshot does not indicate the same.
> {code:java}
> [ec2-user@ip-10-0-2-238 ~]$ nodetool help clearsnapshot
>  NAME nodetool clearsnapshot - Remove the snapshot with the given name from 
> the given keyspaces. If no snapshotName is specified we will remove all 
> snapshots{code}
> The help for clearsnapshot needs to be updated to indicate requirement for 
> --all to remove all snapshots.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-15281) help for clearsnapshot needs to be updated to indicate requirement for --all

2019-08-30 Thread Josh Turner (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Turner updated CASSANDRA-15281:

 Bug Category: Parent values: Code(13163)Level 1 values: Bug - Unclear 
Impact(13164)
   Complexity: Low Hanging Fruit
Discovered By: User Report
Fix Version/s: 4.x
 Severity: Low
   Status: Open  (was: Triage Needed)

> help for clearsnapshot needs to be updated to indicate requirement for --all
> 
>
> Key: CASSANDRA-15281
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15281
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL/Syntax
>Reporter: DeepakVohra
>Assignee: Josh Turner
>Priority: Normal
> Fix For: 4.x
>
>
> According to _CASSANDRA-13391_
> _nodetool clearsnapshot should require --all to clear all snapshots_
> But the help for clearsnapshot does not indicate the same.
> {code:java}
> [ec2-user@ip-10-0-2-238 ~]$ nodetool help clearsnapshot
>  NAME nodetool clearsnapshot - Remove the snapshot with the given name from 
> the given keyspaces. If no snapshotName is specified we will remove all 
> snapshots{code}
> The help for clearsnapshot needs to be updated to indicate requirement for 
> --all to remove all snapshots.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Assigned] (CASSANDRA-15281) help for clearsnapshot needs to be updated to indicate requirement for --all

2019-08-30 Thread Josh Turner (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Turner reassigned CASSANDRA-15281:
---

Assignee: Josh Turner

> help for clearsnapshot needs to be updated to indicate requirement for --all
> 
>
> Key: CASSANDRA-15281
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15281
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL/Syntax
>Reporter: DeepakVohra
>Assignee: Josh Turner
>Priority: Normal
>
> According to _CASSANDRA-13391_
> _nodetool clearsnapshot should require --all to clear all snapshots_
> But the help for clearsnapshot does not indicate the same.
> {code:java}
> [ec2-user@ip-10-0-2-238 ~]$ nodetool help clearsnapshot
>  NAME nodetool clearsnapshot - Remove the snapshot with the given name from 
> the given keyspaces. If no snapshotName is specified we will remove all 
> snapshots{code}
> The help for clearsnapshot needs to be updated to indicate requirement for 
> --all to remove all snapshots.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-15282) nodetool tablestats does not list bytes repaired/unrepaired

2019-08-26 Thread Josh Turner (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Turner updated CASSANDRA-15282:

Test and Documentation Plan: 
Improved UnitTest 
org.apache.cassandra.tools.nodetool.stats.TableStatsPrinterTest to include this 
feature in output check and ran it successfully. 

 
 Status: Patch Available  (was: Open)

> nodetool tablestats does not list bytes repaired/unrepaired
> ---
>
> Key: CASSANDRA-15282
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15282
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tool/nodetool
>Reporter: DeepakVohra
>Assignee: Josh Turner
>Priority: Normal
> Attachments: 15282.trunk
>
>
> According to _CASSANDRA-13774_
> _add bytes repaired/unrepaired in nodetool tablestats_
> But, only the percent is listed, and not the actual bytes with latest 4.0 
> build.
> {code:java}
> nodetool tablestats --sort local_read_count --top 3
> ...
> Percent repaired: 0.0
> ...{code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-15282) nodetool tablestats does not list bytes repaired/unrepaired

2019-08-26 Thread Josh Turner (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Turner updated CASSANDRA-15282:

Attachment: 15282.trunk

> nodetool tablestats does not list bytes repaired/unrepaired
> ---
>
> Key: CASSANDRA-15282
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15282
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tool/nodetool
>Reporter: DeepakVohra
>Assignee: Josh Turner
>Priority: Normal
> Attachments: 15282.trunk
>
>
> According to _CASSANDRA-13774_
> _add bytes repaired/unrepaired in nodetool tablestats_
> But, only the percent is listed, and not the actual bytes with latest 4.0 
> build.
> {code:java}
> nodetool tablestats --sort local_read_count --top 3
> ...
> Percent repaired: 0.0
> ...{code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Commented] (CASSANDRA-15282) nodetool tablestats does not list bytes repaired/unrepaired

2019-08-26 Thread Josh Turner (Jira)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-15282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916047#comment-16916047
 ] 

Josh Turner commented on CASSANDRA-15282:
-

Functionality got removed by CASSANDRA-13889. I've readded the code for this 
feature and updated TableStatsPrinterTest to account for this changed output.

 

> nodetool tablestats does not list bytes repaired/unrepaired
> ---
>
> Key: CASSANDRA-15282
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15282
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tool/nodetool
>Reporter: DeepakVohra
>Assignee: Josh Turner
>Priority: Normal
>
> According to _CASSANDRA-13774_
> _add bytes repaired/unrepaired in nodetool tablestats_
> But, only the percent is listed, and not the actual bytes with latest 4.0 
> build.
> {code:java}
> nodetool tablestats --sort local_read_count --top 3
> ...
> Percent repaired: 0.0
> ...{code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Assigned] (CASSANDRA-15282) nodetool tablestats does not list bytes repaired/unrepaired

2019-08-26 Thread Josh Turner (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Turner reassigned CASSANDRA-15282:
---

Assignee: Josh Turner

> nodetool tablestats does not list bytes repaired/unrepaired
> ---
>
> Key: CASSANDRA-15282
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15282
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tool/nodetool
>Reporter: DeepakVohra
>Assignee: Josh Turner
>Priority: Normal
>
> According to _CASSANDRA-13774_
> _add bytes repaired/unrepaired in nodetool tablestats_
> But, only the percent is listed, and not the actual bytes with latest 4.0 
> build.
> {code:java}
> nodetool tablestats --sort local_read_count --top 3
> ...
> Percent repaired: 0.0
> ...{code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-15282) nodetool tablestats does not list bytes repaired/unrepaired

2019-08-26 Thread Josh Turner (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Turner updated CASSANDRA-15282:

 Bug Category: Parent values: Code(13163)Level 1 values: Bug - Unclear 
Impact(13164)
   Complexity: Low Hanging Fruit
Discovered By: User Report
 Severity: Low
   Status: Open  (was: Triage Needed)

> nodetool tablestats does not list bytes repaired/unrepaired
> ---
>
> Key: CASSANDRA-15282
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15282
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tool/nodetool
>Reporter: DeepakVohra
>Priority: Normal
>
> According to _CASSANDRA-13774_
> _add bytes repaired/unrepaired in nodetool tablestats_
> But, only the percent is listed, and not the actual bytes with latest 4.0 
> build.
> {code:java}
> nodetool tablestats --sort local_read_count --top 3
> ...
> Percent repaired: 0.0
> ...{code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-15283) nodetool statushandoff does not list max hint window

2019-08-22 Thread Josh Turner (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Turner updated CASSANDRA-15283:

Resolution: Information Provided
Status: Resolved  (was: Triage Needed)

> nodetool statushandoff does not list max hint window
> 
>
> Key: CASSANDRA-15283
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15283
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tool/nodetool
>Reporter: DeepakVohra
>Priority: Normal
>
> According to _CASSANDRA-13728_
> _Provide max hint window as part of nodetool_
> the nodetool statushandoff should list max hint window.
> But, with latest 4.0 build the output is still the same as before.
> {code:java}
> nodetool statushandoff
> Hinted handoff is running{code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Assigned] (CASSANDRA-15283) nodetool statushandoff does not list max hint window

2019-08-22 Thread Josh Turner (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Turner reassigned CASSANDRA-15283:
---

Assignee: Josh Turner

> nodetool statushandoff does not list max hint window
> 
>
> Key: CASSANDRA-15283
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15283
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tool/nodetool
>Reporter: DeepakVohra
>Assignee: Josh Turner
>Priority: Normal
>
> According to _CASSANDRA-13728_
> _Provide max hint window as part of nodetool_
> the nodetool statushandoff should list max hint window.
> But, with latest 4.0 build the output is still the same as before.
> {code:java}
> nodetool statushandoff
> Hinted handoff is running{code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Commented] (CASSANDRA-15283) nodetool statushandoff does not list max hint window

2019-08-22 Thread Josh Turner (Jira)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-15283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16913534#comment-16913534
 ] 

Josh Turner commented on CASSANDRA-15283:
-

It looks like CASSANDRA-13728 placed this as a new command of nodetool 
handoffwindow which does work as desired in the trunk.
{code:java}
bin/nodetool handoffwindow
Hinted handoff window is 1080
{code}
In discussion of that ticket it was decided to add a new option instead of 
modifying the existing to avoid breaking automations that may already be in 
place. See this comment:  
https://issues.apache.org/jira/browse/CASSANDRA-13728?focusedCommentId=16131474=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16131474

 

> nodetool statushandoff does not list max hint window
> 
>
> Key: CASSANDRA-15283
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15283
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tool/nodetool
>Reporter: DeepakVohra
>Priority: Normal
>
> According to _CASSANDRA-13728_
> _Provide max hint window as part of nodetool_
> the nodetool statushandoff should list max hint window.
> But, with latest 4.0 build the output is still the same as before.
> {code:java}
> nodetool statushandoff
> Hinted handoff is running{code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-15287) Inaccurate exception message with nodetool snapshot

2019-08-22 Thread Josh Turner (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Turner updated CASSANDRA-15287:

Test and Documentation Plan: 
Reproduced error message:

 
{code:java}
bin/cqlsh << EOF
CREATE KEYSPACE k1 WITH replication = {'class': 'SimpleStrategy', 
'replication_factor': '1'} AND durable_writes = true;

CREATE TABLE k1.t2 (
id uuid PRIMARY KEY,
val text
);

CREATE TABLE k1.t1 (
id uuid PRIMARY KEY,
val text
);
EOF

bin/nodetool snapshot --kt-list k1.t1,k1.t2 --k1
{code}
 

 

Before Patch:

 
{code:java}
error: When specifying the Keyspace columfamily list for a snapshot, you should 
not specify columnfamilyerror: When specifying the Keyspace columfamily list 
for a snapshot, you should not specify columnfamily
-- StackTrace --
java.io.IOException: When specifying the Keyspace columfamily list for a 
snapshot, you should not specify columnfamily at 
org.apache.cassandra.tools.nodetool.Snapshot.execute(Snapshot.java:73) at 
org.apache.cassandra.tools.NodeTool$NodeToolCmd.run(NodeTool.java:307) at 
org.apache.cassandra.tools.NodeTool.main(NodeTool.java:218)
{code}
 

 

After Patch:

 
{code:java}
error: When specifying the Keyspace columfamily list for a snapshot, you should 
not specify keyspaceerror: When specifying the Keyspace columfamily list for a 
snapshot, you should not specify keyspace
-- StackTrace --
java.io.IOException: When specifying the Keyspace columfamily list for a 
snapshot, you should not specify keyspace at 
org.apache.cassandra.tools.nodetool.Snapshot.execute(Snapshot.java:73) at 
org.apache.cassandra.tools.NodeTool$NodeToolCmd.run(NodeTool.java:307) at 
org.apache.cassandra.tools.NodeTool.main(NodeTool.java:218)
{code}
 

 
 Status: Patch Available  (was: Open)

> Inaccurate exception message with nodetool snapshot 
> 
>
> Key: CASSANDRA-15287
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15287
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tool/nodetool
>Reporter: DeepakVohra
>Assignee: Josh Turner
>Priority: Normal
> Attachments: 15287.trunk, 15287.trunk.withchanges
>
>
> 1. Create a keyspace _cqlkeyspace_ (arbitrary name)
> 2. Create two tables (t1 and  t2)
> 3. Run _nodetool snapshot_ to create snapshot for multiple tables in same 
> command. Include the keyspace name as argument (which is not what the command 
> syntax allows)
> {code:java}
> nodetool snapshot --kt-list cqlkeyspace.t1,cqlkeyspace.t2 --tag multi-table   
> --cqlkeyspace
> {code}
> 4. Exception message is inaccurate in that it is referring to columnfamily 
> when it should be referring to keyspace.
> {code:java}
> java.io.IOException: When specifying the Keyspace columfamily list for a 
> snapshot, you should not specify columnfamily
> {code}
> Exception message should be:
> {code:java}
> java.io.IOException: When specifying the Keyspace columfamily list for a 
> snapshot, you should not specify keyspace
> {code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Commented] (CASSANDRA-15287) Inaccurate exception message with nodetool snapshot

2019-08-22 Thread Josh Turner (Jira)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-15287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16913424#comment-16913424
 ] 

Josh Turner commented on CASSANDRA-15287:
-

Confirmed the bug and see that it originated in Cassandra 2.2. The 15287.trunk 
patch applies cleanly to 2.2, 3.0, 3.11, and trunk. I've split the patch in two 
files as I'm not sure the proper version to modify for CHANGES.txt. 

> Inaccurate exception message with nodetool snapshot 
> 
>
> Key: CASSANDRA-15287
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15287
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tool/nodetool
>Reporter: DeepakVohra
>Assignee: Josh Turner
>Priority: Normal
> Attachments: 15287.trunk, 15287.trunk.withchanges
>
>
> 1. Create a keyspace _cqlkeyspace_ (arbitrary name)
> 2. Create two tables (t1 and  t2)
> 3. Run _nodetool snapshot_ to create snapshot for multiple tables in same 
> command. Include the keyspace name as argument (which is not what the command 
> syntax allows)
> {code:java}
> nodetool snapshot --kt-list cqlkeyspace.t1,cqlkeyspace.t2 --tag multi-table   
> --cqlkeyspace
> {code}
> 4. Exception message is inaccurate in that it is referring to columnfamily 
> when it should be referring to keyspace.
> {code:java}
> java.io.IOException: When specifying the Keyspace columfamily list for a 
> snapshot, you should not specify columnfamily
> {code}
> Exception message should be:
> {code:java}
> java.io.IOException: When specifying the Keyspace columfamily list for a 
> snapshot, you should not specify keyspace
> {code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-15287) Inaccurate exception message with nodetool snapshot

2019-08-22 Thread Josh Turner (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Turner updated CASSANDRA-15287:

Attachment: 15287.trunk.withchanges
15287.trunk

> Inaccurate exception message with nodetool snapshot 
> 
>
> Key: CASSANDRA-15287
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15287
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tool/nodetool
>Reporter: DeepakVohra
>Assignee: Josh Turner
>Priority: Normal
> Attachments: 15287.trunk, 15287.trunk.withchanges
>
>
> 1. Create a keyspace _cqlkeyspace_ (arbitrary name)
> 2. Create two tables (t1 and  t2)
> 3. Run _nodetool snapshot_ to create snapshot for multiple tables in same 
> command. Include the keyspace name as argument (which is not what the command 
> syntax allows)
> {code:java}
> nodetool snapshot --kt-list cqlkeyspace.t1,cqlkeyspace.t2 --tag multi-table   
> --cqlkeyspace
> {code}
> 4. Exception message is inaccurate in that it is referring to columnfamily 
> when it should be referring to keyspace.
> {code:java}
> java.io.IOException: When specifying the Keyspace columfamily list for a 
> snapshot, you should not specify columnfamily
> {code}
> Exception message should be:
> {code:java}
> java.io.IOException: When specifying the Keyspace columfamily list for a 
> snapshot, you should not specify keyspace
> {code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-15287) Inaccurate exception message with nodetool snapshot

2019-08-22 Thread Josh Turner (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Turner updated CASSANDRA-15287:

Attachment: 15287.trunk
15287.trunk.withchanges

> Inaccurate exception message with nodetool snapshot 
> 
>
> Key: CASSANDRA-15287
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15287
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tool/nodetool
>Reporter: DeepakVohra
>Assignee: Josh Turner
>Priority: Normal
>
> 1. Create a keyspace _cqlkeyspace_ (arbitrary name)
> 2. Create two tables (t1 and  t2)
> 3. Run _nodetool snapshot_ to create snapshot for multiple tables in same 
> command. Include the keyspace name as argument (which is not what the command 
> syntax allows)
> {code:java}
> nodetool snapshot --kt-list cqlkeyspace.t1,cqlkeyspace.t2 --tag multi-table   
> --cqlkeyspace
> {code}
> 4. Exception message is inaccurate in that it is referring to columnfamily 
> when it should be referring to keyspace.
> {code:java}
> java.io.IOException: When specifying the Keyspace columfamily list for a 
> snapshot, you should not specify columnfamily
> {code}
> Exception message should be:
> {code:java}
> java.io.IOException: When specifying the Keyspace columfamily list for a 
> snapshot, you should not specify keyspace
> {code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-15287) Inaccurate exception message with nodetool snapshot

2019-08-22 Thread Josh Turner (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Turner updated CASSANDRA-15287:

Attachment: (was: 15287.trunk)

> Inaccurate exception message with nodetool snapshot 
> 
>
> Key: CASSANDRA-15287
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15287
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tool/nodetool
>Reporter: DeepakVohra
>Assignee: Josh Turner
>Priority: Normal
>
> 1. Create a keyspace _cqlkeyspace_ (arbitrary name)
> 2. Create two tables (t1 and  t2)
> 3. Run _nodetool snapshot_ to create snapshot for multiple tables in same 
> command. Include the keyspace name as argument (which is not what the command 
> syntax allows)
> {code:java}
> nodetool snapshot --kt-list cqlkeyspace.t1,cqlkeyspace.t2 --tag multi-table   
> --cqlkeyspace
> {code}
> 4. Exception message is inaccurate in that it is referring to columnfamily 
> when it should be referring to keyspace.
> {code:java}
> java.io.IOException: When specifying the Keyspace columfamily list for a 
> snapshot, you should not specify columnfamily
> {code}
> Exception message should be:
> {code:java}
> java.io.IOException: When specifying the Keyspace columfamily list for a 
> snapshot, you should not specify keyspace
> {code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-15287) Inaccurate exception message with nodetool snapshot

2019-08-22 Thread Josh Turner (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Turner updated CASSANDRA-15287:

Attachment: (was: 15287.trunk.withchanges)

> Inaccurate exception message with nodetool snapshot 
> 
>
> Key: CASSANDRA-15287
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15287
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tool/nodetool
>Reporter: DeepakVohra
>Assignee: Josh Turner
>Priority: Normal
>
> 1. Create a keyspace _cqlkeyspace_ (arbitrary name)
> 2. Create two tables (t1 and  t2)
> 3. Run _nodetool snapshot_ to create snapshot for multiple tables in same 
> command. Include the keyspace name as argument (which is not what the command 
> syntax allows)
> {code:java}
> nodetool snapshot --kt-list cqlkeyspace.t1,cqlkeyspace.t2 --tag multi-table   
> --cqlkeyspace
> {code}
> 4. Exception message is inaccurate in that it is referring to columnfamily 
> when it should be referring to keyspace.
> {code:java}
> java.io.IOException: When specifying the Keyspace columfamily list for a 
> snapshot, you should not specify columnfamily
> {code}
> Exception message should be:
> {code:java}
> java.io.IOException: When specifying the Keyspace columfamily list for a 
> snapshot, you should not specify keyspace
> {code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-15287) Inaccurate exception message with nodetool snapshot

2019-08-22 Thread Josh Turner (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Turner updated CASSANDRA-15287:

 Bug Category: Parent values: Code(13163)Level 1 values: Bug - Unclear 
Impact(13164)
   Complexity: Low Hanging Fruit
Discovered By: User Report
 Severity: Low
   Status: Open  (was: Triage Needed)

> Inaccurate exception message with nodetool snapshot 
> 
>
> Key: CASSANDRA-15287
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15287
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tool/nodetool
>Reporter: DeepakVohra
>Assignee: Josh Turner
>Priority: Normal
>
> 1. Create a keyspace _cqlkeyspace_ (arbitrary name)
> 2. Create two tables (t1 and  t2)
> 3. Run _nodetool snapshot_ to create snapshot for multiple tables in same 
> command. Include the keyspace name as argument (which is not what the command 
> syntax allows)
> {code:java}
> nodetool snapshot --kt-list cqlkeyspace.t1,cqlkeyspace.t2 --tag multi-table   
> --cqlkeyspace
> {code}
> 4. Exception message is inaccurate in that it is referring to columnfamily 
> when it should be referring to keyspace.
> {code:java}
> java.io.IOException: When specifying the Keyspace columfamily list for a 
> snapshot, you should not specify columnfamily
> {code}
> Exception message should be:
> {code:java}
> java.io.IOException: When specifying the Keyspace columfamily list for a 
> snapshot, you should not specify keyspace
> {code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Assigned] (CASSANDRA-15287) Inaccurate exception message with nodetool snapshot

2019-08-22 Thread Josh Turner (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Turner reassigned CASSANDRA-15287:
---

Assignee: Josh Turner

> Inaccurate exception message with nodetool snapshot 
> 
>
> Key: CASSANDRA-15287
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15287
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tool/nodetool
>Reporter: DeepakVohra
>Assignee: Josh Turner
>Priority: Normal
>
> 1. Create a keyspace _cqlkeyspace_ (arbitrary name)
> 2. Create two tables (t1 and  t2)
> 3. Run _nodetool snapshot_ to create snapshot for multiple tables in same 
> command. Include the keyspace name as argument (which is not what the command 
> syntax allows)
> {code:java}
> nodetool snapshot --kt-list cqlkeyspace.t1,cqlkeyspace.t2 --tag multi-table   
> --cqlkeyspace
> {code}
> 4. Exception message is inaccurate in that it is referring to columnfamily 
> when it should be referring to keyspace.
> {code:java}
> java.io.IOException: When specifying the Keyspace columfamily list for a 
> snapshot, you should not specify columnfamily
> {code}
> Exception message should be:
> {code:java}
> java.io.IOException: When specifying the Keyspace columfamily list for a 
> snapshot, you should not specify keyspace
> {code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Commented] (CASSANDRA-15186) InternodeOutboundMetrics overloaded bytes/count mixup

2019-08-21 Thread Josh Turner (Jira)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-15186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16912693#comment-16912693
 ] 

Josh Turner commented on CASSANDRA-15186:
-

Attached a simple patch correcting this mixup.

> InternodeOutboundMetrics overloaded bytes/count mixup
> -
>
> Key: CASSANDRA-15186
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15186
> Project: Cassandra
>  Issue Type: Bug
>  Components: Observability/Metrics
>Reporter: Marcus Olsson
>Priority: Normal
> Attachments: 15186-trunk.txt
>
>
> In 
> [https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/metrics/InternodeOutboundMetrics.java]
>  there is a small mixup between overloaded count and bytes, in 
> [LargeMessageDroppedTasksDueToOverload|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/metrics/InternodeOutboundMetrics.java#L129]
>  and 
> [UrgentMessageDroppedTasksDueToOverload|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/metrics/InternodeOutboundMetrics.java#L151].



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-15186) InternodeOutboundMetrics overloaded bytes/count mixup

2019-08-21 Thread Josh Turner (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Turner updated CASSANDRA-15186:

Attachment: 15186-trunk.txt

> InternodeOutboundMetrics overloaded bytes/count mixup
> -
>
> Key: CASSANDRA-15186
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15186
> Project: Cassandra
>  Issue Type: Bug
>  Components: Observability/Metrics
>Reporter: Marcus Olsson
>Priority: Normal
> Attachments: 15186-trunk.txt
>
>
> In 
> [https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/metrics/InternodeOutboundMetrics.java]
>  there is a small mixup between overloaded count and bytes, in 
> [LargeMessageDroppedTasksDueToOverload|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/metrics/InternodeOutboundMetrics.java#L129]
>  and 
> [UrgentMessageDroppedTasksDueToOverload|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/metrics/InternodeOutboundMetrics.java#L151].



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org