You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Anoop Sam John (Jira)" <ji...@apache.org> on 2020/07/12 08:59:00 UTC
[jira] [Commented] (HBASE-24717) regions opened in read only mode
failed when replaying the edits due to permission denied WRITE for
regionDir
[ https://issues.apache.org/jira/browse/HBASE-24717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17156242#comment-17156242 ]
Anoop Sam John commented on HBASE-24717:
----------------------------------------
Which version? You mean using TableSnapshotInputFormat?
Read-only regions should never deal with recovered edits.
> regions opened in read only mode failed when replaying the edits due to permission denied WRITE for regionDir
> -------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-24717
> URL: https://issues.apache.org/jira/browse/HBASE-24717
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Reporter: huan
> Assignee: huan
> Priority: Blocker
>
> Open region in read only mode, [HbaseTableSnapshotInputFormat], if RegionDir has
> recovered edits files under, (filesUnderRootDir), when read-only region read the content, it will try to delete the content of recovered edits, including filesUnderRootDir part
> {code:java}
> // code placeholder
> for (Path file : filesUnderRootDir) {
> if (!rootFS.delete(file, false)) {
> LOG.error("Failed delete of {}", file);
> } else {
> LOG.debug("Deleted recovered.edits file={}", file);
> }
> }
> {code}
> however, read-only mode usually no WRITE access to delete it.
> {code:java}
> // code placeholder
> org.apache.hadoop.security.AccessControlException: Permission denied: user=xxxx, access=WRITE, inode="/hbase/data/default/TABLENAME/d6777e449ed4d137b6a2f735653a7c3a/recovered.edits":hbase:hbase:drwxr-xr-x
> {code}
> it will throw excption and failed
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)