Zoltan Siegl created YARN-9936:
--
Summary: Support vector of capacity percentages in Capacity
Scheduler configuration
Key: YARN-9936
URL: https://issues.apache.org/jira/browse/YARN-9936
Project: Hadoop
For more details, see
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/488/
No changes
-1 overall
The following subsystems voted -1:
asflicense findbugs hadolint pathlen unit xml
The following subsystems voted -1 but
were configured to be filtered/ignored:
cc
Prabhu Joseph created YARN-9937:
---
Summary: Add missing queue configs in
RMWebService#CapacitySchedulerQueueInfo
Key: YARN-9937
URL: https://issues.apache.org/jira/browse/YARN-9937
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-9891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Bacsko resolved YARN-9891.
Resolution: Duplicate
> Capacity scheduler: enhance capacity / maximum-capacity setting
>
Thanks for putting this up, Jonathan Hung.
+1(non-binding)
* verified signature and checksum.
* built source tarball by OpenJDK 7 on CentOS 7 with native profile enabled.
* launched pseudo distributed cluster with security configurations.
* create encryption zone and put files in it.
* accessed
Sounds good to me, thank you for addressing the concerns Jonathan.
+1 from me.
From: Masatake Iwasaki
Sent: Monday, October 28, 2019 7:52 AM
To: Jonathan Hung ; Hdfs-dev
; mapreduce-dev ;
yarn-dev ; Hadoop Common
Subject: Re: [VOTE] Release Apache Hadoop
Manikandan R created YARN-9938:
--
Summary: Validate QueuePath for QueueMapping contains dynamic
group as parent queue
Key: YARN-9938
URL: https://issues.apache.org/jira/browse/YARN-9938
Project: Hadoop
The immediate problem we need to fix is to prevent github updates from
spamming the dev mailing list.
Might make sense to just have a separate issues@ mailing list and point
github to that?
On Sun, Oct 27, 2019 at 10:12 PM Dinesh Chitlangia
wrote:
> +1
>
> -Dinesh
>
>
>
>
> On Sun, Oct 27,
@Vinod Kumar Vavilapalli
Do we need a separate vote thread for this? there are already JIRAs in
place for ozone code removal and I gather it is same for Submarine.
Would it be possible to treat this thread as consensus and act upon the
JIRA itself?
Thanks
Anu
On Sun, Oct 27, 2019 at 6:58 PM
Prashant Golash created YARN-9939:
-
Summary: Killing running containers on UNHEALTHY nodes
Key: YARN-9939
URL: https://issues.apache.org/jira/browse/YARN-9939
Project: Hadoop YARN
Issue
Compatibility testing has gone well for me.
- In a 4-node cluster, I ran YARN rolling upgrade tests between 2.8.5 and 2.10.0
- In a 4-node cluster, I ran YARN rolling upgrade tests between 2.10.0 and trunk
- With one 4-node cluster running 2.10.0 and one 4-node cluster running trunk,
I ran a
Thanks Eric! I sent out an RC1 earlier last week, not sure if you saw that.
The only diff between RC1 and RC0 is HDFS-14667. If RC1 looks good to you
then it'd be great to get your testing results on that thread.
Jonathan Hung
On Mon, Oct 28, 2019 at 1:06 PM epa...@apache.org wrote:
>
+1, Thanks Marton, for the consensus and action plan!
-Rohith Sharma K S
On Sun, 27 Oct 2019 at 13:55, Elek, Marton wrote:
>
> As discussed earlier in the thread of "Hadoop-Ozone repository mailing
> list configurations" [1] I suggested to solve the current
> misconfiguration problem with
Thanks for the efforts! Jonathan!
+1 (non-binding) on RC1.
- Set up a single node cluster with the binary tarball
- Run Spark Pi and PySpark job
BR,
Zhankun
On Mon, 28 Oct 2019 at 23:16, Masatake Iwasaki
wrote:
> Thanks for putting this up, Jonathan Hung.
>
> +1(non-binding)
>
> * verified
+1 on RC1
- Verified signatures
- Built from source (RHEL7)
- Ran single node cluster and tested basic HDFS commands
Thanks for putting this together Jonathan!
On Mon, Oct 28, 2019 at 7:54 PM zhankun tang wrote:
> Thanks for the efforts! Jonathan!
>
> +1 (non-binding) on RC1.
> - Set up a
15 matches
Mail list logo
