For more details, see https://builds.apache.org/job/hadoop-trunk-win/520/
[Jul 5, 2018 5:42:39 PM] (haibochen) YARN-7556. Fair scheduler configuration
should allow resource types in
[Jul 5, 2018 5:54:19 PM] (rkanter) YARN-7451. Add missing tests to verify the
presence of custom resources
[Jul
Late +1 for the merge.
Thanks for driving this improvement Hanisha and Bharat.
On 6/29/18, 3:10 PM, "Bharat Viswanadham" wrote:
Hi All,
Given the positive response to the discussion thread [1], here is the
formal vote thread to merge HDDS-48 in to trunk.
Summary of
The vote passes with +1s from 6 committers and 2 contributors. There are no
-1's.
Thanks everyone for voting.
Voting Thread:
https://lists.apache.org/thread.html/b63e4569407b61a333ddf7a646dcf9ca169d2fd2cb2344d113d80697@%3Chdfs-dev.hadoop.apache.org%3E
Thanks,
Bharat
On 6/29/18, 3:14 PM,
branch-3 has re-appeared yet again on June 2nd. Looks like the
inadvertent branch-3 change from HDFS-11847 was somehow pushed again?
Anyway this branch needs to be deleted yet again as committers are
accidentally committing to it again thinking their change is going
into 3.0.x. Is an INFRA
Thanks everyone particularly Anu & Sunil for resolving the issue.
Yes, Arpit I am canceling the vote and let's open trunk for commits. I'll
also close the INFRA jira.
-Subru
On Fri, Jul 6, 2018 at 11:18 AM, Arpit Agarwal
wrote:
> Thanks Sunil!
>
> @Subru and others who voted for force push,
Thanks Sunil!
@Subru and others who voted for force push, are you okay with cancelling this
vote and declaring trunk open for commits?
On 7/6/18, 11:16 AM, "Sunil G" wrote:
Thanks. These patches are now restored.
- Sunil
On Fri, Jul 6, 2018 at 11:14 AM Vinod Kumar
Thanks. These patches are now restored.
- Sunil
On Fri, Jul 6, 2018 at 11:14 AM Vinod Kumar Vavilapalli
wrote:
> +1
>
> Thanks
> +Vinod
>
>
> On Jul 6, 2018, at 11:12 AM, Sunil G wrote:
>
> I just checked. YARN-7556 and YARN-7451 can be cherry-picked.
> I cherry-picked in my local and
@Sunil G +1, Thanks for fixing this issue.
--Anu
On 7/6/18, 11:12 AM, "Sunil G" wrote:
I just checked. YARN-7556 and YARN-7451 can be cherry-picked.
I cherry-picked in my local and compiled. Things are good.
I can push this now which will restore trunk to its original.
+1 from me.
Also +1 to reopen trunk for all commits.
On 7/6/18, 11:12 AM, "Sunil G" wrote:
I just checked. YARN-7556 and YARN-7451 can be cherry-picked.
I cherry-picked in my local and compiled. Things are good.
I can push this now which will restore trunk to its original.
+1
Thanks
+Vinod
> On Jul 6, 2018, at 11:12 AM, Sunil G wrote:
>
> I just checked. YARN-7556 and YARN-7451 can be cherry-picked.
> I cherry-picked in my local and compiled. Things are good.
>
> I can push this now which will restore trunk to its original.
> I can do this if there are no
I just checked. YARN-7556 and YARN-7451 can be cherry-picked.
I cherry-picked in my local and compiled. Things are good.
I can push this now which will restore trunk to its original.
I can do this if there are no objection.
- Sunil
On Fri, Jul 6, 2018 at 11:10 AM Arpit Agarwal
wrote:
>
afaict YARN-8435 is still in trunk. YARN-7556 and YARN-7451 are not.
From: Giovanni Matteo Fumarola
Date: Friday, July 6, 2018 at 10:59 AM
To: Vinod Kumar Vavilapalli
Cc: Anu Engineer , Arpit Agarwal
, "su...@apache.org" ,
"yarn-...@hadoop.apache.org" ,
"hdfs-...@hadoop.apache.org" ,
Yes these patches can be cherry-picked.
git cherry-pick 17262470246232d0f0651d627a4961e55b1efe6a
git cherry-pick 99febe7fd50c31c0f5dd40fa7f376f2c1f64f8c3
I will try this now and will compile.
- Sunil
On Fri, Jul 6, 2018 at 10:59 AM Giovanni Matteo Fumarola <
giovanni.fumar...@gmail.com>
Everything seems ok except the 3 commits: YARN-8435, YARN-7556, YARN-7451
are not anymore in trunk due to the revert.
Haibo/Robert if you can recommit your patches I will commit mine
subsequently to preserve the original order.
(My apology for the mess I did with the merge commit)
On Fri, Jul
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/829/
[Jul 1, 2018 11:41:46 AM] (nanda) HADOOP-15574: Suppress build error if there
are no docs after excluding
-1 overall
The following subsystems voted -1:
asflicense findbugs pathlen unit xml
The
I will add that the branch also successfully compiles.
Let's just move forward as is, unblock commits and just fix things if anything
is broken.
+Vinod
> On Jul 6, 2018, at 10:30 AM, Anu Engineer wrote:
>
> Hi All,
>
> [ Thanks to Arpit for working offline and verifying that branch is
Hi All,
[ Thanks to Arpit for working offline and verifying that branch is indeed good.]
I want to summarize what I know of this issue and also solicit other points of
view.
We reverted the commit(c163d1797) from the branch, as soon as we noticed it.
That is, we have made no other commits
-1 for the force push. Nothing is broken in trunk. The history looks ugly for
two commits and we can live with it.
The revert restored the branch to Giovanni's intent. i.e. only YARN-8435 is
applied. Verified there is no delta between hashes 0d9804d and 39ad989 (HEAD).
39ad989 2018-07-05
-1 (non-binding)
force pushes are extremely disruptive. there's no way to know who's
updated their local git repo to include these changes since the commit
went in. if a merge commit is so disruptive that we need to subject folks
to the inconvenience of a force push then we should have more
> On 6 Jul 2018, at 00:04, Eric Yang wrote:
>
> +1 on Non-routable IP idea. My preference is to start in Hadoop-common to
> minimize the scope and incrementally improve. However, this will be
> incompatible change for initial user experience on public cloud. What would
> be the right
20 matches
Mail list logo
