Hi devs, 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 work on the ongoing high-availability refactor effort[1].
Below are all of classes I noticed. - YarnHighAvailabilityServices - AbstractYarnNonHaServices - YarnIntraNonHaMasterServices - YarnPreConfiguredMasterNonHaServices - SingleLeaderElectionService - FsNegativeRunningJobsRegistry (as well as their dedicated tests) Any suggestion? Best, tison. [1] https://issues.apache.org/jira/browse/FLINK-10333