[
https://issues.apache.org/jira/browse/IMPALA-10375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318963#comment-17318963
]
Quanlong Huang commented on IMPALA-10375:
-----------------------------------------
Do we plan to fix this in 4.0? If not, I'll adjust the target version to 4.1.
> Lock down which filesystem types use the file handle cache
> ----------------------------------------------------------
>
> Key: IMPALA-10375
> URL: https://issues.apache.org/jira/browse/IMPALA-10375
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 4.0
> Reporter: Joe McDonnell
> Assignee: Joe McDonnell
> Priority: Major
>
> When determining whether to cache file handles, the code uses this check:
> {noformat}
> bool use_file_handle_cache = false;
> if (is_file_handle_caching_enabled() &&
> (expected_local_ ||
> (FLAGS_cache_remote_file_handles && disk_id_ ==
> io_mgr_->RemoteDfsDiskId()) ||
> (FLAGS_cache_s3_file_handles && disk_id_ == io_mgr_->RemoteS3DiskId()) ||
> (FLAGS_cache_abfs_file_handles && disk_id_ ==
> io_mgr_->RemoteAbfsDiskId())) {
> use_file_handle_cache = true;
> }{noformat}
> If expected_local_ is specified, then we always would allow caching,
> regardless of filesystem type. While expected_local_ should be false for
> remote filesystems, the code should be more defensive and only use the file
> handle cache for specific supported filesystems. In particular, we currently
> don't support caching Ozone file handles, but if this somehow considered
> Ozone local, then it would cache them.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
