Hi All,
Please note that ATSv2 has been merged to branch-2.
Refer to
https://github.com/apache/hadoop/commit/54a694172d7162b2ff45d6e1780c0523cfda66e7
We will continue monitoring if everything works well post-merge.
Regards,
Varun Saxena.
On Sat, Oct 7, 2017 at 5:30 AM, Subramaniam V K wrote:
stakeholders to discuss inclusion in 2.9. We'll report back
>>> to the 2.9 release thread as soon as we reach consensus.
>>>
>>> On Thu, Aug 31, 2017 at 10:39 AM, Ravi Prakash
>>> wrote:
>>>
>>>> +1 to maintaining history.
>>>&g
+1
On Fri, 6 Jul 2018 at 3:07 AM, Subru Krishnan wrote:
> Folks,
>
> There was a merge commit accidentally pushed to trunk, you can find the
> details in the mail thread [1].
>
> I have raised an INFRA ticket [2] to reset/force push to clean up trunk.
>
> Can we have a quick vote for INFRA sign-
Thanks Junping for creating the release.
+1 (non-binding)
* Verified signatures.
* Built from source.
* Set up a pseudo-distributed cluster.
* Successfully ran pi and wordcount jobs.
* Navigated the YARN RM and NM UI.
Regards,
Varun Saxena.
On Wed, Mar 22, 2017 at 12:13 AM, Haibo Chen wrote:
Hi All,
Just to update.
Folks who may be interested in going through the documentation for the
feature can refer to current documentation attached in pdf format, on the
umbrella JIRA i.e. YARN-5355.
Furthermore, we have run the YARN-5355 patch(with all the changes made in
the branch) against trun
Thanks Subru for voting.
> What are the timelines you are looking for getting this into branch-2?
We haven't yet decided on it and were thinking of discussing this in detail
within the team after merge to trunk.
The timelines would depend on whether we release whatever we merge to trunk
in 2.9 o
+1 (binding).
Kudos to all the team members for their great work!
Being part of the ATSv2 team, I have been involved with either development
or review of most of the JIRAs'.
Tested ATSv2 in both secure and non-secure mode. Also verified that there
is no impact when ATSv2 is turned off.
Regards,
Hi Andrew,
We have completed the merge of TSv2 to trunk.
You can now go ahead with the branching.
Regards,
Varun Saxena.
On Tue, Aug 29, 2017 at 11:35 PM, Andrew Wang
wrote:
> Sure. Ping me when the TSv2 goes in, and I can take care of branching.
>
> We're still waiting on the native services
be here?
>>>
>>> I do currently plan to merge the s3guard in as one single squashed
>>> patch; just getting HADOOP-14809 sorted first.
>>>
>>>
>>> > On 30 Aug 2017, at 07:09, Vrushali C wrote:
>>> >
>>> > I'm adding my +1 (bi
+1
On Sat, 2 Feb 2019, 03:54 Wangda Tan, wrote:
> Hi all,
>
> According to positive feedbacks from the thread [1]
>
> This is vote thread to start a new subproject named "hadoop-submarine"
> which follows the release process already established for ozone.
>
> The vote runs for usual 7 days, whi
10 matches
Mail list logo
