[
https://issues.apache.org/jira/browse/OOZIE-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17017780#comment-17017780
]
Junfan Zhang commented on OOZIE-3572:
-------------------------------------
[~asalamon74] After a series of tests, I have implemented tasks submitted to
other clusters at the workflow action level. There are several implementation
factors as follows.
1. specify conf {{oozie.service.HadoopAccessorService.hadoop.configurations}}.
This can load the corresponding cluster configuration according to the setting
{{job-tracker}} in workflow action xml when the action is running
2. Because our current default file system uses viewfs, when action start in
other cluster, the oozie current cluster viewfs path cannot be recognized
normally. So when loading is needed, replace it with active namenode.
3. Similarly, the workflow action actionDir also uses the viewfs path, so it
needs to be changed to activeNamenode.
*Does the community need to support this action-level cross-cluster scheduling
model?*
Also, there doesn't seem to be a detailed description of the
{{oozie.service.HadoopAccessorService.hadoop.configurations}} parameter in the
documentation.
> Support workflow action running in different clusters?
> ------------------------------------------------------
>
> Key: OOZIE-3572
> URL: https://issues.apache.org/jira/browse/OOZIE-3572
> Project: Oozie
> Issue Type: Improvement
> Reporter: Junfan Zhang
> Priority: Major
>
> Currently in our production environment, there are more than 10 clusters, and
> each cluster is deployed with Oozie server. This has caused difficulties in
> operation and maintenance, and difficulty in expanding the workflow between
> multiple clusters.
> Does the community have plans to support actions running in different
> clusters?
> Or give me some suggestions
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
