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
Vrushali C created YARN-8500:
Summary: Use hbase shaded jars
Key: YARN-8500
URL: https://issues.apache.org/jira/browse/YARN-8500
Project: Hadoop YARN
Issue Type: Sub-task
Reporter:
Sunil Govindan created YARN-8499:
Summary: ATS v2 should handle connection issues in general for all
storages
Key: YARN-8499
URL: https://issues.apache.org/jira/browse/YARN-8499
Project: Hadoop YARN
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
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
+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.
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-dev@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
[
https://issues.apache.org/jira/browse/YARN-8462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe resolved YARN-8462.
--
Resolution: Duplicate
This is being handled by YARN-8193 with a new branch-2 patch posted there.
>
-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
Hi Sean,
thank you for your support. I read the discussion on
https://s.apache.org/5GeN and this sounds good.
Kind regards,
Cliff
On 2018/07/04 16:39:49, Sean Busbey wrote:
> Hi Cliff!>
>
> That looks like the result of an automated scan + exploit tool.
Presuming your cluster is not
21 matches
Mail list logo
