cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-7778) Use PID to automatically scale thread pools and throttles.
Date Fri, 15 Aug 2014 18:27:18 GMT

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

Jonathan Ellis updated CASSANDRA-7778:
--------------------------------------

    Fix Version/s: 3.0

> Use PID to automatically scale thread pools and throttles.
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-7778
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7778
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Matt Stump
>              Labels: ponies
>             Fix For: 3.0
>
>
> Most customers deploy with non-optimal configurations. Examples include compaction throttle,
streaming throttle, RPC requests threadpool size, which are set too aggressively or too conservatively.
 Often these problems aren't discovered until the cluster is in the field, and the problem
will manifest as a critical outage. This results in the perception that Cassandra "falls over"
without warning. Because it's difficult to ship with a set of tuning parameters that are valid
for all or even most scenarios I propose that we use a PID algorithm to automatically tune
several key parameters. The goal of the PID would be to keep load within a healthy range.
If the user chooses they could always revert to explicitly defined configuration.
> http://en.wikipedia.org/wiki/PID_controller



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

Mime
View raw message