You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Zili Chen (Jira)" <ji...@apache.org> on 2019/10/08 08:05:00 UTC

[jira] [Created] (FLINK-14343) Remove uncompleted YARNHighAvailabilityService

Zili Chen created FLINK-14343:
---------------------------------

             Summary: Remove uncompleted YARNHighAvailabilityService
                 Key: FLINK-14343
                 URL: https://issues.apache.org/jira/browse/FLINK-14343
             Project: Flink
          Issue Type: Task
          Components: Runtime / Coordination
            Reporter: Zili Chen
            Assignee: Zili Chen
             Fix For: 1.10.0


Corresponding mailing list [thread|https://lists.apache.org/x/thread.html/6022f2124be91e3f4667d61a977ea0639e2c19286560d6d1cb874792@%3Cdev.flink.apache.org%3E].

Noticed that there are several stale & uncompleted high-availability services implementations, I start this thread in order to see whether or not we can remove them for a
clean codebase.

Below are all of classes I noticed.

- YarnHighAvailabilityServices
- AbstractYarnNonHaServices
- YarnIntraNonHaMasterServices
- YarnPreConfiguredMasterNonHaServices
- SingleLeaderElectionService
- FsNegativeRunningJobsRegistry
(as well as their dedicated tests)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)