You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Wei-Chiu Chuang (Jira)" <ji...@apache.org> on 2024/09/11 18:32:00 UTC

[jira] [Resolved] (HDDS-11449) Ambigious "Ignoring ozone.fs.hsync.enabled because HBase enhancements are disallowed" logs

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

Wei-Chiu Chuang resolved HDDS-11449.
------------------------------------
    Fix Version/s: 1.5.0
       Resolution: Fixed

> Ambigious "Ignoring ozone.fs.hsync.enabled because HBase enhancements are disallowed" logs
> ------------------------------------------------------------------------------------------
>
>                 Key: HDDS-11449
>                 URL: https://issues.apache.org/jira/browse/HDDS-11449
>             Project: Apache Ozone
>          Issue Type: Bug
>            Reporter: Pratyush Bhatt
>            Assignee: Ashish Kumar
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.5.0
>
>
> HDDS-11342 added a Master config so that all HBase-related enhancements would be disabled (disallowed) when this config is set to {{{}false{}}}.
> It adds a Warn message if any of the config is having a non-default value:
> {code:java}
> When any of the configs listed above has a value other than the one above, a warning-level message will be printed that prompts the user to flip the config if they want to enable the feature. {code}
> Looks like there is a bug here.
> The defaults are as follows as per the JIRA:
> {code:java}
> ozone.fs.hsync.enabled = false
> ozone.client.incremental.chunk.list = false
> ozone.client.stream.putblock.piggybacking = false
> ozone.client.key.write.concurrency = 1 {code}
> I was running a fs -cp command, and it had logs like below:
> {code:java}
> 2024-09-10 18:21:52 WARN helpers.OzoneFSUtils: Ignoring ozone.fs.hsync.enabled = false because HBase enhancements are disallowed. To enable it, set ozone.client.hbase.enhancements.allowed = true as well.
> 2024-09-10 18:21:53 WARN helpers.OzoneFSUtils: Ignoring ozone.fs.hsync.enabled = false because HBase enhancements are disallowed. To enable it, set ozone.client.hbase.enhancements.allowed = true as well.
> 2024-09-10 18:21:53 WARN helpers.OzoneFSUtils: Ignoring ozone.fs.hsync.enabled = false because HBase enhancements are disallowed. To enable it, set ozone.client.hbase.enhancements.allowed = true as well.
> 2024-09-10 18:21:53 WARN helpers.OzoneFSUtils: Ignoring ozone.fs.hsync.enabled = false because HBase enhancements are disallowed. To enable it, set ozone.client.hbase.enhancements.allowed = true as well.
> 2024-09-10 18:21:53 WARN helpers.OzoneFSUtils: Ignoring ozone.fs.hsync.enabled = false because HBase enhancements are disallowed. To enable it, set ozone.client.hbase.enhancements.allowed = true as well.
> 2024-09-10 18:21:53 WARN helpers.OzoneFSUtils: Ignoring ozone.fs.hsync.enabled = false because HBase enhancements are disallowed. To enable it, set ozone.client.hbase.enhancements.allowed = true as well.
> {code}
> This to me doesn't make sense, as the config is in its default value and still this is thrown which is pretty obvious from the logs.
> And other problem is that these WARN logs are bombarded. They should only come once per command/operation.
> cc: [~siyao]  [~ashishkr] [~weichiu] 



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org