You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Eric Evans (JIRA)" <ji...@apache.org> on 2009/08/06 17:05:14 UTC
[jira] Updated: (CASSANDRA-349) better error handling for
CommitLogSyncDelay
[ https://issues.apache.org/jira/browse/CASSANDRA-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Evans updated CASSANDRA-349:
---------------------------------
Fix Version/s: 0.4
Priority: Minor (was: Major)
Affects Version/s: 0.4
> better error handling for CommitLogSyncDelay
> --------------------------------------------
>
> Key: CASSANDRA-349
> URL: https://issues.apache.org/jira/browse/CASSANDRA-349
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.4
> Reporter: Eric Evans
> Priority: Minor
> Fix For: 0.4
>
>
> When CommitLogSyncDelay is missing from the config, cassandra throws a NumberFormatException. Since this required directive is new for 0.4, it should probably have better handling, (like CommitLogSync does for example).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.