[jira] [Commented] (FLINK-10558) Port YARNHighAvailabilityITCase and YARNSessionCapacitySchedulerITCase to new code base

["TisonKun (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-10558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16657694#comment-16657694 ] 

TisonKun commented on FLINK-10558:
----------------------------------

[~till.rohrmann] I'd like to know if the present status excepted. As [~yanghua] commented on GitHub.

bq. @tillrohrmann For test case testTaskManagerFailure, the current test mode (based on stdout and stderr's special print message) cannot verify the Flip-6 scene. Because it doesn't pre-start a TM, so I can only commit a job to drive the TM registration, but this will cause the Job's output to flush out the flink's output, which shares stdout and stderr. Therefore, many judgments will not take effect.

I wonder if on FLIP-6 yarn session mode, we'd like to (really) pre-start TMs, if so, we have to mark that the workaround(submit a job to drive th TM registration) is temporary.

> Port YARNHighAvailabilityITCase and YARNSessionCapacitySchedulerITCase to new code base
> ---------------------------------------------------------------------------------------
>
>                 Key: FLINK-10558
>                 URL: https://issues.apache.org/jira/browse/FLINK-10558
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: vinoyang
>            Assignee: TisonKun
>            Priority: Minor
>
> {{YARNHighAvailabilityITCase}}, 
> {{YARNSessionCapacitySchedulerITCase#testClientStartup,}} 
> {{YARNSessionCapacitySchedulerITCase#testTaskManagerFailure}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)