[
https://issues.apache.org/jira/browse/HBASE-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-2382:
-------------------------
Attachment: 2382-v5-TRUNK.patch
I committed Nicolas's patches to the branch w/ some extra commentary on what
pseudo-distributed is and some cast at an explication of why one replica only
when pseudo-distributed. Thanks for the patch Nicolas.
The attached file is Nicolas's work forward-ported only it can't be applied
until we add in support for hdfs-862 to TRUNK too. So, I'll edit this issue to
only be for 0.21 going forward. It can't go in until hbase-2306 goes in.
> Don't rely on fs.getDefaultReplication() to roll HLogs
> ------------------------------------------------------
>
> Key: HBASE-2382
> URL: https://issues.apache.org/jira/browse/HBASE-2382
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: Jean-Daniel Cryans
> Assignee: Nicolas Spiegelberg
> Fix For: 0.21.0
>
> Attachments: 2382-v5-TRUNK.patch, HBASE-2382-20.4.patch,
> HBASE-2382-documentation.patch
>
>
> As I was commenting in HBASE-2234, using fs.getDefaultReplication() to roll
> HLogs if they lose replicas isn't reliable since that value is client-side
> and unless HBase is configured with it or has Hadoop's configurations on its
> classpath, it will do the wrong thing.
> Dhruba added:
> bq. Can we use <hlogpath>.getFiletatus().getReplication() instead of
> fs.getDefaltReplication()? This will will ensure that we look at the repl
> factor of the precise file we are interested in, rather than what the
> system-wide default value is.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
