[
https://issues.apache.org/jira/browse/CASSANDRA-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13772134#comment-13772134
]
Jonathan Ellis commented on CASSANDRA-6059:
-------------------------------------------
I respect that, but I still think it's time we fixed it:
- Current value of 10s is mostly an accident, because we didn't want to
surprise people back in 1.1? when we split the timeout values apart. At some
point that logic needs to take a back seat to giving people actual good
defaults.
- We're very early in 2.0 still, mass adoption is still ahead of us.
- Typically people doing minor version updates don't rip-and-replace
cassandra.yaml so they will keep using their old settings.
> Improve memory-use defaults
> ---------------------------
>
> Key: CASSANDRA-6059
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6059
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 2.0.1
>
> Attachments: 6059.txt
>
>
> Anecdotally, it's still too easy to OOM Cassandra even after moving sstable
> internals off heap.
--
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
