[jira] [Updated] (CASSANDRA-7238) Nodetool Status performance is much slower with VNodes On

2016-01-27 Thread Paulo Motta (JIRA) 

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

Paulo Motta updated CASSANDRA-7238:
---
Reproduced In: 2.1 beta2, 2.0.8  (was: 2.0.8, 2.1 beta2)
 Reviewer: Paulo Motta

> Nodetool Status performance is much slower with VNodes On
> -
>
> Key: CASSANDRA-7238
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7238
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
> Environment: 1000 M1.Large Ubuntu 12.04
>Reporter: Russell Alexander Spitzer
>Assignee: Yuki Morishita
>Priority: Minor
> Fix For: 2.1.x, 2.2.x, 3.0.x, 3.x
>
>
> Nodetool status on a 1000 Node cluster without vnodes returns in several 
> seconds. With vnodes on (256) there are OOM errors with the default XMX of 
> 32. Adjusting the XMX to 128 allows nodetool status to complete but the 
> execution takes roughly 10 minutes.
> Tested
> {code}
> XMX|  Status
> 32 |OOM
> 64 |OOM: GC Overhead
> 128|Finishes in ~10 minutes
> 500|Finishes in ~10 minutes
> 1000   |Finishes in ~10 minutes
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-7238) Nodetool Status performance is much slower with VNodes On

2015-08-24 Thread Jonathan Ellis (JIRA) 

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

Jonathan Ellis updated CASSANDRA-7238:
--
Assignee: Philip Thompson

> Nodetool Status performance is much slower with VNodes On
> -
>
> Key: CASSANDRA-7238
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7238
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
> Environment: 1000 M1.Large Ubuntu 12.04
>Reporter: Russell Alexander Spitzer
>Assignee: Philip Thompson
>Priority: Minor
> Fix For: 2.0.x
>
>
> Nodetool status on a 1000 Node cluster without vnodes returns in several 
> seconds. With vnodes on (256) there are OOM errors with the default XMX of 
> 32. Adjusting the XMX to 128 allows nodetool status to complete but the 
> execution takes roughly 10 minutes.
> Tested
> {code}
> XMX|  Status
> 32 |OOM
> 64 |OOM: GC Overhead
> 128|Finishes in ~10 minutes
> 500|Finishes in ~10 minutes
> 1000   |Finishes in ~10 minutes
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-7238) Nodetool Status performance is much slower with VNodes On

2015-01-20 Thread T Jake Luciani (JIRA) 

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

T Jake Luciani updated CASSANDRA-7238:
--
Fix Version/s: (was: 2.0.12)
   2.0.13

> Nodetool Status performance is much slower with VNodes On
> -
>
> Key: CASSANDRA-7238
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7238
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
> Environment: 1000 M1.Large Ubuntu 12.04
>Reporter: Russell Alexander Spitzer
>Priority: Minor
> Fix For: 2.0.13
>
>
> Nodetool status on a 1000 Node cluster without vnodes returns in several 
> seconds. With vnodes on (256) there are OOM errors with the default XMX of 
> 32. Adjusting the XMX to 128 allows nodetool status to complete but the 
> execution takes roughly 10 minutes.
> Tested
> {code}
> XMX|  Status
> 32 |OOM
> 64 |OOM: GC Overhead
> 128|Finishes in ~10 minutes
> 500|Finishes in ~10 minutes
> 1000   |Finishes in ~10 minutes
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-7238) Nodetool Status performance is much slower with VNodes On

2014-09-18 Thread Michael Shuler (JIRA) 

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

Michael Shuler updated CASSANDRA-7238:
--
Fix Version/s: 2.0.11

> Nodetool Status performance is much slower with VNodes On
> -
>
> Key: CASSANDRA-7238
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7238
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
> Environment: 1000 M1.Large Ubuntu 12.04
>Reporter: Russell Alexander Spitzer
>Priority: Minor
> Fix For: 2.0.11
>
>
> Nodetool status on a 1000 Node cluster without vnodes returns in several 
> seconds. With vnodes on (256) there are OOM errors with the default XMX of 
> 32. Adjusting the XMX to 128 allows nodetool status to complete but the 
> execution takes roughly 10 minutes.
> Tested
> {code}
> XMX|  Status
> 32 |OOM
> 64 |OOM: GC Overhead
> 128|Finishes in ~10 minutes
> 500|Finishes in ~10 minutes
> 1000   |Finishes in ~10 minutes
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-7238) Nodetool Status performance is much slower with VNodes On

