+1 from me.
I have:
1) setup a small cluster
2) enabled the reservation system
3) submitted reservation through REST
4) ran a job within reservation
5) did few negative tests (what happens if res system is disabled and you
try to reserve, what happens if a job is submitted with invalid res id,
For more details, see
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/32/
[Nov 6, 2017 7:40:41 AM] (naganarasimha_gr) MAPREDUCE-6975. Logging task
counters. Contributed by Prabhu Joseph.
[Error replacing 'FILE' - Workspace is not accessible]
Attila Sasvari created MAPREDUCE-7003:
-
Summary: Indefinite retries of getJobSummary() if a job summary
file is corrupt
Key: MAPREDUCE-7003
URL: https://issues.apache.org/jira/browse/MAPREDUCE-7003
What are the known gaps that need bridging between 2.x and 3.x?
>From an HDFS perspective, we've tested wire compat, rolling upgrade, and
rollback.
>From a YARN perspective, we've tested wire compat and rolling upgrade. Arun
just mentioned an NM rollback issue that I'm not familiar with.
Here’s +1 from myself.
The vote passes with 7 (+1) bindings and 2 (+1) non-bindings.
Thanks for all who voted. I’ll merge to trunk by the end of today.
Jian
On Nov 6, 2017, at 8:38 AM, Billie Rinaldi
> wrote:
+1 (binding)
On Mon, Oct
Congratulations to all the contributors involved, this is a great step forward!
+Vinod
> On Nov 6, 2017, at 2:40 PM, Jian He wrote:
>
> Okay, I just merged the branch to trunk (108 commits in total !)
> Again, thanks for all who contributed to this feature!
>
> Jian
>
>
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/582/
[Nov 6, 2017 7:28:38 AM] (naganarasimha_gr) MAPREDUCE-6975. Logging task
counters. Contributed by Prabhu Joseph.
-1 overall
The following subsystems voted -1:
asflicense unit
The following
Thanks Vinod.
>> Of the top of my head, one of the biggest areas is application
>> compatibility. When folks move from 2.x to 3.x, are their apps binary
>> compatible? Source compatible? Or need changes?
I thought these are good concerns from overall perspective. On the other hand,
I've
Thanks Subru/Arun for the great work!
Downloaded source and built from it. Deployed RM HA non-secured cluster
along with new YARN UI and ATSv2.
I am facing basic RM HA switch issue after first time successful start. *Can
anyone else is facing this issue?*
When RM is switched from ACTIVE to
The main goal of the bridging release is to ease transition on stuff that is
guaranteed to be broken.
Of the top of my head, one of the biggest areas is application compatibility.
When folks move from 2.x to 3.x, are their apps binary compatible? Source
compatible? Or need changes?
In 1.x ->
Okay, I just merged the branch to trunk (108 commits in total !)
Again, thanks for all who contributed to this feature!
Jian
On Nov 6, 2017, at 1:26 PM, Jian He
> wrote:
Here’s +1 from myself.
The vote passes with 7 (+1) bindings and 2 (+1)
Here is my +1 to start.
- Setup a small 4 node cluster
- Verified some basic HDFS commands
- Ran Pi / sleep jobs (with some mix of Opportunistic containers - both
distributed and centralized scheduling)
Cheers
-Arun
On Fri, Nov 3, 2017 at 4:38 PM, Arun Suresh wrote:
> Hey
+1 (binding) thanks Jian for all the great work!
Built from branch and deployed, able to bring up services along with atsv2
enabled and new YARN UI integration.
Tried flexing, start, stop operations using REST api's.
- Rohith Sharma K S
On 31 October 2017 at 01:36, Jian He
+1 (non-binding)
-Gour
On 10/30/17, 1:49 PM, "Jian He" wrote:
>Few more things:
>
>This is the document for trying a non-docker service on YARN.
>https://github.com/apache/hadoop/blob/yarn-native-services/hadoop-yarn-pro
+1 (binding)
On Mon, Oct 30, 2017 at 1:06 PM, Jian He wrote:
> Hi All,
>
> I would like to restart the vote for merging yarn-native-services to trunk.
> Since last vote, we have been working on several issues in documentation,
> DNS, CLI modifications etc. We believe now
15 matches
Mail list logo