* Verified mds and pgp signatures of both source and binary* Built tarball from
source on OS X 10.11.6 (El Capitan)* Deployed in pseudo-distributed mode* Ran
sleep jobs and other randomly selected tests on both MapReduce and Tez*
Visually verified the RM and history server UIs
Thanks,
Eric
+1 (non-binding)
- Verified signatures and md5- Built from source- Started single-node cluster
on my mac- Ran some sleep jobs
Eric
On Tuesday, January 24, 2017 4:32 PM, Yufei Gu wrote:
Hi Andrew,
Thanks for working on this.
+1 (Non-Binding)
1. Downloaded the
wed a successful job, but as you
can see, I did not have anything printed onto the command line. Hopefully this
is just a misconfiguration on my part, but I figured that I would point it out
just in case.
Thanks,
Eric
On Tuesday, August 30, 2016 4:00 PM, Eric Badger
<ebad...@yahoo-inc.com.INVALI
PM, Allen Wittenauer
<a...@effectivemachines.com> wrote:
> On Aug 30, 2016, at 2:06 PM, Eric Badger <ebad...@yahoo-inc.com.INVALID>
> wrote:
>
>
> WARNING: log4j.properties is not found. HADOOP_CONF_DIR may be incomplete.
^^
>
>
All on OSX 10.11.6:
Verified the hashes. However, Andrew, I don't know where to find your public
key, so I wasn't able to verify that they were signed by you.Built from
sourceDeployed a pseudo-distributed clusterRan a few sample jobsPoked around
the RM UIPoked around the attached website
+1 non-binding
All on OSX 10.11.6:Verified signatures of source and binary tarballsCompiled
from sourceDeployed pseudo clusterRan sample jobs
Thanks,
Eric
On Tuesday, August 23, 2016 1:26 PM, Xuan Gong
wrote:
+1 Binding.
Built from source code.
Deployed single
This is an issue with maven. It uses the same .m2 directory across both of the
builds unless you specify otherwise and they stomp all over each other. What I
do to get around this issue is to create 2 separate .m2 directories with their
own unique settings.xml file. The settings.xml files are
+1 (non-binding)
- Verified checksums and signatures of all files
- Built from source on MacOS Sierra via JDK 1.8.0 u65
- Deployed single-node cluster
- Successfully ran a few sample jobs
Thanks,
Eric
On Tuesday, March 21, 2017 2:56 PM, John Zhuge wrote:
+1. Thanks
- Verified all checksums signatures
- Built from src on macOS 10.12.5 with Java 1.8.0u65
- Deployed single node pseudo cluster
- Successfully ran sleep and pi jobs
- Navigated the various UIs
+1 (non-binding)
Thanks,
Eric
On Thursday, July 6, 2017 3:31 PM, Aaron Fabbri
- Verified all checksums signatures
- Built from src on macOS 10.12.6 with Java 1.8.0u65
- Deployed single node pseudo cluster
- Successfully ran sleep and pi jobs
- Navigated the various UIs
+1 (non-binding)
Thanks,
Eric
On Wednesday, August 2, 2017 12:31 PM, Chris Douglas
+1 definitely think an official Hadoop docker image (possibly 1 per major
or minor release) would be a positive both for contributors and for users
of Hadoop.
Eric
On Wed, Sep 13, 2017 at 1:19 PM, Wangda Tan wrote:
> +1 to add Hadoop docker image for easier testing /
+1 (non-binding)
- Verified all checksums and signatures
- Built native from source on macOS 10.12.6 and RHEL 7.1
- Deployed a single node pseudo cluster
- Ran pi and sleep jobs
- Verified Docker was marked as experimental
Thanks,
Eric
On Tue, Oct 3, 2017 at 1:41 PM, John Zhuge
+1 (non-binding)
- Verified all hashes and checksums
- Built from source on macOS 10.12.6, Java 1.8.0u65
- Deployed a pseudo cluster
- Ran some example jobs
Thanks,
Eric
On Wed, Nov 15, 2017 at 10:24 AM, Carlo Aldo Curino
wrote:
> +1 (binding)
>
> On Nov 15, 2017 8:23
Thanks, Junping
+1 (non-binding) looks good from my end
- Verified all hashes and checksums
- Built from source on macOS 10.12.6, Java 1.8.0u65
- Deployed a pseudo cluster
- Ran some example jobs
Eric
On Tue, Dec 12, 2017 at 12:55 PM, Konstantin Shvachko
wrote:
>
Thanks, Konstantin. Everything looks good to me
+1 (non-binding)
- Verified all signatures and digests
- Built from source on macOS 10.12.6, Java 1.8.0u65
- Deployed a pseudo cluster
- Ran some example jobs
Eric
On Tue, Dec 12, 2017 at 11:01 AM, Jason Lowe wrote:
>
+1 (non-binding) pending the issue that Sunil/Rohith pointed out
- Verified all hashes and checksums
- Built from source on macOS 10.12.6, Java 1.8.0u65
- Deployed a pseudo cluster
- Ran some example jobs
Thanks,
Eric
On Tue, Nov 7, 2017 at 4:03 PM, Wangda Tan wrote:
>
+1 (non-binding)
- Verified all hashes and checksums
- Built from source on macOS 10.12.6, Java 1.8.0u65
- Deployed a pseudo cluster
- Ran some example jobs
Thanks,
Eric
On Tue, Oct 24, 2017 at 12:59 AM, Mukul Kumar Singh
wrote:
> Thanks Junping,
>
> +1 (non-binding)
+1 (non-binding)
- Verified all hashes and checksums
- Built from source on macOS 10.13.4, Java 1.8.0u65
- Deployed a pseudo cluster
- Ran some example jobs
Eric
On Thu, Apr 26, 2018 at 11:16 PM, Takanobu Asanuma
wrote:
> Thanks for working on this, Sammi!
>
> +1
My thinking is to cut the branch in next couple of days and create RC for
vote at the end of month.
> We plan to cut branch-3.0.3 by the coming Wednesday (May 9th) and vote
for RC on May 30th
I much prefer to wait to cut the branch until just before the production
of the release and the vote.
+1 (non-binding)
- Verified all hashes and checksums
- Built from source on macOS 10.13.6, Java 1.8.0u65
- Deployed a pseudo cluster
- Ran some example jobs
On Tue, Aug 7, 2018 at 8:46 AM, Shashikant Banerjee <
sbaner...@hortonworks.com> wrote:
> +1(non-binding)
>
> * checked out git tag
+1 (non-binding)
- Verified all hashes and checksums
- Built from source on macOS 10.13.6, Java 1.8.0u65
- Deployed a pseudo cluster
- Ran some example jobs
Eric
On Tue, Sep 11, 2018 at 1:39 PM, Gabor Bota wrote:
> Thanks for the work Junping!
>
> +1 (non-binding)
>
> - checked out git
+1 (non-binding)
- Verified all hashes and checksums
- Built from source on macOS 10.14.1, Java 1.8.0u65
- Deployed a pseudo cluster
- Ran some example jobs
Eric
On Tue, Nov 27, 2018 at 7:02 AM Ayush Saxena wrote:
> Sunil, Thanks for driving this release!!!
>
> +1 (non-binding)
> -Built from
+1 (non-binding)
- Verified all hashes and checksums
- Built from source on RHEL 7
- Deployed a single node pseudo cluster
- Ran some example jobs
- Verified the Docker environment works with non-entrypoint mode
Eric
On Tue, Jan 8, 2019 at 5:42 AM Sunil G wrote:
> Hi folks,
>
>
> Thanks to
Is there a YARN call today (in 16 minutes)? I saw it on the calendar until
a few minutes ago.
Eric
On Tue, Jun 18, 2019 at 11:18 PM Wangda Tan wrote:
> Thanks @Wei-Chiu Chuang . updated gdoc
>
> On Tue, Jun 18, 2019 at 7:35 PM Wei-Chiu Chuang
> wrote:
>
> > Thanks Wangda,
> >
> > I just like
It seems as though ebugs is running a static code analyzer across all of
hadoop and creating a new JIRA for every issue it finds (15 JIRAs in the
past 3 hours). While this could potentially be useful, I don't think it's a
good idea at all to file a new JIRA for every single issue that is found.
It
- Stuff has been going into branch-2 sporadically but I don't who is
actively
using that code other than as part of a cherrypick backwards strategy.
- Should we do a 2.10.x release? Or just say "time to upgrade?"
We have talked at a few different Hadoop contributors meetups and community
syncs
+1
On Wed, Aug 21, 2019 at 9:40 AM Sean Busbey
wrote:
> +1
>
> On Tue, Aug 20, 2019 at 10:03 PM Wangda Tan wrote:
> >
> > Hi all,
> >
> > This is a vote thread to mark any versions smaller than 2.7 (inclusive),
> > and 3.0 EOL. This is based on discussions of [1]
> >
> > This discussion runs
Where would JIRA fit into the PR workflow? Would we file JIRAs just to
track github PRs and have all of the discussion on the PR?
Eric
On Mon, Jul 22, 2019 at 1:10 PM Dinesh Chitlangia
wrote:
> +1 Absolutely. It also makes it easy/clean for reviewers to leave specific
> comments and the
We (Verizon Media) are currently moving towards upgrading our clusters from
our internal fork of branch-2.8 to an internal fork of branch-2. During
this process, we have found multiple incompatible changes in protobufs
between branch-2.8 and branch-2. These incompatibilities were all
introduced
Hi Runlin,
Awesome to hear that you've been able to upgrade! Do you mind sharing some
thoughts on your experience with the upgrade? Did you take a cluster
downtime to do the upgrade? How long did the upgrade take? Did you find any
incompatibilities or issues during or after the upgrade? Do you
Hi Jonathan,
Thanks for putting this RC together. You stated that there are improvements
related to rolling upgrades from 2.x to 3.x and I know I have seen multiple
JIRAs getting committed to that effect. Could you describe any tests that
you have done to verify rolling upgrade compatibility for
Hello all,
Is it written anywhere what the difference is between a minor release and a
point/dot/maintenance (I'll use "point" from here on out) release? I have
looked around and I can't find anything other than some compatibility
documentation in 2.x that has since been removed in 3.x [1] [2]. I
From: Jonathan Hung
> Sent: Tuesday, September 24, 2019 11:38 AM
> To: Eric Badger
> Cc: Hadoop Common; yarn-dev; mapreduce-dev; Hdfs-dev
> Subject: Re: Incompatible changes between branch-2.8 and branch-2.9
>
> Hi Eric, thanks for the investigation.
>
> * For YARN-661
tegy? It should be OK to remove/add optional
> > fields (removing the field with id 12, and adding the field with id 13).
> > The difficulties I see here are, we would have to leave id 12 blank in
> > 2.8.6 (so we cannot have YARN-6164 in branch-2.8), and users on 2.8.4/5
> > w
Hi Xiaoqiao,
I believe that
https://github.com/apache/hadoop/commit/3274fd139d9b612e449fc234f8804a2a97ae6c47
broke compilation for branch-3.2. Looks like you missed a 3.2.2 -> 3.2.3 in
pom.xml in the top-level directory.
Hi,
Could I get some people to review this JIRA? It is a large patch and
touches a lot of files. Additionally, it makes some incompatible changes,
notably changing the names of config keys.
https://issues.apache.org/jira/browse/HADOOP-17169
Eric
+1 (non-binding)
- Verified all hashes and checksums
- Built from source on RHEL 7
- Deployed a single node pseudo cluster
- Ran some example jobs
Only minor thing is that the DockerLinuxContainerRuntime won't run in a
secure environment using kerberos and nscd because there is no way to
Congrats, Jim! Well-deserved and much overdue!
Eric
On Mon, Aug 3, 2020 at 11:38 AM epa...@apache.org wrote:
> I am pleased to announce that Jim Brennan has accepted the invitation to
> become a Hadoop committer focusing on the YARN space.
>
> Please reach out to Jim and welcome him in his new
+1 (binding)
- Built from source on RHEL 7.6
- Deployed on a single-node cluster
- Verified DefaultContainerRuntime
- Verified RuncContainerRuntime (after setting things up with the
docker-to-squash tool available on YARN-9564)
Eric
I've committed https://issues.apache.org/jira/browse/YARN-10540. Xiaoqiao,
feel free to cherry-pick this into the 3.2.2 release branch if you think it
is relevant.
Also, can someone tell me which releases we should be targeting? Currently
these versions are all Unreleased on JIRA:
3.4.1, 3.4.0
Works for me. I'll be there
Eric
On Tue, Nov 17, 2020 at 12:04 PM Craig.Condit
wrote:
> Hi everone,
>
> I'd like to propose a topic for tomorrow's YARN community sync. I've
> created a few JIRAs relating to enhancing the runc container support in
> YARN (YARN-10493 and YARN-10494) and would
+1
On Thu, Jun 3, 2021 at 6:14 AM Surendra Singh Lilhore <
surendralilh...@gmail.com> wrote:
> +1
>
> Thanks and Regards
> Surendra
>
>
> On Thu, Jun 3, 2021 at 4:31 PM tom lee wrote:
>
> > +1
> >
> > Masatake Iwasaki 于2021年6月3日周四 下午5:43写道:
> >
> > > +1
> > >
> > > Masatake Iwasaki
> > >
> > >
Hello all,
I'd like to gauge the community on the usage of lambdas within Hadoop code.
I've been reviewing a lot of patches recently that either add or modify
lambdas and I'm beginning to think that sometimes we, as a community, are
writing lambdas because we can rather than because we should. To
at 1:18 PM Eric Badger wrote:
> If we're not using patches on JIRA anymore, why are we using JIRA at all?
> Why don't we just use GitHub Issues? Using JIRA to then redirect to GitHub
> seems unintuitive and will fracture the information between two different
> places. Do the conversa
If we're not using patches on JIRA anymore, why are we using JIRA at all?
Why don't we just use GitHub Issues? Using JIRA to then redirect to GitHub
seems unintuitive and will fracture the information between two different
places. Do the conversations happen on JIRA or on a GitHub PR? Having
Eric Badger created YARN-4756:
-
Summary: Unnecessary wait in Node Status Updater during reboot
Key: YARN-4756
URL: https://issues.apache.org/jira/browse/YARN-4756
Project: Hadoop YARN
Issue Type
Eric Badger created YARN-5069:
-
Summary: TestFifoScheduler.testResourceOverCommit race condition
Key: YARN-5069
URL: https://issues.apache.org/jira/browse/YARN-5069
Project: Hadoop YARN
Issue
Eric Badger created YARN-5462:
-
Summary:
TestNodeStatusUpdater.testNodeStatusUpdaterRetryAndNMShutdown fails
intermittently
Key: YARN-5462
URL: https://issues.apache.org/jira/browse/YARN-5462
Project
Eric Badger created YARN-5463:
-
Summary:
TestResourceLocalizationService.testPublicResourceInitializesLocalDir fails
Intermittently due to IllegalArgumentException from cleanup
Key: YARN-5463
URL: https
[
https://issues.apache.org/jira/browse/YARN-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Badger resolved YARN-5463.
---
Resolution: Duplicate
Closing as a dup of YARN-4717. Not sure how I didn't see the old one before I
[
https://issues.apache.org/jira/browse/YARN-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Badger resolved YARN-5700.
---
Resolution: Cannot Reproduce
Revisited this and I cannot reproduce the failure. Closing as cannot
Eric Badger created YARN-5622:
-
Summary: TestYarnCLI.testGetContainers fails due to mismatched
date formats
Key: YARN-5622
URL: https://issues.apache.org/jira/browse/YARN-5622
Project: Hadoop YARN
Eric Badger created YARN-5641:
-
Summary: Localizer leaves behind tarballs after container is
complete
Key: YARN-5641
URL: https://issues.apache.org/jira/browse/YARN-5641
Project: Hadoop YARN
Eric Badger created YARN-5700:
-
Summary: testAMRestartNotLostContainerCompleteMsg times out
intermittently in 2.8
Key: YARN-5700
URL: https://issues.apache.org/jira/browse/YARN-5700
Project: Hadoop YARN
Eric Badger created YARN-5752:
-
Summary: TestLocalResourcesTrackerImpl#testLocalResourceCache
times out
Key: YARN-5752
URL: https://issues.apache.org/jira/browse/YARN-5752
Project: Hadoop YARN
Eric Badger created YARN-5994:
-
Summary: TestCapacityScheduler.testAMLimitUsage fails
intermittently
Key: YARN-5994
URL: https://issues.apache.org/jira/browse/YARN-5994
Project: Hadoop YARN
Eric Badger created YARN-5957:
-
Summary: NMWebAppFilter currently drops end of URL during
container log redirection
Key: YARN-5957
URL: https://issues.apache.org/jira/browse/YARN-5957
Project: Hadoop
Eric Badger created YARN-6441:
-
Summary: Improve UI error message while trying to sort running
DAGs with Auto Refresh enabled
Key: YARN-6441
URL: https://issues.apache.org/jira/browse/YARN-6441
Project
Eric Badger created YARN-6479:
-
Summary: TestDistributedShell.testDSShellWithoutDomainV1_5 fails
Key: YARN-6479
URL: https://issues.apache.org/jira/browse/YARN-6479
Project: Hadoop YARN
Issue
Eric Badger created YARN-6480:
-
Summary: Timeout is too aggressive for
TestAMRestart.testPreemptedAMRestartOnRMRestart
Key: YARN-6480
URL: https://issues.apache.org/jira/browse/YARN-6480
Project: Hadoop
Eric Badger created YARN-6988:
-
Summary: container-executor fails for docker when command length >
4096 B
Key: YARN-6988
URL: https://issues.apache.org/jira/browse/YARN-6988
Project: Hadoop Y
Eric Badger created YARN-6749:
-
Summary: TestAppSchedulingInfo.testPriorityAccounting fails
consistently
Key: YARN-6749
URL: https://issues.apache.org/jira/browse/YARN-6749
Project: Hadoop YARN
Eric Badger created YARN-6536:
-
Summary: TestAMRMClient.testAMRMClientWithSaslEncryption fails
intermittently
Key: YARN-6536
URL: https://issues.apache.org/jira/browse/YARN-6536
Project: Hadoop YARN
Eric Badger created YARN-6919:
-
Summary: Add default volume mount list
Key: YARN-6919
URL: https://issues.apache.org/jira/browse/YARN-6919
Project: Hadoop YARN
Issue Type: Sub-task
Eric Badger created YARN-7025:
-
Summary: Make CGROUPS_ROOT_DIRECTORY configurable in
DockerLinuxContainerRuntime
Key: YARN-7025
URL: https://issues.apache.org/jira/browse/YARN-7025
Project: Hadoop YARN
Eric Badger created YARN-7040:
-
Summary: TestConfigurationNodeLabelsProvider.testConfigTimer
Key: YARN-7040
URL: https://issues.apache.org/jira/browse/YARN-7040
Project: Hadoop YARN
Issue Type
Eric Badger created YARN-6552:
-
Summary: Increase YARN test timeouts from 1 second to 10 seconds
Key: YARN-6552
URL: https://issues.apache.org/jira/browse/YARN-6552
Project: Hadoop YARN
Issue
Eric Badger created YARN-7189:
-
Summary: Docker doesn't remove containers that error out early
Key: YARN-7189
URL: https://issues.apache.org/jira/browse/YARN-7189
Project: Hadoop YARN
Issue Type
Eric Badger created YARN-7231:
-
Summary: Make Docker target directory for cgroups configurable by
yarn-site.xml
Key: YARN-7231
URL: https://issues.apache.org/jira/browse/YARN-7231
Project: Hadoop YARN
Eric Badger created YARN-7114:
-
Summary: NM can fail during shutdown with log aggregation
Key: YARN-7114
URL: https://issues.apache.org/jira/browse/YARN-7114
Project: Hadoop YARN
Issue Type: Bug
[
https://issues.apache.org/jira/browse/YARN-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Badger resolved YARN-7025.
---
Resolution: Duplicate
> Make CGROUPS_ROOT_DIRECTORY configurable in DockerLinuxContainerRunt
Eric Badger created YARN-7353:
-
Summary: Docker permitted volumes don't properly check for
directories
Key: YARN-7353
URL: https://issues.apache.org/jira/browse/YARN-7353
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Badger resolved YARN-7344.
---
Resolution: Duplicate
Assignee: (was: Eric Badger)
Sounds good. I'll dup this JIRA
Eric Badger created YARN-7644:
-
Summary: NM gets backed up deleting docker containers
Key: YARN-7644
URL: https://issues.apache.org/jira/browse/YARN-7644
Project: Hadoop YARN
Issue Type: Sub
Eric Badger created YARN-7667:
-
Summary: Docker Stop grace period should be configurable
Key: YARN-7667
URL: https://issues.apache.org/jira/browse/YARN-7667
Project: Hadoop YARN
Issue Type: Sub
Eric Badger created YARN-7395:
-
Summary: NM fails to successfully kill tasks that run over their
memory limit
Key: YARN-7395
URL: https://issues.apache.org/jira/browse/YARN-7395
Project: Hadoop YARN
Eric Badger created YARN-8261:
-
Summary: Docker container launch fails due to .cmd file creation
failure
Key: YARN-8261
URL: https://issues.apache.org/jira/browse/YARN-8261
Project: Hadoop YARN
Eric Badger created YARN-8335:
-
Summary: Privileged docker containers' jobSubmitDir does not get
successfully cleaned up
Key: YARN-8335
URL: https://issues.apache.org/jira/browse/YARN-8335
Project
[
https://issues.apache.org/jira/browse/YARN-8335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Badger resolved YARN-8335.
---
Resolution: Duplicate
> Privileged docker containers' jobSubmitDir does not get successfully clea
[
https://issues.apache.org/jira/browse/YARN-8343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Badger resolved YARN-8343.
---
Resolution: Duplicate
> YARN should have ability to run images only from a whitelist doc
Eric Badger created YARN-8241:
-
Summary: MRAppMaster fails when using UID:GID pair within docker
container
Key: YARN-8241
URL: https://issues.apache.org/jira/browse/YARN-8241
Project: Hadoop YARN
Eric Badger created YARN-7848:
-
Summary: Force removal of docker containers that do not get
removed on first try
Key: YARN-7848
URL: https://issues.apache.org/jira/browse/YARN-7848
Project: Hadoop YARN
Eric Badger created YARN-7904:
-
Summary: Privileged, trusted containers need all of their
bind-mounted directories to be read-only
Key: YARN-7904
URL: https://issues.apache.org/jira/browse/YARN-7904
Eric Badger created YARN-7915:
-
Summary: Trusted image log message repeated multiple times
Key: YARN-7915
URL: https://issues.apache.org/jira/browse/YARN-7915
Project: Hadoop YARN
Issue Type
Eric Badger created YARN-7960:
-
Summary: Add no-new-privileges flag to docker run
Key: YARN-7960
URL: https://issues.apache.org/jira/browse/YARN-7960
Project: Hadoop YARN
Issue Type: Sub-task
Eric Badger created YARN-7677:
-
Summary: HADOOP_CONF_DIR should not be automatically put in task
environment
Key: YARN-7677
URL: https://issues.apache.org/jira/browse/YARN-7677
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Badger resolved YARN-8241.
---
Resolution: Won't Fix
We do not plan to support running containers in which a user lookup cannot
[
https://issues.apache.org/jira/browse/YARN-7197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Badger resolved YARN-7197.
---
Resolution: Won't Fix
There are currently no plans to attempt to implement this feature. Feel free
[
https://issues.apache.org/jira/browse/YARN-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Badger resolved YARN-3611.
---
Resolution: Fixed
We have closed out Phase 1 of Docker container support and are now moving onto
Eric Badger created YARN-8064:
-
Summary: Docker ".cmd" files should not be put in hadoop.tmp.dir
Key: YARN-8064
URL: https://issues.apache.org/jira/browse/YARN-8064
Project: Hadoop YARN
Eric Badger created YARN-8206:
-
Summary: Sending a kill does not immediately kill docker containers
Key: YARN-8206
URL: https://issues.apache.org/jira/browse/YARN-8206
Project: Hadoop YARN
Issue
[
https://issues.apache.org/jira/browse/YARN-8786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Badger resolved YARN-8786.
---
Resolution: Duplicate
Sounds good. Resolving this as a duplicate of YARN-8751
Eric Badger created YARN-9564:
-
Summary: Create docker-to-squash tool for image conversion
Key: YARN-9564
URL: https://issues.apache.org/jira/browse/YARN-9564
Project: Hadoop YARN
Issue Type
Eric Badger created YARN-9582:
-
Summary: Port YARN-8569 to FSImageContainerRuntime
Key: YARN-9582
URL: https://issues.apache.org/jira/browse/YARN-9582
Project: Hadoop YARN
Issue Type: Sub-task
Eric Badger created YARN-9561:
-
Summary: Add C changes for the new OCI/squashfs/runc runtime
Key: YARN-9561
URL: https://issues.apache.org/jira/browse/YARN-9561
Project: Hadoop YARN
Issue Type
Eric Badger created YARN-9560:
-
Summary: Restructure DockerLinuxContainerRuntime to extend a new
OCIContainerRuntime
Key: YARN-9560
URL: https://issues.apache.org/jira/browse/YARN-9560
Project: Hadoop
Eric Badger created YARN-9562:
-
Summary: Add Java changes for the new OCI/squashfs/runc runtime
Key: YARN-9562
URL: https://issues.apache.org/jira/browse/YARN-9562
Project: Hadoop YARN
Issue
Eric Badger created YARN-9818:
-
Summary: test_docker_util.cc:test_add_mounts doesn't correctly
test for parent dir of container-executor.cfg
Key: YARN-9818
URL: https://issues.apache.org/jira/browse/YARN-9818
Eric Badger created YARN-9959:
-
Summary: Work around hard-coded tmp and /var/tmp bind-mounts in
the container's working directory
Key: YARN-9959
URL: https://issues.apache.org/jira/browse/YARN-9959
Eric Badger created YARN-9943:
-
Summary: Investigate image/tag management and how to do
docker-to-squash conversion at scale
Key: YARN-9943
URL: https://issues.apache.org/jira/browse/YARN-9943
Project
1 - 100 of 111 matches
Mail list logo