[
https://issues.apache.org/jira/browse/APEXCORE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037894#comment-16037894
]
ASF GitHub Bot commented on APEXCORE-736:
-----------------------------------------
GitHub user PramodSSImmaneni opened a pull request:
https://github.com/apache/apex-core/pull/538
APEXCORE-736 Using YARN client api to fetch the application master
container report
This is a continuation of the PR
https://github.com/apache/apex-core/pull/534 and merging this should close that
PR.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/PramodSSImmaneni/apex-core APEXCORE-736
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/apex-core/pull/538.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #538
----
commit f0fa410e5156fa9ea25c6447495a0e3f40cc6c21
Author: devtagare <[email protected]>
Date: 2017-05-31T21:09:00Z
YarnClient to get containerInfo
commit c4be3af4d72b1a0addabf31b5771ad0f130c0daf
Author: Pramod Immaneni <[email protected]>
Date: 2017-06-05T18:36:23Z
Merge branch 'APEXCORE-736' of github.com:devtagare/incubator-apex-core
into APEXCORE-736
commit 1e24aaf6c8a07ff24106dde439bfd817ebb9a553
Author: Pramod Immaneni <[email protected]>
Date: 2017-06-06T00:31:50Z
APEXCORE-736 Using YARN client api to fetch the application master
container report
----
> Unable to fetch application master container report with kerberized web
> services in STRAM
> -----------------------------------------------------------------------------------------
>
> Key: APEXCORE-736
> URL: https://issues.apache.org/jira/browse/APEXCORE-736
> Project: Apache Apex Core
> Issue Type: Bug
> Reporter: devendra tagare
> Assignee: devendra tagare
>
> Currently we are using a WebServicesClient in StreamingContainerManager to
> get container report from Yarn.
> Using the WebServicesClient will throw and exception if the webservices are
> kerberized.
> We should use a YARN client instead which can access kerberized YARN
> webservices as per its access levels.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)