You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Paul Yang (JIRA)" <ji...@apache.org> on 2010/05/12 02:41:41 UTC

[jira] Work started: (HIVE-1322) Cached FileSystem can lead to persistant IOExceptions

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

Work on HIVE-1322 started by Paul Yang.

> Cached FileSystem can lead to persistant IOExceptions
> -----------------------------------------------------
>
>                 Key: HIVE-1322
>                 URL: https://issues.apache.org/jira/browse/HIVE-1322
>             Project: Hadoop Hive
>          Issue Type: Bug
>          Components: Metastore
>            Reporter: Paul Yang
>            Assignee: Paul Yang
>            Priority: Minor
>             Fix For: 0.6.0
>
>         Attachments: HIVE-1322.1.patch, HIVE-1322.2.patch
>
>
> In the metastore, the FileSystem object is created through Path.getFileSytem(), which caches the created instance for performance. For DFS, the cached FileSystem seems to retain the original IP (resolved from the supplied hostname). If the hostname->IP mapping changes, then FS operations will throw IOExceptions. Because the FileSystem is cached, re-creating the object has no effect and will continue to result in IOExceptions.
> One solution is to call close on an IOException. That will remove the entry in the cache.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.