[
https://issues.apache.org/jira/browse/AMBARI-9971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361252#comment-14361252
]
Vijay Srinivasaraghavan commented on AMBARI-9971:
-------------------------------------------------
The current RCO configuration and its implementation logic considers only two
scenarios (GlusterFS and non-GlusterFS which is HDFS). This forces a constraint
on adding any new hadoop compatible file system as the RCO can't be applied.
Instead of keeping conditional validation on specific file system (HDFS vs
Gluster) at the RCO java component level, if we could keep the RCO definition
in XML as abstract say "option_hcfs" and allow each file system stack (HDFS or
GlusterFS or any other FS) to override the RCO configuration as appropriate.
The java component can be modified to read "optional_hcfs" configuration
values. A separate JIRA (AMBARI-10023) for HCFS support is created which talks
abot the RCO scenario just explained.
> Provide means to eliminate unnecessary ordering constraints when default FS
> is external
> ---------------------------------------------------------------------------------------
>
> Key: AMBARI-9971
> URL: https://issues.apache.org/jira/browse/AMBARI-9971
> Project: Ambari
> Issue Type: Task
> Reporter: Ivan Mitic
> Fix For: 2.0.0
>
>
> In cloud deployments, external file system can be used as default, in which
> case dependencies from the role command order json need to be relaxed (or
> fully removed).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
