You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Peter Schuller (Created) (JIRA)" <ji...@apache.org> on 2012/01/28 08:10:10 UTC
[jira] [Created] (CASSANDRA-3807) bootstrap can silently fail if
sources are down for one or more ranges
bootstrap can silently fail if sources are down for one or more ranges
----------------------------------------------------------------------
Key: CASSANDRA-3807
URL: https://issues.apache.org/jira/browse/CASSANDRA-3807
Project: Cassandra
Issue Type: Bug
Reporter: Peter Schuller
Assignee: Peter Schuller
Priority: Critical
Assigning to me, will submit patch after CASSANDRA-3483.
The silent failure is not new; been like that since forever (well, at least 0.8). The result is that the node goes up in the ring and starts serving inconsistent reads.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3807) bootstrap can silently fail if
sources are down for one or more ranges
Posted by "Peter Schuller (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195450#comment-13195450 ]
Peter Schuller commented on CASSANDRA-3807:
-------------------------------------------
Correction, I'll just build it into the 3483 patch.
> bootstrap can silently fail if sources are down for one or more ranges
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-3807
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3807
> Project: Cassandra
> Issue Type: Bug
> Reporter: Peter Schuller
> Assignee: Peter Schuller
> Priority: Critical
>
> Assigning to me, will submit patch after CASSANDRA-3483.
> The silent failure is not new; been like that since forever (well, at least 0.8). The result is that the node goes up in the ring and starts serving inconsistent reads.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3807) bootstrap can silently fail if
sources are down for one or more ranges
Posted by "Peter Schuller (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195474#comment-13195474 ]
Peter Schuller commented on CASSANDRA-3807:
-------------------------------------------
CASSANDRA-3483 now has a patch that addresses this.
> bootstrap can silently fail if sources are down for one or more ranges
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-3807
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3807
> Project: Cassandra
> Issue Type: Bug
> Reporter: Peter Schuller
> Assignee: Peter Schuller
> Priority: Critical
>
> Assigning to me, will submit patch after CASSANDRA-3483.
> The silent failure is not new; been like that since forever (well, at least 0.8). The result is that the node goes up in the ring and starts serving inconsistent reads.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3807) bootstrap can silently fail if
sources are down for one or more ranges
Posted by "Peter Schuller (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204136#comment-13204136 ]
Peter Schuller commented on CASSANDRA-3807:
-------------------------------------------
I should mention for the record that the symptom need not necessarily be an *empty* node (or rather empty + whatever writes have come in), but can also be a partially filled node if a subset of the ranges were able to stream but not others.
> bootstrap can silently fail if sources are down for one or more ranges
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-3807
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3807
> Project: Cassandra
> Issue Type: Bug
> Reporter: Peter Schuller
> Priority: Critical
>
> Assigning to me, will submit patch after CASSANDRA-3483.
> The silent failure is not new; been like that since forever (well, at least 0.8). The result is that the node goes up in the ring and starts serving inconsistent reads.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CASSANDRA-3807) bootstrap can silently fail if
sources are down for one or more ranges
Posted by "Jonathan Ellis (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-3807.
---------------------------------------
Resolution: Duplicate
Assignee: (was: Peter Schuller)
> bootstrap can silently fail if sources are down for one or more ranges
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-3807
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3807
> Project: Cassandra
> Issue Type: Bug
> Reporter: Peter Schuller
> Priority: Critical
>
> Assigning to me, will submit patch after CASSANDRA-3483.
> The silent failure is not new; been like that since forever (well, at least 0.8). The result is that the node goes up in the ring and starts serving inconsistent reads.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira