[
https://issues.apache.org/jira/browse/HBASE-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-4553:
-------------------------
Priority: Critical (was: Major)
Fix Version/s: 0.92.0
Marking critical for 0.92. I see this in unit tests from time to time --
TestAvroServer does it pretty reliably. If no .tableinfo, we're kinda hosed so
needs to work. I'm on this one.
> The update of .tableinfo is not atomic; we remove then rename
> -------------------------------------------------------------
>
> Key: HBASE-4553
> URL: https://issues.apache.org/jira/browse/HBASE-4553
> Project: HBase
> Issue Type: Task
> Reporter: stack
> Priority: Critical
> Fix For: 0.92.0
>
>
> This comes of HBASE-4547. The rename in 0.20 hdfs fails if file exists
> already. In 0.20+ its better but still 'some' issues if existing reader when
> file is renamed. This issue is about fixing this (though we depend on fix
> first being in hdfs).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
