[
https://issues.apache.org/jira/browse/KNOX-2436?focusedWorklogId=475210&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-475210
]
ASF GitHub Bot logged work on KNOX-2436:
----------------------------------------
Author: ASF GitHub Bot
Created on: 27/Aug/20 09:40
Start Date: 27/Aug/20 09:40
Worklog Time Spent: 10m
Work Description: arvaiadam commented on pull request #369:
URL: https://github.com/apache/knox/pull/369#issuecomment-681841227
> @arvaiadam , in the PR description you say this is needed for Oozie 5.x.
Would not be better to create a new version within gateway-service-definitions
(e.g. 5.0.0) and leave the previous version as-is?
Thanks for your feedback, i changed accordingly.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 475210)
Time Spent: 50m (was: 40m)
> 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: 50m
> 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)
