You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ahmed Bashir (JIRA)" <ji...@apache.org> on 2012/10/10 23:33:02 UTC
[jira] [Created] (CASSANDRA-4790) Allow property override of
available processors value
Ahmed Bashir created CASSANDRA-4790:
---------------------------------------
Summary: Allow property override of available processors value
Key: CASSANDRA-4790
URL: https://issues.apache.org/jira/browse/CASSANDRA-4790
Project: Cassandra
Issue Type: Improvement
Components: Core
Affects Versions: 1.1.4
Reporter: Ahmed Bashir
Currently, many critical thread pools are sized according to the number of available processors i.e. Runtime.getRuntime.availableProcessors() (See StageManager.java)
In a multi-instance deployment, multiple Cassandra instances will independently assume that all processors are available to it; there should be a mechanism to specify a smaller set of processors (and perhaps have affinity).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4790) Allow property override of
available processors value
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-4790:
----------------------------------------
Fix Version/s: 1.2.0 rc1
> Allow property override of available processors value
> -----------------------------------------------------
>
> Key: CASSANDRA-4790
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4790
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Ahmed Bashir
> Assignee: Brandon Williams
> Priority: Minor
> Fix For: 1.1.8, 1.2.0 rc1
>
> Attachments: 4790.txt
>
>
> Currently, many critical thread pools are sized according to the number of available processors i.e. Runtime.getRuntime.availableProcessors() (See StageManager.java)
> In a multi-instance deployment, multiple Cassandra instances will independently assume that all processors are available to it; there should be a mechanism to specify a smaller set of processors (and perhaps have affinity).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4790) Allow property override of
available processors value
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-4790:
--------------------------------------
Priority: Minor (was: Major)
Affects Version/s: (was: 1.1.4)
Fix Version/s: 1.1.8
Issue Type: New Feature (was: Improvement)
Adding a -D option to cassandra-env.sh would be cleanest.
> Allow property override of available processors value
> -----------------------------------------------------
>
> Key: CASSANDRA-4790
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4790
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Ahmed Bashir
> Priority: Minor
> Fix For: 1.1.8
>
>
> Currently, many critical thread pools are sized according to the number of available processors i.e. Runtime.getRuntime.availableProcessors() (See StageManager.java)
> In a multi-instance deployment, multiple Cassandra instances will independently assume that all processors are available to it; there should be a mechanism to specify a smaller set of processors (and perhaps have affinity).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CASSANDRA-4790) Allow property override of
available processors value
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams reassigned CASSANDRA-4790:
-------------------------------------------
Assignee: Brandon Williams
> Allow property override of available processors value
> -----------------------------------------------------
>
> Key: CASSANDRA-4790
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4790
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Ahmed Bashir
> Assignee: Brandon Williams
> Priority: Minor
> Fix For: 1.1.8
>
>
> Currently, many critical thread pools are sized according to the number of available processors i.e. Runtime.getRuntime.availableProcessors() (See StageManager.java)
> In a multi-instance deployment, multiple Cassandra instances will independently assume that all processors are available to it; there should be a mechanism to specify a smaller set of processors (and perhaps have affinity).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4790) Allow property override of
available processors value
Posted by "Aleksey Yeschenko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510690#comment-13510690 ]
Aleksey Yeschenko commented on CASSANDRA-4790:
----------------------------------------------
lgtm, +1 (piconit - IDEA's auto-import misplaced FBUtilities import in StageManager).
> Allow property override of available processors value
> -----------------------------------------------------
>
> Key: CASSANDRA-4790
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4790
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Ahmed Bashir
> Assignee: Brandon Williams
> Priority: Minor
> Fix For: 1.1.8
>
> Attachments: 4790.txt
>
>
> Currently, many critical thread pools are sized according to the number of available processors i.e. Runtime.getRuntime.availableProcessors() (See StageManager.java)
> In a multi-instance deployment, multiple Cassandra instances will independently assume that all processors are available to it; there should be a mechanism to specify a smaller set of processors (and perhaps have affinity).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4790) Allow property override of
available processors value
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-4790:
----------------------------------------
Attachment: 4790.txt
Patch to override with -Dcassandra.available_processors
> Allow property override of available processors value
> -----------------------------------------------------
>
> Key: CASSANDRA-4790
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4790
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Ahmed Bashir
> Assignee: Brandon Williams
> Priority: Minor
> Fix For: 1.1.8
>
> Attachments: 4790.txt
>
>
> Currently, many critical thread pools are sized according to the number of available processors i.e. Runtime.getRuntime.availableProcessors() (See StageManager.java)
> In a multi-instance deployment, multiple Cassandra instances will independently assume that all processors are available to it; there should be a mechanism to specify a smaller set of processors (and perhaps have affinity).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira