[
https://issues.apache.org/jira/browse/FLINK-8562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16404987#comment-16404987
]
ASF GitHub Bot commented on FLINK-8562:
---------------------------------------
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/5416#discussion_r175480192
--- Diff:
flink-yarn-tests/src/test/java/org/apache/flink/yarn/YARNSessionFIFOITCase.java
---
@@ -105,7 +105,7 @@ public void testDetachedMode() throws
InterruptedException, IOException {
}
//additional sleep for the JM/TM to start and establish
connection
- sleep(2000);
+ sleep(3000);
--- End diff --
Hmm is this timeout increase not a little bit arbitrary. Can we implement
some better waiting strategy? Like waiting for the respective log statement,
for example.
> Fix YARNSessionFIFOSecuredITCase
> --------------------------------
>
> Key: FLINK-8562
> URL: https://issues.apache.org/jira/browse/FLINK-8562
> Project: Flink
> Issue Type: Bug
> Components: Security
> Affects Versions: 1.5.0, 1.6.0
> Reporter: Shuyi Chen
> Assignee: Shuyi Chen
> Priority: Blocker
> Fix For: 1.5.0
>
>
> Currently, YARNSessionFIFOSecuredITCase will not fail even if the current
> Flink YARN Kerberos integration is failing in production. Please see
> FLINK-8275.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
