[
https://issues.apache.org/jira/browse/CASSANDRA-3206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104892#comment-13104892
]
Peter Schuller commented on CASSANDRA-3206:
-------------------------------------------
My two cents: Just go wild. I really don't see the need to be conservative. On
any modern system that you run Cassandra on, the resources consumed by file
descriptors is going to be irrelevant and I don't see when you'd ever actually
want Cassandra to hit the limit, unless it's *completely* run-away and buggy in
which case the limit need not be low. Better a very high number so people don't
run into it, than try to shave off.
64k seems reasonable, I'd be fine with 250k ;)
> increase file descriptor limit in deb, rpm packages
> ---------------------------------------------------
>
> Key: CASSANDRA-3206
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3206
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
> Reporter: Jonathan Ellis
> Assignee: paul cannon
> Priority: Minor
> Fix For: 0.8.6
>
>
> We can use a lot of file descriptors (one per socket, 5? per sstable).
> People hit this regularly on the user list and it will get worse with Leveled
> compaction, which limits sstable size to a relatively low size (currently
> 5MB).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
