[
https://issues.apache.org/jira/browse/MAPREDUCE-7530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18057877#comment-18057877
]
ASF GitHub Bot commented on MAPREDUCE-7530:
-------------------------------------------
K0K0V0K opened a new pull request, #8247:
URL: https://github.com/apache/hadoop/pull/8247
### Description of PR
We can not get metrics for running MR job via proxy.
Example call:
http://{{RM}}:8088/proxy/application_1770709887971_0014/ws/v1/mapreduce/jobs/job_1770709887971_0014/counters
Results:
404
Seems like we have to use moxy here also
### How was this patch tested?
I manually tried some MR job, and I could access the UI
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
### AI Tooling
No AI tool was used
> MR AM REST API backward compatibility with Jersey1
> --------------------------------------------------
>
> Key: MAPREDUCE-7530
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7530
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mr-am
> Affects Versions: 3.5.0
> Reporter: Bence Kosztolnik
> Priority: Major
>
> We can not get metrics for running MR job via proxy.
> Example call:
> http://\{{RM}}:8088/proxy/application_1770709887971_0014/ws/v1/mapreduce/jobs/job_1770709887971_0014/counters
> Results 404
> Seems like we have to use moxy here also
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
