You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Tak-Lon (Stephen) Wu (Jira)" <ji...@apache.org> on 2025/05/22 19:13:00 UTC

[jira] [Commented] (HBASE-27982) Synchronous replication should check if the file system supports truncate API

    [ https://issues.apache.org/jira/browse/HBASE-27982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953531#comment-17953531 ] 

Tak-Lon (Stephen) Wu commented on HBASE-27982:
----------------------------------------------

I guessed based on the PR https://github.com/apache/hbase/pull/5747 , we can close this task and let the exception throws when truncate API wasn't implemented?

> Synchronous replication should check if the file system supports truncate API
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-27982
>                 URL: https://issues.apache.org/jira/browse/HBASE-27982
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Wei-Chiu Chuang
>            Assignee: Wei-Chiu Chuang
>            Priority: Minor
>              Labels: pull-request-available
>
> Ok. I missed this but I was just told that the synchronous replication leverages the truncate() FS API.
> https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/master/replication/SyncReplicationReplayWALManager.java#L282
> Ozone does not implement truncate so calling this method on the WAL FS will result in an exception. It would be a better user experience to alert user that this is not supported from the start.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)