Rohith Sharma K S created YARN-6304:
---
Summary: Skip rm.transitionToActive call to RM if RM is already
active.
Key: YARN-6304
URL: https://issues.apache.org/jira/browse/YARN-6304
Project: Hadoop YAR
> On Mar 7, 2017, at 2:51 PM, Andrew Wang wrote:
> I think it'd be nice to
> have a nightly Jenkins job that builds an RC,
Just a reminder that any such build cannot be used for an actual
release:
http://www.apache.org/legal/release-policy.html#owned-controlled-hardware
I was planning to take this up, celebrating my return from my paternity leave
of absence for quite a while.
Marton, let me know if you do want to take this up instead and we can work
together.
Thanks
+Vinod
> On Mar 7, 2017, at 9:13 AM, Sangjin Lee wrote:
>
> If we have a volunteer for relea
Our release steps are documented on the wiki:
2.6/2.7:
https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
2.8+:
https://wiki.apache.org/hadoop/HowToRelease
I think given the push toward 2.8 and 3.0, there's less interest in
streamlining the 2.6 and 2.7 release processes. CHANGES.txt is the big
Daniel Templeton created YARN-6303:
--
Summary: hadoop-mapreduce-client-jobclient.jar sets a main class
that isn't in the JAR
Key: YARN-6303
URL: https://issues.apache.org/jira/browse/YARN-6303
Project
Miklos Szegedi created YARN-6302:
Summary: Fail the node, if Linux Container Executor is not
configured properly
Key: YARN-6302
URL: https://issues.apache.org/jira/browse/YARN-6302
Project: Hadoop YAR
Hi Abhishek!
You might also want to pull in
https://issues.apache.org/jira/browse/YARN-6054 .
HTH
Ravi
On Mon, Mar 6, 2017 at 8:39 AM, Jason Lowe
wrote:
> Verify that something outside of Hadoop/YARN is not coming along
> periodically and removing "old" files (e.g.: tmpwatch, etc.). Users hav
Daniel Templeton created YARN-6301:
--
Summary: Fair scheduler docs should explain the meaning of setting
a queue's weight to zero
Key: YARN-6301
URL: https://issues.apache.org/jira/browse/YARN-6301
Pr
Hi Sabiya,
1. Unfortunately no.
2. Technically yes, although I'm not sure if people have tried it and
succeeded. Which other filesystem were you thinking of using?
3. None. Admins can choose to take backups. Recently HDFS got the snapshot
feature.
4. Hopefully yes.
5. No. Tasks are restarted on ot
Daniel Templeton created YARN-6300:
--
Summary: NULL_UPDATE_REQUESTS is redundant in TestFairScheduler
Key: YARN-6300
URL: https://issues.apache.org/jira/browse/YARN-6300
Project: Hadoop YARN
Daniel Templeton created YARN-6299:
--
Summary: FairSharePolicy is off when demand is less than min share
Key: YARN-6299
URL: https://issues.apache.org/jira/browse/YARN-6299
Project: Hadoop YARN
Yufei Gu created YARN-6298:
--
Summary: Metric preemptCall is not used in new preemption.
Key: YARN-6298
URL: https://issues.apache.org/jira/browse/YARN-6298
Project: Hadoop YARN
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/YARN-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haibo Chen resolved YARN-6252.
--
Resolution: Duplicate
> Suspicious code fragments: comparing with itself
> --
Haibo Chen created YARN-6297:
Summary: TestAppLogAggregatorImp.verifyFilesUploaded() should
check # of filed uploaded with that of files expected
Key: YARN-6297
URL: https://issues.apache.org/jira/browse/YARN-6297
Haibo Chen created YARN-6296:
Summary: ReservationId.compareTo ignores id when clustertimestamp
is the same
Key: YARN-6296
URL: https://issues.apache.org/jira/browse/YARN-6296
Project: Hadoop YARN
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/250/
[Mar 6, 2017 4:34:51 PM] (aajisaka) HADOOP-14108. CLI MiniCluster: add an
option to specify NameNode HTTP
[Mar 6, 2017 6:47:15 PM] (wang) HDFS-11441. Add escaping to error message in
KMS web UI. Contribute
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/338/
[Mar 6, 2017 11:04:03 AM] (yqlin) HDFS-8741. Proper error msg to be printed
when invalid operation type is
[Mar 6, 2017 4:34:51 PM] (aajisaka) HADOOP-14108. CLI MiniCluster: add an
option to specify NameNo
[
https://issues.apache.org/jira/browse/YARN-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haibo Chen resolved YARN-3471.
--
Resolution: Not A Problem
> Fix timeline client retry
> -
>
> Key
I don't think there should be any linkage between releasing 2.8.0 and
2.7.4. If we have a volunteer for releasing 2.7.4, we should go full speed
ahead. We still need a volunteer from a PMC member or a committer as some
tasks may require certain privileges, but I don't think it precludes
working wit
In hadoop 2.4.0
NM always have 100+ AppLogAggregatorImpl threads running,
Normally,only 20+ containers will running all time,so if there is any issue
about the AppLogAggregator leak.
I observe these threads is all waiting,because the logic of code is:
While(If not appFinshed)
Wait(1s);
Like this:
Feng Yuan created YARN-6295:
---
Summary: AppLogAggregatorImpl thread leak
Key: YARN-6295
URL: https://issues.apache.org/jira/browse/YARN-6295
Project: Hadoop YARN
Issue Type: Bug
Components
Is there any reason to wait for 2.8 with 2.7.4?
Unfortunately the previous thread about release cadence has been ended without
final decision. But if I understood well, there was more or less an agreement
about that it would be great to achieve more frequent releases, if possible
(with or with
22 matches
Mail list logo
