You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stu Hood (JIRA)" <ji...@apache.org> on 2011/07/18 21:41:58 UTC
[jira] [Created] (CASSANDRA-2916) Streaming estimatedKey
calculation should never be 0
Streaming estimatedKey calculation should never be 0
----------------------------------------------------
Key: CASSANDRA-2916
URL: https://issues.apache.org/jira/browse/CASSANDRA-2916
Project: Cassandra
Issue Type: Bug
Components: Core
Reporter: Stu Hood
Assignee: Stu Hood
Priority: Minor
Fix For: 1.0
The new in-streaming SSTable rebuild uses the sender's estimated key calculation to determine which codepath to take: in some cases, samples can result in an estimated key count of 0.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2916) Streaming estimatedKey
calculation should never be 0
Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stu Hood updated CASSANDRA-2916:
--------------------------------
Attachment: 0001-CASSANDRA-2916-Assume-at-least-one-estimated-key-for-s.txt
Path to ensure that we never estimate 0 keys for non-empty ranges. Also, properly handle the case where a range captures exactly one key.
> Streaming estimatedKey calculation should never be 0
> ----------------------------------------------------
>
> Key: CASSANDRA-2916
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2916
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Stu Hood
> Assignee: Stu Hood
> Priority: Minor
> Fix For: 1.0
>
> Attachments: 0001-CASSANDRA-2916-Assume-at-least-one-estimated-key-for-s.txt
>
>
> The new in-streaming SSTable rebuild uses the sender's estimated key calculation to determine which codepath to take: in some cases, samples can result in an estimated key count of 0.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2916) Streaming estimatedKey
calculation should never be 0
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-2916:
--------------------------------------
Affects Version/s: 1.0
> Streaming estimatedKey calculation should never be 0
> ----------------------------------------------------
>
> Key: CASSANDRA-2916
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2916
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0
> Reporter: Stu Hood
> Assignee: Stu Hood
> Priority: Minor
> Fix For: 1.0
>
> Attachments: 0001-CASSANDRA-2916-Assume-at-least-one-estimated-key-for-s.txt
>
>
> The new in-streaming SSTable rebuild uses the sender's estimated key calculation to determine which codepath to take: in some cases, samples can result in an estimated key count of 0.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2916) Streaming estimatedKey
calculation should never be 0
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067274#comment-13067274 ]
Hudson commented on CASSANDRA-2916:
-----------------------------------
Integrated in Cassandra #960 (See [https://builds.apache.org/job/Cassandra/960/])
ensure that we never estimate 0 keys when streaming non-empty ranges
patch by Stu Hood; reviewed by jbellis for CASSANDRA-2916
jbellis : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1148029
Files :
* /cassandra/trunk/test/unit/org/apache/cassandra/streaming/StreamingTransferTest.java
* /cassandra/trunk/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
* /cassandra/trunk/src/java/org/apache/cassandra/streaming/IncomingStreamReader.java
> Streaming estimatedKey calculation should never be 0
> ----------------------------------------------------
>
> Key: CASSANDRA-2916
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2916
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0
> Reporter: Stu Hood
> Assignee: Stu Hood
> Priority: Minor
> Fix For: 1.0
>
> Attachments: 0001-CASSANDRA-2916-Assume-at-least-one-estimated-key-for-s.txt
>
>
> The new in-streaming SSTable rebuild uses the sender's estimated key calculation to determine which codepath to take: in some cases, samples can result in an estimated key count of 0.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CASSANDRA-2916) Streaming
estimatedKey calculation should never be 0
Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067238#comment-13067238 ]
Stu Hood edited comment on CASSANDRA-2916 at 7/18/11 7:44 PM:
--------------------------------------------------------------
Patch to ensure that we never estimate 0 keys for non-empty ranges. Also, properly handle the case where a range captures exactly one key.
was (Author: stuhood):
Path to ensure that we never estimate 0 keys for non-empty ranges. Also, properly handle the case where a range captures exactly one key.
> Streaming estimatedKey calculation should never be 0
> ----------------------------------------------------
>
> Key: CASSANDRA-2916
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2916
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Stu Hood
> Assignee: Stu Hood
> Priority: Minor
> Fix For: 1.0
>
> Attachments: 0001-CASSANDRA-2916-Assume-at-least-one-estimated-key-for-s.txt
>
>
> The new in-streaming SSTable rebuild uses the sender's estimated key calculation to determine which codepath to take: in some cases, samples can result in an estimated key count of 0.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira