You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Adam Arvai (Jira)" <ji...@apache.org> on 2020/08/24 08:42:00 UTC
[jira] [Created] (KNOX-2436) Add new service for replacing
resourceManager property during Oozie usage
Adam Arvai created KNOX-2436:
--------------------------------
Summary: Add new service for replacing resourceManager property during Oozie usage
Key: KNOX-2436
URL: https://issues.apache.org/jira/browse/KNOX-2436
Project: Apache Knox
Issue Type: New Feature
Reporter: Adam Arvai
In Oozie 5.x there is a new parameter called resourceManager. This is used instead of jobTracker. However, Oozie can fall back to jobTracker value if no resourceManager is defined. resourceManager shall have the same value as jobTracker has now.
This ticket is intend to track the work on adding a new rewrite rule and a new service returning the resource-manager's address.
Currently the JobTrackerServiceModelGenerator despite its name is actually returning the resource-manager's address. This is not enabled by default because its misleading name since we no longer have job-trackers but resource-managers.
By having a new service which does exactly the same thing as JobTrackerServiceModelGenerator but is enabled by default we could have Oozie work with Knox out of the box.
We should be careful as the resource manager service name is already taken by ResourceManagerUIServiceModelGenerator.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)