You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2026/10/09 21:16:00 UTC

[jira] [Updated] (PHOENIX-7865) Set explicit HDFS block size on replication log files

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

Andrew Kyle Purtell updated PHOENIX-7865:
-----------------------------------------
    Fix Version/s: PHOENIX-7562-feature
                   5.4.0

> Set explicit HDFS block size on replication log files
> -----------------------------------------------------
>
>                 Key: PHOENIX-7865
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-7865
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Tanuj Khurana
>            Assignee: Tanuj Khurana
>            Priority: Major
>             Fix For: PHOENIX-7562-feature, 5.4.0
>
>
> The ReplicationLog used to clamp the configured max rotation size to the FileSystem default block size to keep each log file in a single HDFS block (so the disruptor consumer thread never makes an addBlock RPC to the NameNode). That clamp silently capped large rotation-size configs. But this coupling was too tight and sometimes could create too many log files for the ReplicationLogProcessor to process.
> Decouple the two concerns: stop clamping, and instead create each log file with an explicit per-file block size.



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