p-szucs opened a new pull request, #6625:
URL: https://github.com/apache/hadoop/pull/6625
Change-Id: I47937134c8d8e1537c6af1033cc590dd528dda11
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
Quoting the upstream ticket for problem statement:
> This problem happens when AM submits a startContainer request with a new
HDFS token (say, tokenB) which is not managed by YARN, so two tokens exist in
the credentials of the user on NM, one is tokenB, the other is the one renewed
on RM (tokenA). If tokenB is selected when connect to HDFS and tokenB expires,
exception happens.
This change removes the expired delegation tokens from the credentials
before the log aggregation tries to write the logs into HDFS, so we can avoid
getting InvalidToken exceptions.
### How was this patch tested?
Added unit test.
Tested the change on a cluster having an expired HDFS delegation token
present in the credentials when trying to use HDFS.
### For code changes:
- [x] 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?
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
