You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2013/05/20 23:35:16 UTC
[jira] [Commented] (HBASE-8580) Ensure that there are 3 replicas
when Flushing or Compacting
[ https://issues.apache.org/jira/browse/HBASE-8580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662376#comment-13662376 ]
Sergey Shelukhin commented on HBASE-8580:
-----------------------------------------
We are not guaranteed that replicas will not fail during, or immediately after, we finish writing, or later, so we are only privileging some small window of time to ensure 3 replicas, and trying to marginally improve reliability over HDFS by poking around in the (semi-)internals.
How is this different from having <3 replicas at other time? Is there some specific bug/scenario you saw?
> Ensure that there are 3 replicas when Flushing or Compacting
> ------------------------------------------------------------
>
> Key: HBASE-8580
> URL: https://issues.apache.org/jira/browse/HBASE-8580
> Project: HBase
> Issue Type: Improvement
> Reporter: Elliott Clark
>
> It is possible that datanodes in a DFS pipeline can be dropped. When this happens it possible for there to be fewer than the number of replicas expected. After a close on the file the namenode tries to re-replicate the file. On flush and compaction we should block waiting for the number of datanodes reporting that they have the needed blocks to be 3.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira