[
https://issues.apache.org/jira/browse/HBASE-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-1470:
-------------------------
Attachment: 1470-v2.patch
If dfs.support.append is set to true AND you have put an hadoop with
hadoop-4379 into hbase CLASSPATH, this patch will make it so sync use the
hadoop-4379 new syncFs call.
This is a bit tough to test. You have to do messing with different hadop jars.
I played around a bunch with it and it seems to do the right thing. I'll just
commit since it satisfies a probably exotic need (Last time I was running 4379,
namenode shutdown because of a bad generation stamp. I don't think this a 4379
issue. Its probably something that can happen if you ahve
dfs.support.append=true, a bug).
> hbase and HADOOP-4379, dhruba's flush/sync
> ------------------------------------------
>
> Key: HBASE-1470
> URL: https://issues.apache.org/jira/browse/HBASE-1470
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Fix For: 0.20.0
>
> Attachments: 1470-v2.patch, 1470.patch, recovery3.patch
>
>
> This covers work with HADOOP-4379
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
