cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Roth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13279) Table default settings file
Date Tue, 28 Feb 2017 14:33:45 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888112#comment-15888112
] 

Benjamin Roth commented on CASSANDRA-13279:
-------------------------------------------

Maybe it was a bit misleading. I am not defending a new source per se. I am simply 'pro' improving
docs by adding problem/solution centric resources in a place that can easily be found by anyone.
E.g. if I google for "Cassandra performance tuning", the first match should go to an official
guide. 

I'd love to volunteer but first I'd like to work on MVs which I am deferring since end of
'16.
But if there is a consensus of a possible structure and if I have access to the docs I am
happy to add content whenever I feel like.

> Table default settings file
> ---------------------------
>
>                 Key: CASSANDRA-13279
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13279
>             Project: Cassandra
>          Issue Type: Wish
>          Components: Configuration
>            Reporter: Romain Hardouin
>            Priority: Minor
>              Labels: config, documentation
>
> Following CASSANDRA-13241 we often see that there is no one-size-fits-all value for settings.
We can't find a sweet spot for every use cases.
> It's true for settings in cassandra.yaml but as [~brstgt] said for {{chunk_length_in_kb}}:
"this is somewhat hidden for the average user". 
> Many table settings are somewhat hidden for the average user. Some people will think
RTFM but if a file - say tables.yaml - contains default values for table settings, more people
would pay attention to them. And of course this file could contain useful comments and guidance.

> Example with SSTable compression options:
> {code}
> # General comments about sstable compression
> compression:
>     # First of all: explain what is it. We split each SSTable into chunks, etc.
>     # Explain when users should lower this value (e.g. 4) or when a higher value like
64 or 128 are recommended.
>     # Explain the trade-off between read latency and off-heap compression metadata size.
>     chunk_length_in_kb: 16
>     
>     # List of available compressor: LZ4Compressor, SnappyCompressor, and DeflateCompressor
>     # Explain trade-offs, some specific use cases (e.g. archives), etc.
>     class: 'LZ4Compressor'
>     
>     # If you want to disable compression by default, uncomment the following line
>     #enabled: false
> {code}
> So instead of hard coded values we would end up with something like TableConfig + TableDescriptor
à la Config + DatabaseDescriptor.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message