cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (CASSANDRA-2916) Streaming estimatedKey calculation should never be 0
Date Mon, 18 Jul 2011 19:45:57 GMT

    [ 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

        

Mime
View raw message