cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Hermes (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1906) Sanitize configuration code
Date Fri, 11 Feb 2011 20:08:57 GMT


Jon Hermes commented on CASSANDRA-1906:

CFS has started to accumulate Default<T>s for settings that can be changed at runtime
for per-node settings (min/max compaction threshold, and mem size/ops/time (soon row/key cache
save period CASSANDRA-2100)). If we want to keep these ephemeral (non-migration) changes,
then Tables (KSs) and StorageService (Global per-node settings) should follow in suit, and
there should be one for every config option that doesn't impact the cluster (i.e. changing
the saved_caches dir/ = Good, changing the partitioner or token ephemerally = bad).

This reduces it to three paths:
- Read from cassandra.yaml for SS settings at boot time,
- Read from the schema and accept migrations to the schema for permanent KS/CF settings,
- Change any per-node value at runtime in SS/Table/CFS,
... and the first and third may well be combined for a scant two _code_ paths (compare to
current 4+ code paths) separated by the permanent/non-permanent taxonomy.

> Sanitize configuration code
> ---------------------------
>                 Key: CASSANDRA-1906
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jon Hermes
>            Assignee: Jon Hermes
>            Priority: Minor
>             Fix For: 0.8
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> Multipart:
> - Drop deprecated YAML config. Only config allowed is via thrift/JMX. Make this gratuitously
easy to do with sane defaults and accepting changesets as opposed to full definitions.
> - Combine common code between KS/CF/ColumnDefs and between thrift/avro defs.
> - Provide an obvious and clean interface for changing settings locally versus globally
(JMX vs. thrift). Dox here.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message