Hi folks,

Recently we started investigating fuse-dfs for use of ML frameworks on k8s.

I think that it is convenient way for data scientist to support access to HDFS 
via FUSE.
We also expect that we do not need to implement a function for HDFS access each 
ML frameworks.

I guess it is common use-case of HDFS for ML users.
If there is no maintainer in the community, my staffs is capable to take on the 
role.

By the way, I wonder,
- How do you access to data in HDFS from k8s? Any other solution rather than 
fuse-dfs?
- How do you think about another implementation for fuse like 
https://github.com/Microsoft/hdfs-mount . Should we ignore fuse-dfs and use or 
implement the other?

Regards,
Shingo

On 2018/10/01 20:10:07, Wei-Chiu Chuang <w...@apache.org> wrote: 
> Hi fellow Hadoop developers,> 
> 
> I want to start this thread to raise the awareness of the quality of> 
> fuse-dfs. It appears that this sub-component is not being developed and> 
> maintained, and appears not many are using it.> 
> 
> In the past two years, there has been only one bug fixed (HDFS-13322).> 
> 
> <goog_437937250>> 
> https://issues.apache.org/jira/issues/?jql=project%20in%20(HADOOP%2C%20HDFS)%20AND%20text%20~%20fuse%20ORDER%20BY%20created%20DESC%2C%20updated%20DESC>
>  
> 
> It doesn't support keytab login, ACL permissions, rename, ... a number of> 
> POSIX semantics. We also recently realized fuse-dfs doesn't work under> 
> heavy weight workload (Think running SQL applications on it)> 
> 
> So what's the status now? Is there any one who is still using fuse-dfs in> 
> production? Should we start the deprecation process? Or at least document> 
> that it is not meant for anything beyond simple data transfer? IIRC vim> 
> would even complain if you try to edit a file in fuse_dfs directory.> 
> -- > 
> A very happy Hadoop contributor> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Reply via email to