hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-2382) Don't rely on fs.getDefaultReplication() to roll HLogs
Date Mon, 17 May 2010 21:18:42 GMT

     [ https://issues.apache.org/jira/browse/HBASE-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack resolved HBASE-2382.
--------------------------

    Resolution: Fixed

HBase-2306 went in when we did this -> "HBASE-2544  Forward port branch 0.20 WAL to TRUNK".
 HBASE-2544 also added the bulk of this issue.  I then applied 2382-v5-TRUNK.patch which was
edits to overview.html changes.  Resolving.

> 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.


Mime
View raw message