As I mentioned in the [VOTE] thread at [1], for Timeline Service v2, we
are thinking about merging to branch2 some time in the next couple of weeks.
So far, we have been maintaining a branch2 based YARN-5355_branch2 along
with our trunk based feature branch YARN-5355. Varun Saxena has been
Hi Subru,
We are also discussing the merge of HDFS-10467 (Router-based federation)
and we would like to target 2.9 to do a full release together with YARN
federation.
Chris Douglas already arranged the integration into trunk for 3.0.0 GA.
Regarding the points to cover:
1. API compatibility: we
Hi Subru,
Thanks for starting the discussion. We are targeting merging YARN-5734
(API-based scheduler configuration) to branch-2 before the release of
2.9.0, since the feature is close to complete. Regarding the requirements
for merge,
1. API compatibility - this feature adds new APIs, does not
Thanks Vrushali for being entirely open as to the current status of ATSv2.
I appreciate that we want to ensure things are tested at scale, and as you
said we are working on that right now on our clusters.
We have tested the feature to demonstrate it works at what we consider
moderate scale.
I
Thanks Subru for initiating this discussion.
Wanted to share some thoughts in the context of Timeline Service v2. The
current status of this module is that we are ramping up for a second merge
to trunk. We still have a few merge blocker jiras outstanding, which we
think we will finish soon.
Folks,
With the release for 2.8, we would like to look ahead to 2.9 release as
there are many features/improvements in branch-2 (about 1062 commits), that
are in need of a release vechile.
Here's our first cut of the proposal from the YARN side:
1. Scheduler improvements (decoupling
