[jira] [Commented] (HDDS-7325) getDefaultBlockSize reports incorrect size

["Michael Smith (Jira)" <ji...@apache.org>]

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

Michael Smith commented on HDDS-7325:
-------------------------------------

I think this also causes us to be unable to use a service ID to connect to Ozone. Only hostname works.

> getDefaultBlockSize reports incorrect size
> ------------------------------------------
>
>                 Key: HDDS-7325
>                 URL: https://issues.apache.org/jira/browse/HDDS-7325
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: Ozone Client, Ozone Filesystem
>    Affects Versions: 1.1.0
>            Reporter: Michael Smith
>            Priority: Major
>
> Calling some operations on the Hadoop FileSystem interface backed by an Ozone FileSystem do not return the expected results when based on ozone-site.xml configuration options.
> If I do something like
> {code}
> Configuration conf = new Configuration();
> FileSystem fs = (new Path(uri)).getFileSystem(CONF);
> fs.getDefaultSize()
> {code}
> it always returns the default value when I set {{ozone.scm.block.size}} in ozone-site.xml (also tried core-site.xml).
> The only way to get the correct value is to
> 1. Pass an OzoneConfiguration object.
> 2. Disable fs cache with {{fs.ofs.impl.disable.cache: true}} in core-site.xml (so we don't have to pass OzoneConfiguration every place we fetch the FileSystem).
> Having to explicitly pass an OzoneConfiguration object seems contrary to the principles of the Hadoop FileSystem abstraction.



--
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