Tao Yang created YARN-7591:
--
Summary: NPE in async-scheduling mode of CapacityScheduler
Key: YARN-7591
URL: https://issues.apache.org/jira/browse/YARN-7591
Project: Hadoop YARN
Issue Type: Bug
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/609/
[Nov 29, 2017 4:54:49 PM] (weichiu) HADOOP-15054. upgrade hadoop dependency on
commons-codec to 1.11.
[Nov 29, 2017 5:43:03 PM] (weiy) HDFS-12835. Fix the javadoc errors in
Router-based federation.
[Nov
Eric Yang created YARN-7590:
---
Summary: Improve container-executor validation check
Key: YARN-7590
URL: https://issues.apache.org/jira/browse/YARN-7590
Project: Hadoop YARN
Issue Type: Improvement
+1, thanks Sunil!
Wangda Tan
On Wed, Nov 29, 2017 at 5:56 PM, Sunil G wrote:
> Hi All,
>
>
> Based on the discussion at [1], I'd like to start a vote to merge feature
> branch
>
> YARN-5881 to trunk. Vote will run for 7 days, ending Wednesday Dec 6 at
> 6:00PM PDT.
>
>
>
Jason Lowe created YARN-7589:
Summary: TestPBImplRecords fails with NullPointerException
Key: YARN-7589
URL: https://issues.apache.org/jira/browse/YARN-7589
Project: Hadoop YARN
Issue Type: Bug
Allen Wittenauer created YARN-7588:
--
Summary: Remove 'yarn historyserver' from bin/yarn
Key: YARN-7588
URL: https://issues.apache.org/jira/browse/YARN-7588
Project: Hadoop YARN
Issue Type:
> On Nov 30, 2017, at 1:07 AM, Rohith Sharma K S
> wrote:
>
>
> >. If ATSv1 isn’t replaced by ATSv2, then why is it marked deprecated?
> Ideally it should not be. Can you point out where it is marked as deprecated?
> If it is in historyserver daemon start, that
Weiwei Yang created YARN-7587:
-
Summary: Skip dispatching opportunistic containers to nodes whose
queue is already full
Key: YARN-7587
URL: https://issues.apache.org/jira/browse/YARN-7587
Project: Hadoop
Suma Shivaprasad created YARN-7586:
--
Summary: Application Placement should be done before ACL checks in
ResourceManager
Key: YARN-7586
URL: https://issues.apache.org/jira/browse/YARN-7586
Project:
Hi Vinod/Allen
bq. We need to figure out if this V1 TimelineService should even be support
given ATSv2.
ATSv2 is in alpha phase. We should continue to support Timeline Service V1
till we have the detailed entity level ACLs in V2. And also there are
proposal to upgrade/migration paths from TSv1 to
Thanks everyone for the feedback!
Based on positive feedback, we started voting thread in
http://mail-archives.apache.org/mod_mbox/hadoop-yarn-dev/201711.mbox/%3CCACYiTuhzMrd_kFRT7_f4VBHejrajbCnVB1wmgHLMLXRr58y0MA%40mail.gmail.com%3E
@Carlo: Yes, this change should be straight forward except
11 matches
Mail list logo