[
https://issues.apache.org/jira/browse/KNOX-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186431#comment-17186431
]
ASF subversion and git services commented on KNOX-2436:
-------------------------------------------------------
Commit bdee3172d8e99aa42ceeeaba6a3cee10abb51248 in knox's branch
refs/heads/master from Adam Arvai
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=bdee317 ]
KNOX-2436 Add new service for replacing resourceManager property during Oozie
usage (#369)
> 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
> Assignee: Adam Arvai
> Priority: Major
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> 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)
