Thanks for the votes and discussion. It is now past Monday Oct 9 11:00AM
PDT so the vote has ended. There were 4 +1 and no -1, so vote passes. This
feature will be merged to trunk, branch-3.0, and branch-2 shortly (16
subtasks).
Thanks everyone!
Jonathan Hung
On Mon, Oct 9, 2017 at 9:18 AM
on the
last week of Sept.
Please let me know if you have any concerns. Thanks!
Jonathan Hung
On Wed, Jul 26, 2017 at 11:23 AM, J. Rottinghuis <jrottingh...@gmail.com>
wrote:
> Thanks Vrushali for being entirely open as to the current status of ATSv2.
> I appreciate that we want to e
was to merge this to trunk (which is what the YARN-7241
diff is based on), and port to branch-2 before the 2.9 release. @Andrew,
what are your thoughts on also merging this to branch-3.0?
Thanks!
Jonathan Hung
hou.
[1]
http://mail-archives.apache.org/mod_mbox/hadoop-yarn-dev/201709.mbox/%3CCAHzWLgfEAgczjcEOUCg-03ma3ROtO=pkec9dpggyx9rzf3n...@mail.gmail.com%3E
Jonathan Hung
re is also turned off by
default). Hoping to get this in before 3.0.0-GA. Just wanted to send this
note so that we are not caught off guard by this feature.
Thanks!
Jonathan Hung
On Fri, Aug 25, 2017 at 11:06 AM, Wangda Tan <wheele...@gmail.com> wrote:
> Resource profile is similar t
"yarn rmadmin -refreshQueues" enabled when configuration mutation
API disabled (and vice-versa)
- Tested queue admin configuration mutation policy
Jonathan Hung
On Mon, Nov 13, 2017 at 4:10 PM, Arun Suresh <asur...@apache.org> wrote:
> Hi Folks,
>
> Apache Hadoop 2
Thanks Konstantin for working on this.
+1 (non-binding)
- Downloaded binary and verified md5
- Deployed RM HA and tested failover
Jonathan Hung
On Wed, Dec 13, 2017 at 11:02 AM, Eric Payne <erichadoo...@yahoo.com.invalid
> wrote:
> Thanks for the hard work on this release, Konstan
on restart/failover
- Verified "yarn rmadmin -refreshQueues" works when scheduler configuration
API disabled, and does not work when scheduler configuration API enabled
Jonathan Hung
On Tue, Dec 12, 2017 at 5:44 PM, Junping Du <j...@hortonworks.com> wrote:
> Thanks Andrew
API
disabled (and vice-versa)
Jonathan Hung
On Tue, Nov 7, 2017 at 2:56 PM, Eric Badger <ebad...@oath.com> 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
>
- verified refreshQueues mutation is disabled in this case
Jonathan Hung
On Thu, Mar 22, 2018 at 9:10 AM, Wangda Tan <wheele...@gmail.com> wrote:
> Thanks @Bharat for the quick check, the previously staged repository has
> some issues. I re-deployed jars to nexus.
>
> Here's
branch-2, syncing any bug fixes in our internal fork
which did not make it to the feature branch, etc. Assuming no objections,
once it's ready we will start a vote to merge.
Thanks,
Jonathan Hung
+1!
Jonathan Hung
On Sat, Dec 15, 2018 at 8:26 AM Zhe Zhang wrote:
> +1
>
> Thanks for addressing concerns from the previous vote.
>
> On Fri, Dec 14, 2018 at 6:24 PM Konstantin Shvachko
> wrote:
>
> > Hi Hadoop developers,
> >
> > I would like to propo
Hi Jim, we have not tested rolling upgrade. I don’t foresee this being an
issue, but we’ll try it out and report back.
Jonathan
From: Jim Brennan
Sent: Tuesday, April 2, 2019 9:17 AM
To: Jonathan Hung
Cc: yarn-...@hadoop.apache.org; mapreduce-dev
'll start a merge vote next week.
Thanks.
Jonathan Hung
My non-binding +1 to finish. This vote passes with 6 binding +1, 3
non-binding +1, and no vetoes. We will make the changes as part
of HADOOP-15711, please follow there.
Thanks all!
Jonathan Hung
On Tue, Feb 5, 2019 at 11:38 PM Akira Ajisaka wrote:
> +1
>
> -Akira
>
> On Wed, F
+1. This is important for improving the deep learning on hadoop story.
There's recently a lot of momentum for this, and decoupling
submarine/hadoop will help it continue.
Jonathan Hung
On Thu, Jan 31, 2019 at 11:04 AM Wangda Tan wrote:
> Hi devs,
>
> Since we started submarine-relat
+1. Thanks Wangda.
Jonathan Hung
On Fri, Feb 1, 2019 at 2:25 PM Dinesh Chitlangia <
dchitlan...@hortonworks.com> wrote:
> +1 (non binding), thanks Wangda for organizing this.
>
> Regards,
> Dinesh
>
>
>
> On 2/1/19, 5:24 PM, "Wangda Tan" wrote:
>
-Build/
[3]
https://builds.apache.org/view/H-L/view/Hadoop/job/hadoop-qbt-branch2-java7-linux-x86/
Jonathan Hung
Sorry for the delay, had to deprioritize this. Hoping to get to this next week.
Jonathan
From: Jim Brennan
Sent: Thursday, April 18, 2019 7:28 AM
To: Jonathan Hung
Cc: yarn-...@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
Subject: Re: [DISCUSS] Merging
Hi Wangda, Thanks for starting the discussion. We would also like to
release 2.10.0 which was discussed previously
<https://www.mail-archive.com/yarn-dev@hadoop.apache.org/msg29479.html> and
at various contributor meetups. I'm interested in being release manager for
that.
Thanks,
Jonatha
Reviving this thread: we tested YARN RU starting with a cluster running
2.7.4, to running branch-2 + YARN-8200. Ran some simple MR/Spark jobs
concurrently with the RM/NM upgrades and did not see any issues.
If no other concerns I'll continue with a vote.
Jonathan Hung
On Thu, Apr 18, 2019 at 5
+1. Thanks!
Jonathan Hung
On Tue, Aug 20, 2019 at 8: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 for 7 days and will conclude on Aug
.
We're targeting a release at end of September.
Please share any thoughts you have about this. Thanks!
[1] https://www.mail-archive.com/yarn-dev@hadoop.apache.org/msg29461.html
[2]
https://www.mail-archive.com/mapreduce-dev@hadoop.apache.org/msg21293.html
[3] https://www.mail-archive.com/yarn-dev@hadoop.apache.org/msg33440.html
Jonathan Hung
Thanks all, +1 from me too.
There's three binding +1, two non-binding +1, and no -1 so I'll merge
YARN-8200 to branch-2 shortly. I'll skip branch-3.0 since it's EOL as
others have mentioned.
Jonathan Hung
On Tue, Aug 27, 2019 at 11:49 AM Konstantin Shvachko
wrote:
> +1 for the merge.
>
=csrqgysvpdf7mh-iu17femgx89dhr+1...@mail.gmail.com%3e
Jonathan Hung
be to move the
intraQueuePreemptionDisabled field from id 12 to id 13 in branch-2.8, then
users would upgrade from 2.8.4/2.8.5 to 2.8.6 (someone would have to
release this), then upgrade from 2.8.6 to 2.9+.
Jonathan Hung
On Tue, Sep 24, 2019 at 9:23 AM Eric Badger
wrote:
> We (Verizon Media) are currently m
Hi all,
I am happy to announce that the Apache Hadoop 2.10.0 has been released.
Apache Hadoop 2.10.0 is the first release in the Apache Hadoop 2.10 line.
The release details, including links to downloads, list of major features,
release notes, and changelog, are on the 2.10.0 announcement page
Some other additional items we would need:
- Mark all fix-versions in YARN/HDFS/MAPREDUCE/HADOOP from 2.11.0 to
2.10.1
- Remove 2.11.0 as a version in these projects
Jonathan Hung
On Thu, Nov 14, 2019 at 6:51 PM Jonathan Hung wrote:
> Hi folks,
>
> Given the release
This way we get all the current branch-2 fixes into the 2.10.x release
line. Then the commit chain will look like: trunk -> branch-3.2 ->
branch-3.1 -> branch-2.10 -> branch-2.9 -> branch-2.8
Thoughts?
Jonathan Hung
[1] https://www.mail-archive.com/yarn-dev@hadoop.apache.org/msg29479.html
. But this proposal would reduce a lot of confusion IMO.
Jonathan Hung
On Fri, Nov 15, 2019 at 11:41 AM epa...@apache.org
wrote:
> Thanks Jonathan for opening the discussion.
>
> I am not in favor of this proposal. 2.10 was very recently released, and
> moving to 2.10 will take some time for t
to use java 11 on branch-2, we can always
revive branch-2. But for now I think the convenience of not needing to port
to both branch-2 and branch-2.10 (and below) outweighs the cost of
potentially needing to revive branch-2.
Jonathan Hung
On Wed, Nov 20, 2019 at 10:50 AM Eric Yang wrote:
>
FYI, starting the rename process, beginning with INFRA-19521.
Jonathan Hung
On Wed, Nov 27, 2019 at 12:15 PM Konstantin Shvachko
wrote:
> Hey guys,
>
> I think we diverged a bit from the initial topic of this discussion, which
> is removing branch-2.10, and changing the version
old branch-2.10
- Rename branch-2 to (new) branch-2.10
- Set version in new branch-2.10 to 2.10.1-SNAPSHOT
- Renamed fix versions from 2.11.0 to 2.10.1
- Removed 2.11.0 as a version in HADOOP/YARN/HDFS/MAPREDUCE
Jonathan Hung
On Wed, Dec 4, 2019 at 10:55 AM Jonathan Hung wrote:
> FYI, s
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 from me too. The vote passed, so I'll continue with the rest of the
release.
Thanks everyone!
Jonathan Hung
On Tue, Oct 29, 2019 at 1:40 PM Giovanni Matteo Fumarola <
giovanni.fumar...@gmail.com> wrote:
> +1 (non-binding).
>
> - Built from source on Ubuntu with OpenJDK 11.0
://repository.apache.org/content/repositories/orgapachehadoop-1243/
My public key is available here:
https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
The vote will run for 5 weekdays, until Tuesday, October 29 at 3:00 pm PDT.
Thanks,
Jonathan Hung
[1]
https://issues.apache.org/jira/issues/?jql
in dominant resource calculator, but root cause remains
to be seen.
Jonathan Hung
On Wed, Oct 23, 2019 at 9:02 AM epa...@apache.org wrote:
> Hi Jonathan,
>
> Thanks very much for all of your work on this release.
>
> I have a concern about cross-queue (inter-queue) preemption in 2
I've moved all jiras with target version 2.10.0 to 2.10.1. Also I've
created branch-2.10 and branch-2.10.0, please commit any 2.10.x bug fixes
to branch-2.10.
I'll send out a vote thread for 2.10.0-RC0 shortly.
Jonathan Hung
On Fri, Oct 11, 2019 at 10:32 AM Jonathan Hung wrote:
> Edit: se
/repositories/orgapachehadoop-1241/
My public key is available here:
https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
The vote will run for 5 weekdays, until Wednesday, October 23 at 6:00 pm
PDT.
Thanks,
Jonathan Hung
[1]
https://issues.apache.org/jira/issues/?jql=project%20in%20(HDFS%2C
to be correct.
I think we could easily overwrite the current RC1 artifacts with ones
containing proper release notes. Not sure what to do about the javadoc
issue though, that would require overwriting the release-2.10.0-RC1 tag
which I don't want to do. What do others think?
Jonathan Hung
On Fri
Hi Eric, I took a quick look, are you using
mapreduce.application.framework.path to run your MR jobs? If not, this
seems like expected behavior if AM and tasks get launched on different NMs
with different locally installed hadoop versions?
Jonathan Hung
On Sat, Oct 26, 2019 at 8:55 AM epa
be up to date, but
I think that's fine.
I'll go ahead with this plan if no objections.
Jonathan Hung
On Fri, Oct 25, 2019 at 12:19 PM Jonathan Hung wrote:
> Thanks for looking Erik.
>
> For the release notes, yeah I think it's because there's no release notes
> for the corresponding
Thanks Konstantin and Zhankun. Unfortunately a feature slipped our radar
(HDFS-14667). Since this is the first of a minor release, we would like to
get it into 2.10.0.
HDFS-14667 has been committed to branch-2.10.0, I will be rolling an RC1
shortly.
Jonathan Hung
On Tue, Oct 22, 2019 at 1:39
Hi Eric, we've run some basic HDFS commands with a 3.2.1 namenode and
2.10.0 clients and datanodes. Everything worked as expected.
Jonathan Hung
On Tue, Oct 22, 2019 at 3:04 PM Eric Badger
wrote:
> Hi Jonathan,
>
> Thanks for putting this RC together. You stated that there are
>
Sorry, let me edit my first point. We can just create addendums for YARN-6616
in branch-2.7 and branch-2.8 to edit the submitTime field to the correct id 28.
We don’t need to revert YARN-6616 from these branches completely.
Jonathan
From: Jonathan Hung
Sent
2.9+. But rolling upgrade
would still work IIUC.
Jonathan Hung
On Tue, Sep 24, 2019 at 2:52 PM Eric Badger
wrote:
> * For YARN-6616, for branch-2.8 and below, it was only committed to
> 2.7.8/2.8.6 which have not been released (as I understand). Perhaps we can
> revert YARN-6616 fro
Hi folks, as of now all 2.10.0 blockers have been resolved [1]. So I'll
start the release process soon (cutting branches, updating target versions,
etc).
[1] https://issues.apache.org/jira/issues/?filter=12346975
Jonathan Hung
On Mon, Aug 26, 2019 at 10:19 AM Jonathan Hung wrote:
> Hi fo
Edit: seems a 2.10.0 blocker was reopened (HDFS-14305). I'll continue
watching this jira and start the release once this is resolved.
Jonathan Hung
On Thu, Oct 10, 2019 at 5:13 PM Jonathan Hung wrote:
> Hi folks, as of now all 2.10.0 blockers have been resolved [1]. So I'll
>
Makes sense. I've cherry-picked the commits in branch-2 that were missed in
branch-2.10.
Jonathan Hung
On Wed, Apr 15, 2020 at 2:25 AM Akira Ajisaka wrote:
> Hi folks,
>
> I am still seeing some changes are being committed to branch-2.
> I'd like to delete the source code f
Source code has been deleted from branch-2. Thanks Akira for taking this up!
Jonathan Hung
On Thu, Apr 16, 2020 at 11:40 AM Jonathan Hung wrote:
> Makes sense. I've cherry-picked the commits in branch-2 that were missed
> in branch-2.10.
>
> Jonathan Hung
>
>
> On Wed, Ap
[
https://issues.apache.org/jira/browse/MAPREDUCE-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hung resolved MAPREDUCE-6860.
--
Resolution: Not A Bug
> User intermediate-done-dir permissions should use hist
Jonathan Hung created MAPREDUCE-6860:
Summary: User intermediate-done-dir permissions should use history
file permissions configuration
Key: MAPREDUCE-6860
URL: https://issues.apache.org/jira/browse/MAPREDUCE
Jonathan Hung created MAPREDUCE-6885:
Summary: JobHistory event handler thread should not die if
exception thrown
Key: MAPREDUCE-6885
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6885
53 matches
Mail list logo
