You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2009/12/08 03:17:18 UTC
[jira] Created: (CASSANDRA-610) Gossip conviction threshold too low
Gossip conviction threshold too low
-----------------------------------
Key: CASSANDRA-610
URL: https://issues.apache.org/jira/browse/CASSANDRA-610
Project: Cassandra
Issue Type: Bug
Environment: debian lenny amd 64 OpenJDK 64-Bit Server VM (build 1.6.0_0-b11, mixed mode)
Reporter: Brandon Williams
Assignee: Brandon Williams
Fix For: 0.5
Attachments: 610.patch
The current gossip conviction threshold is a bit too low, and can cause hosts to 'flap' under heavy load. I suspect that the original author of the failure detector implementation originally used both suspect and convict, but at some point decided that there was no action to take when a host was suspected, or that it was not worth doing. They appear to have short-circuited the code to convict on suspect to eliminate this, however this caused the suspicion threshold (5) to be used for convicting hosts instead of the conviction threshold (8).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-610) Gossip conviction threshold too
low
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787262#action_12787262 ]
Jonathan Ellis commented on CASSANDRA-610:
------------------------------------------
LGTM. Waiting for Dan to test.
> Gossip conviction threshold too low
> -----------------------------------
>
> Key: CASSANDRA-610
> URL: https://issues.apache.org/jira/browse/CASSANDRA-610
> Project: Cassandra
> Issue Type: Bug
> Environment: debian lenny amd 64 OpenJDK 64-Bit Server VM (build 1.6.0_0-b11, mixed mode)
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Fix For: 0.5
>
> Attachments: 610.patch
>
>
> The current gossip conviction threshold is a bit too low, and can cause hosts to 'flap' under heavy load. I suspect that the original author of the failure detector implementation originally used both suspect and convict, but at some point decided that there was no action to take when a host was suspected, or that it was not worth doing. They appear to have short-circuited the code to convict on suspect to eliminate this, however this caused the suspicion threshold (5) to be used for convicting hosts instead of the conviction threshold (8).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-610) Gossip conviction threshold too
low
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788064#action_12788064 ]
Hudson commented on CASSANDRA-610:
----------------------------------
Integrated in Cassandra #282 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/282/])
increase failure conviction threshold. patch by Brandon Williams; reviewed by jbellis for
> Gossip conviction threshold too low
> -----------------------------------
>
> Key: CASSANDRA-610
> URL: https://issues.apache.org/jira/browse/CASSANDRA-610
> Project: Cassandra
> Issue Type: Bug
> Environment: debian lenny amd 64 OpenJDK 64-Bit Server VM (build 1.6.0_0-b11, mixed mode)
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Fix For: 0.5
>
> Attachments: 610.patch
>
>
> The current gossip conviction threshold is a bit too low, and can cause hosts to 'flap' under heavy load. I suspect that the original author of the failure detector implementation originally used both suspect and convict, but at some point decided that there was no action to take when a host was suspected, or that it was not worth doing. They appear to have short-circuited the code to convict on suspect to eliminate this, however this caused the suspicion threshold (5) to be used for convicting hosts instead of the conviction threshold (8).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-610) Gossip conviction threshold too low
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-610:
---------------------------------------
Attachment: 610.patch
> Gossip conviction threshold too low
> -----------------------------------
>
> Key: CASSANDRA-610
> URL: https://issues.apache.org/jira/browse/CASSANDRA-610
> Project: Cassandra
> Issue Type: Bug
> Environment: debian lenny amd 64 OpenJDK 64-Bit Server VM (build 1.6.0_0-b11, mixed mode)
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Fix For: 0.5
>
> Attachments: 610.patch
>
>
> The current gossip conviction threshold is a bit too low, and can cause hosts to 'flap' under heavy load. I suspect that the original author of the failure detector implementation originally used both suspect and convict, but at some point decided that there was no action to take when a host was suspected, or that it was not worth doing. They appear to have short-circuited the code to convict on suspect to eliminate this, however this caused the suspicion threshold (5) to be used for convicting hosts instead of the conviction threshold (8).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.