Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cache Hadoop Filesystem instance on Gravitino server to improve the performance #6561

Open
yuqi1129 opened this issue Feb 27, 2025 · 4 comments · May be fixed by #6619
Open

Cache Hadoop Filesystem instance on Gravitino server to improve the performance #6561

yuqi1129 opened this issue Feb 27, 2025 · 4 comments · May be fixed by #6619
Assignees

Comments

@yuqi1129
Copy link
Contributor

yuqi1129 commented Feb 27, 2025

Currently , all Gravitino File system providers use the following code

(Take HDFSFileSystemProvider for example)

Image

FileSystem.instance will always create a new Filesystem everytime even though they are the same mostly. In fact Hadoop FileSystem did have cache mechanism, If we use FileSystem.get, cache mechanism in FileSystem will works. Due to the fact the Gravitino virtual FileSystem (GVFS) client also shares FileSystemProviders and supports credentials for each unique path, we should be cautious when planning to enable cache in the file system. in all

  • In Gravitno server side, we can enable cache in FileSystem level
  • In GVFS, we need to disable it FileSystem level and cache file system instacen in GVFS level
@sunxiaojian
Copy link
Collaborator

@yuqi1129 please assign it to me.

@yuqi1129
Copy link
Contributor Author

yuqi1129 commented Mar 3, 2025

Of course, I will send it to you if you are interested in this issue.

@sunxiaojian
Copy link
Collaborator

Of course, I will send it to you if you are interested in this issue.

ok, thanks

@shaofengshi
Copy link
Contributor

Good catch!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants