You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (Jira)" <ji...@apache.org> on 2020/09/15 20:18:00 UTC
[jira] [Resolved] (FLINK-19218) Remove inconsistent host logic for
LocalFileSystem
[ https://issues.apache.org/jira/browse/FLINK-19218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephan Ewen resolved FLINK-19218.
----------------------------------
Resolution: Fixed
Fixed in 1.12.0 via 5bcdd7de67bf21bc19c8b5b84f617dacaf7f0c99
> Remove inconsistent host logic for LocalFileSystem
> --------------------------------------------------
>
> Key: FLINK-19218
> URL: https://issues.apache.org/jira/browse/FLINK-19218
> Project: Flink
> Issue Type: Bug
> Components: API / Core
> Affects Versions: 1.11.1
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Priority: Major
> Fix For: 1.12.0
>
>
> The {{LocalFileSystem}} returns file splits with a host information as returned via
> {code}
> InetAddress.getLocalHost().getHostName();
> {code}
> This might be different, though, from the host name that the TaskManager is configured to use, which results in incorrect location matching if this information is used.
> It is also incorrect in cases where the file system is in fact not local, but a mounted NAS.
> Since this information is anyways not useful (there no good way to support locality-aware file access for the LocalFileSystem) I would suggest to remove this code. That would be better than having code in place that tries to suggest locality information that is frequently incorrect.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)