[
https://issues.apache.org/jira/browse/CASSANDRA-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922466#action_12922466
]
Paul Bohm commented on CASSANDRA-1629:
--------------------------------------
Table.java:~275 in trunk
flushTask =
StorageService.scheduledTasks.scheduleWithFixedDelay(runnable, minCheckMs,
minCheckMs, TimeUnit.MILLISECONDS);
crashes cassandra when minCheckMs == 0, as can result from e.g.
memtableFlushAfterMins == 0.
There's no easy way for users to recover from this. Probably both setting the
memtable thresholds and above should have sanity checks.
> disallow memtable sizes <= 0
> ----------------------------
>
> Key: CASSANDRA-1629
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1629
> Project: Cassandra
> Issue Type: Bug
> Reporter: Brandon Williams
> Priority: Minor
> Fix For: 0.7.0
>
>
> It's possible to create memtable size thresholds <= 0 currently. If your
> thrift interface is old, this is easy to do accidentally, and we shouldn't
> allow this in general.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
