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:03:14 UTC
[jira] Created: (CASSANDRA-349) better error handling for
CommitLogSyncDelay
better error handling for CommitLogSyncDelay
--------------------------------------------
Key: CASSANDRA-349
URL: https://issues.apache.org/jira/browse/CASSANDRA-349
Project: Cassandra
Issue Type: Bug
Reporter: Eric Evans
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.
[jira] Updated: (CASSANDRA-349) better error handling for
CommitLogSyncDelay
Posted by "Michael Greene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Greene updated CASSANDRA-349:
-------------------------------------
Component/s: Core
> better error handling for CommitLogSyncDelay
> --------------------------------------------
>
> Key: CASSANDRA-349
> URL: https://issues.apache.org/jira/browse/CASSANDRA-349
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.4
> Reporter: Eric Evans
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.4
>
> Attachments: 349.patch
>
>
> 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.
[jira] Commented: (CASSANDRA-349) better error handling for
CommitLogSyncDelay
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740618#action_12740618 ]
Eric Evans commented on CASSANDRA-349:
--------------------------------------
+1
> 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
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.4
>
> Attachments: 349.patch
>
>
> 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.
[jira] Resolved: (CASSANDRA-349) better error handling for
CommitLogSyncDelay
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-349.
--------------------------------------
Resolution: Fixed
committed
> 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
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.4
>
> Attachments: 349.patch
>
>
> 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.
[jira] Assigned: (CASSANDRA-349) better error handling for
CommitLogSyncDelay
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis reassigned CASSANDRA-349:
----------------------------------------
Assignee: Jonathan Ellis
> 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
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.4
>
> Attachments: 349.patch
>
>
> 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.
[jira] Updated: (CASSANDRA-349) better error handling for
CommitLogSyncDelay
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-349:
-------------------------------------
Attachment: 349.patch
patch
> 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
>
> Attachments: 349.patch
>
>
> 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.
[jira] Updated: (CASSANDRA-349) better error handling for
CommitLogSyncDelay
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CASSANDRA-349) better error handling for
CommitLogSyncDelay
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740883#action_12740883 ]
Hudson commented on CASSANDRA-349:
----------------------------------
Integrated in Cassandra #161 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/161/])
human-readable error for bad CommitLogSyncDelay.
patch by jbellis; reviewed by Eric Evans for
> 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
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.4
>
> Attachments: 349.patch
>
>
> 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.