2014-06-26 Thread Russell Alexander Spitzer (JIRA) 

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

Russell Alexander Spitzer updated CASSANDRA-7238:
-

Reproduced In: 2.1 beta2, 2.0.8  (was: 2.1 beta2)

> Nodetool Status performance is much slower with VNodes On
> -
>
> Key: CASSANDRA-7238
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7238
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
> Environment: 1000 M1.Large Ubuntu 12.04
>Reporter: Russell Alexander Spitzer
>Priority: Minor
>
> Nodetool status on a 1000 Node cluster without vnodes returns in several 
> seconds. With vnodes on (256) there are OOM errors with the default XMX of 
> 32. Adjusting the XMX to 128 allows nodetool status to complete but the 
> execution takes roughly 10 minutes.
> Tested
> {code}
> XMX|  Status
> 32 |OOM
> 64 |OOM: GC Overhead
> 128|Finishes in ~10 minutes
> 500|Finishes in ~10 minutes
> 1000   |Finishes in ~10 minutes
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (CASSANDRA-7238) Nodetool Status performance is much slower with VNodes On

2014-05-15 Thread Russell Alexander Spitzer (JIRA) 

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

Russell Alexander Spitzer updated CASSANDRA-7238:
-

Reproduced In: 2.1 beta2

> Nodetool Status performance is much slower with VNodes On
> -
>
> Key: CASSANDRA-7238
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7238
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
> Environment: 1000 M1.Large Ubuntu 12.04
>Reporter: Russell Alexander Spitzer
>Priority: Minor
>
> Nodetool status on a 1000 Node cluster without vnodes returns in several 
> seconds. With vnodes on (256) there are OOM errors with the default XMX of 
> 32. Adjusting the XMX to 128 allows nodetool status to complete but the 
> execution takes roughly 10 minutes.
> Tested
> {code}
> XMX|  Status
> 32 |OOM
> 64 |OOM: GC Overhead
> 128|Finishes in ~10 minutes
> 500|Finishes in ~10 minutes
> 1000   |Finishes in ~10 minutes
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (CASSANDRA-7238) Nodetool Status performance is much slower with VNodes On

2014-05-15 Thread Ryan McGuire (JIRA) 

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

Ryan McGuire updated CASSANDRA-7238:


Tester: Ryan McGuire

> Nodetool Status performance is much slower with VNodes On
> -
>
> Key: CASSANDRA-7238
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7238
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
> Environment: 1000 M1.Large Ubuntu 12.04
>Reporter: Russell Alexander Spitzer
>Priority: Minor
> Fix For: 2.1 beta2
>
>
> Nodetool status on a 1000 Node cluster without vnodes returns in several 
> seconds. With vnodes on (256) there are OOM errors with the default XMX of 
> 32. Adjusting the XMX to 128 allows nodetool status to complete but the 
> execution takes roughly 10 minutes.
> Tested
> {code}
> XMX|  Status
> 32 |OOM
> 64 |OOM: GC Overhead
> 128|Finishes in ~10 minutes
> 500|Finishes in ~10 minutes
> 1000   |Finishes in ~10 minutes
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (CASSANDRA-7238) Nodetool Status performance is much slower with VNodes On

2014-05-14 Thread Russell Alexander Spitzer (JIRA) 

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

Russell Alexander Spitzer updated CASSANDRA-7238:
-

Fix Version/s: (was: 2.1 beta2)

> Nodetool Status performance is much slower with VNodes On
> -
>
> Key: CASSANDRA-7238
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7238
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
> Environment: 1000 M1.Large Ubuntu 12.04
>Reporter: Russell Alexander Spitzer
>Priority: Minor
>
> Nodetool status on a 1000 Node cluster without vnodes returns in several 
> seconds. With vnodes on (256) there are OOM errors with the default XMX of 
> 32. Adjusting the XMX to 128 allows nodetool status to complete but the 
> execution takes roughly 10 minutes.
> Tested
> {code}
> XMX|  Status
> 32 |OOM
> 64 |OOM: GC Overhead
> 128|Finishes in ~10 minutes
> 500|Finishes in ~10 minutes
> 1000   |Finishes in ~10 minutes
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)