[
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
