Jira: https://issues.apache.org/jira/browse/YARN-3271
Build: https://builds.apache.org/job/PreCommit-YARN-Build/7549/
###
## LAST 60 LINES OF THE CONSOLE
###
Jira: https://issues.apache.org/jira/browse/YARN-3552
Build: https://builds.apache.org/job/PreCommit-YARN-Build/7552/
###
## LAST 60 LINES OF THE CONSOLE
###
I will be out of the office starting 2015-04-30 and will not return until
2015-05-03.
I will be out of the office and will not return until 2015-May-3. I may not
reply mail in time during these days.
CSTL Bussiness Architect backup - Yun CDL Wang/China/IBM
PowerVC - Li Gong Liu/China/IBM
Jira: https://issues.apache.org/jira/browse/YARN-3552
Build: https://builds.apache.org/job/PreCommit-YARN-Build/7550/
###
## LAST 60 LINES OF THE CONSOLE
###
Jira: https://issues.apache.org/jira/browse/YARN-2893
Build: https://builds.apache.org/job/PreCommit-YARN-Build/7551/
###
## LAST 60 LINES OF THE CONSOLE
###
Jira: https://issues.apache.org/jira/browse/YARN-3476
Build: https://builds.apache.org/job/PreCommit-YARN-Build/7554/
###
## LAST 60 LINES OF THE CONSOLE
###
See https://builds.apache.org/job/Hadoop-Yarn-trunk/913/changes
Changes:
[jing9] HDFS-8283. DataStreamer cleanup and some minor improvement. Contributed
by Tsz Wo Nicholas Sze.
[wheat9] HDFS-8269. getBlockLocations() does not resolve the .reserved path and
generates incorrect edit logs when
See https://builds.apache.org/job/Hadoop-Yarn-trunk/913/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 8843 lines...]
Tests run: 1087, Failures: 1, Errors: 1,
Jira: https://issues.apache.org/jira/browse/YARN-3271
Build: https://builds.apache.org/job/PreCommit-YARN-Build/7553/
###
## LAST 60 LINES OF THE CONSOLE
###
Jira: https://issues.apache.org/jira/browse/YARN-3539
Build: https://builds.apache.org/job/PreCommit-YARN-Build/7556/
###
## LAST 60 LINES OF THE CONSOLE
###
Thanks Zhijie. Inline.
On Wed, Apr 29, 2015 at 9:43 PM, Zhijie Shen zs...@hortonworks.com wrote:
My 2 cents:
Branch maintenance cost should be fine if we have few features to be
developed in branches. However, if there're too many, each other branch may
be blind to most of latest code
Jira: https://issues.apache.org/jira/browse/YARN-3544
Build: https://builds.apache.org/job/PreCommit-YARN-Build/7555/
###
## LAST 60 LINES OF THE CONSOLE
###
IMO,
Branch development is great when the feature is blue sky - we don't exactly
know what we are going to do. We will try out things and the current state will
be unstable for a while until we have figured things out.
On master, the work would be clearly spec'd out and done without causing
Thanks Bikas. Inline.
On Thu, Apr 30, 2015 at 10:12 AM, Bikas Saha bi...@hortonworks.com wrote:
IMO,
Branch development is great when the feature is blue sky - we don't
exactly know what we are going to do. We will try out things and the
current state will be unstable for a while until we
Following up on Zhijie's comments, there's nothing to prevent periodically
pulling updates from the main branch (e.g. branch-2 or trunk) into the
feature branch, is there? Or cherry-picking some changes to alleviate
conflict management during branch merging?
I've seen other projects use one of
Jira: https://issues.apache.org/jira/browse/YARN-3539
Build: https://builds.apache.org/job/PreCommit-YARN-Build/7558/
###
## LAST 60 LINES OF THE CONSOLE
###
I think what Zhijie is talking about is a little different. Work happening in
parallel across 2 branches have no clue about each other since they don’t get
updates via master. If a bunch of these branches is tried to be merged close to
a release then there are likely to be a lot of surprises.
Anthony Rojas created YARN-3566:
---
Summary: YARN Scheduler Web UI not properly sorting through
Application ID or Progress bar
Key: YARN-3566
URL: https://issues.apache.org/jira/browse/YARN-3566
Project:
Jira: https://issues.apache.org/jira/browse/YARN-3521
Build: https://builds.apache.org/job/PreCommit-YARN-Build/7557/
###
## LAST 60 LINES OF THE CONSOLE
###
In other words, the best solution is careful up-front design and break up of
changes so that they can be made incrementally. At that point working on master
is not much different than working in a branch. However, if that allows for a
set of changes to be made inside a branch in a
[
https://issues.apache.org/jira/browse/YARN-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved YARN-3481.
---
Resolution: Duplicate
Report NM aggregated container resource utilization in
Jira: https://issues.apache.org/jira/browse/YARN-3534
Build: https://builds.apache.org/job/PreCommit-YARN-Build/7564/
###
## LAST 60 LINES OF THE CONSOLE
###
Jira: https://issues.apache.org/jira/browse/YARN-3534
Build: https://builds.apache.org/job/PreCommit-YARN-Build/7560/
###
## LAST 60 LINES OF THE CONSOLE
###
Fair point. Yes, if features are completely agnostic of other features,
they might be touching the same sub-system significantly. And, will
definitely lead to longer conflict resolution.
Zhihai/Bikas - any suggestions on what we can do to avoid these issues
outside of keeping an eye out for what
In HDFS, our recent feature branches tried to keep large portions of their
new code in new classes (i.e.
org.apache.hadoop.hdfs.server.namenode.CacheManager) or even new Java
packages (i.e. org.apache.hadoop.hdfs.server.namenode.snapshot). We tried
to make minimal changes in existing code: just
Jira: https://issues.apache.org/jira/browse/YARN-3411
Build: https://builds.apache.org/job/PreCommit-YARN-Build/7561/
###
## LAST 60 LINES OF THE CONSOLE
###
Started by
Hey gang.
With the commit of HADOOP-11866, the output for checkstyle and
whitespace has been greatly enhanced to actually be useful now. Instead of
getting weird output, you'll see the file, the line number and (in the case of
checkstyle) error. Note that line numbers are
Jira: https://issues.apache.org/jira/browse/YARN-3539
Build: https://builds.apache.org/job/PreCommit-YARN-Build/7563/
###
## LAST 60 LINES OF THE CONSOLE
###
Started by
Jira: https://issues.apache.org/jira/browse/YARN-3411
Build: https://builds.apache.org/job/PreCommit-YARN-Build/7565/
###
## LAST 60 LINES OF THE CONSOLE
###
Started by
Jira: https://issues.apache.org/jira/browse/YARN-3134
Build: https://builds.apache.org/job/PreCommit-YARN-Build/7562/
###
## LAST 60 LINES OF THE CONSOLE
###
Jira: https://issues.apache.org/jira/browse/YARN-1462
Build: https://builds.apache.org/job/PreCommit-YARN-Build/7566/
###
## LAST 60 LINES OF THE CONSOLE
###
Jira: https://issues.apache.org/jira/browse/YARN-2369
Build: https://builds.apache.org/job/PreCommit-YARN-Build/7559/
###
## LAST 60 LINES OF THE CONSOLE
###
Exactly. Branch development is good, but I concerned about too many concurrent
branches. In terms of code management, the good branch development candidate
could be those like registry, shared cache and timeline service. Their most
changes are the incremental code in some new sub-module, are
Thank you, Arpit. In addition, I suggest we include the following:
HADOOP-11333. Fix deadlock in DomainSocketWatcher when the notification
pipe is full
HADOOP-11604. Prevent ConcurrentModificationException while closing domain
sockets during shutdown of DomainSocketWatcher thread.
HADOOP-11648.
HDFS candidates for back-porting to Hadoop 2.6.1. The first two were requested
in [1].
HADOOP-11674. oneByteBuf in CryptoInputStream and CryptoOutputStream should be
non static
HADOOP-11710. Make CryptoOutputStream behave like DFSOutputStream wrt
synchronization
HDFS-7009. Active NN and
[
https://issues.apache.org/jira/browse/YARN-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee resolved YARN-3546.
Resolution: Not A Problem
AbstractYarnScheduler.getApplicationAttempt seems misleading, and there're
36 matches
Mail list logo