[
https://issues.apache.org/jira/browse/FLINK-14834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16982696#comment-16982696
]
Aljoscha Krettek commented on FLINK-14834:
------------------------------------------
I think I found the culprit for the failure of the {{dummfs}} tests. It's this
change:
https://github.com/apache/flink/commit/749965348170e4608ff2a23c9617f67b8c341df5.
This changes the job to have two sources instead of one which, under normal
circumstances, requires too many slots to run and therefore the job will fail.
For the failure of the {{normal}} tests, I see in the logs that there is only
two instances of
{code}
2019-11-20 21:32:48,107 INFO org.apache.flink.yarn.YarnResourceManager
- Requesting new TaskExecutor container with resources
<memory:1000, vCores:1>. Number pending requests 1.
{code}
while the job requires three {{TaskExecutors}} to run. For a successful run of
this test you will see three {{Requesting new TaskExecutor}} lines. I don't
know why the {{JobMaster}} does not request more {{TaskExecutors}} but this
could be a bug.
> Kerberized YARN on Docker test fails on Travis
> ----------------------------------------------
>
> Key: FLINK-14834
> URL: https://issues.apache.org/jira/browse/FLINK-14834
> Project: Flink
> Issue Type: Bug
> Components: Deployment / YARN, Tests
> Affects Versions: 1.10.0
> Reporter: Gary Yao
> Assignee: Aljoscha Krettek
> Priority: Blocker
> Labels: test-stability
> Fix For: 1.10.0
>
>
> https://api.travis-ci.org/v3/job/612782888/log.txt
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
