[
https://issues.apache.org/jira/browse/AMBARI-5181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284511#comment-14284511
]
Vijay Srinivasaraghavan commented on AMBARI-5181:
-------------------------------------------------
Martin Bukatovic Tracking issues using "hcfs" label certainly helps but my
broader concern is that the current Ambari framework is not designed to support
any HCFS (in-place of HDFS) as an alternate file system. The framework assumes
HDFS as core component that should exist in the first place. I believe there
was an effort attempted earlier to support generic HCFS but later reverted back
to support only GlusterFS. I am trying to understand the painpoints on why the
generic design was aborted.
> HCFS Component for Ambari JIRAs
> -------------------------------
>
> Key: AMBARI-5181
> URL: https://issues.apache.org/jira/browse/AMBARI-5181
> Project: Ambari
> Issue Type: Task
> Reporter: jay vyas
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Lets create an "HCFS" component for ambari JIRAs... ! ((( Ping [~erinaboyd]
> is this what your thought is ? This was originally your idea, thanks for
> mentioning it ! )))
> Now that Ambari is HCFS Compliant (i.e. see
> https://forge.gluster.org/hadoop/pages/ConfiguringAmbari2), it would be great
> if we were able to document and file bugs specific to HCFS related support ..
> for example:
> - if there was a bug associated with installing a file system plugin
> - if an HCFS ambari module breaks or causes ambari deployment to fail
> - if an HCFS is somehow not compliant with HDFS specific semantics in how
> ambari sets up the file system... see BIGTOP-1200 / BIGTOP-952 as an how
> management tools "should" (or at least "could") be doing HCFS provisioning :)
>
> So, lets create an HCFS component where we can track any file system plugin
> and setup related issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
