We're going to fix the Submarine email list issues once spin-off works
start
On Wed, Oct 23, 2019 at 2:39 PM Matt Foley
wrote:
> Definitely yes on ‘ozone-issues’. Whether we want to keep ozone-dev and
> hdfs-dev together or separate, I’m neutral.
> Thanks,
> —Matt
>
> On Oct 23, 2019, at 2:11 P
+1, we should do that earlier than later. It is a code change that I think
we don't need to wait for 7 days vote.
On Thu, Oct 24, 2019 at 4:18 PM Anu Engineer
wrote:
> +1 for Ozone. We are in our own repo now. It would be good to remove this
> code from Hadoop, otherwise it will confuse new cont
+1, thanks Jonathan for bringing this up!
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 the community. It seems prematur
before with a lot of help from folks
>> > > especially Sunil. :D
>> > > And this time I would like to help to release the 3.1.4. Thanks!
>> > >
>> > > BR,
>> > > Zhankun
>> > >
>> > > Hui Fei 于2019年8月16日
> etag/version can be used to get the explicit version you want.)
> > >
> > > On Tue, Jan 7, 2020 at 2:18 AM Akira Ajisaka
> > wrote:
> > >
> > > > > I am interested on 3.3 release ..will act as RM .will update the
> > wiki
> > >
+1
On Mon, Mar 2, 2020 at 8:50 PM Akira Ajisaka wrote:
> +1
>
> -Akira
>
> On Tue, Mar 3, 2020 at 4:55 AM Ayush Saxena wrote:
>
> > +1 for marking 2.8 EOL
> >
> > -Ayush
> >
> > > On 03-Mar-2020, at 12:18 AM, Wei-Chiu Chuang
> wrote:
> > >
> > > I am sorry I forgot to start a VOTE thread.
> >
+1,
Thanks,
Wangda
On Thu, May 14, 2020 at 7:01 AM Tsuyoshi Ozawa wrote:
> +1
>
> Thanks
> - Tsuyoshi
>
> On Thu, May 14, 2020 at 19:42 Rakesh Radhakrishnan <
> rakeshr.oz...@gmail.com>
> wrote:
>
> > +1
> >
> > Thanks,
> > Rakesh
> >
> > On Wed, May 13, 2020 at 1:23 PM Elek, Marton wrote:
> >
Congrats!
Best,
Wangda Tan
On Thu, Jun 11, 2020 at 5:55 PM Tao Yang wrote:
> Congratulations Xiaoqiao!
>
> Best,
> Tao
>
>
> --
> 发件人：Weiwei Yang
> 发送时间：2020年6月12日(星期五) 02:24
> 收件人：Sree Vaddi
+1,
Thanks,
Wangda Tan
On Tue, Sep 29, 2020 at 10:10 AM Aravindan Vijayan
wrote:
> +1, thank you Marton.
>
> On Tue, Sep 29, 2020 at 9:17 AM Bharat Viswanadham
> wrote:
>
> > +1
> > Thank You @Elek, Marton for driving this.
> >
> >
> > Thanks,
&
> > From: Tsuyoshi Ozawa [oz...@apache.org]
> > Sent: Wednesday, October 28, 2015 23:13
> > To: Vinod Vavilapalli
> > Cc: yarn-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
> > common-...@hadoop.apache.org; Vinod Kumar Vavilapalli; Wangda Tan;
> > Tsuyo
Thanks to Vinod for starting this discussion!
+1 to add YARN-1197 (container resizing) to 2.8.0, it is end-to-end tested.
I'd prefer to push it as an Alpha feature before wilder testing.
And also agree to call first release of 2.8 as an Alpha release according
to the number of new features / code
+1 (Non-binding):
- Deployed local cluster from binary
- Configured CS with node label
- Ran jobs with/without labels
- Ran distributed shell / MR jobs.
Thanks,
Wangda
On Wed, Nov 11, 2015 at 8:31 PM, Vinod Kumar Vavilapalli wrote:
> Hi all,
>
>
> I've created a release candidate RC0 for Apach
Hi folks,
I found there're lots of commits are in branch-2 only.
Ran "git log branch-2.8..branch-2".
There're 35 commits for YARN, 41 commits for HDFS and 12 commits for
COMMON. Only several of them are placed in 2.9.0 section in CHANGES.txt.
I think we can either hard reset branch-2.8 to branch
sion%20%3D%202.9.0%20ORDER%20BY%20priority%20DESC
> ).
> >
> > So, we don’t need any drastic measures?
> >
> > Thanks
> > +Vinod
> >
> >> On Dec 16, 2015, at 5:38 PM, Wangda Tan wrote:
> >>
> >> Hi folks,
> >>
> &g
+1 (binding)
- Build & deploy single-node Hadoop from source code
- Add/Remove node labels to queues/nodes
- Run distributed shell commanding using default/specified node labels
Thanks,
Wangda
On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki <
iwasak...@oss.nttdata.co.jp> wrote:
> +1(non-bind
+1 (Binding), I tried to use YARN service assembly before to run different
kinds of jobs (for example, distributed Tensorflow), it is really easy for
end user to run jobs on YARN.
Thanks to the whole team for the great job!
Best,
Wangda
On Fri, Sep 1, 2017 at 3:33 PM, Gour Saha wrote:
> +1 (n
me know if you have any suggestions/concerns.
Thanks,
Wangda Tan
[1] http://markmail.org/message/hwar5f5ap654ck5o?q=
Branch+merges+and+3%2E0%2E0-beta1+scope
[2] http://markmail.org/message/hwar5f5ap654ck5o?q=Branch+
merges+and+3%2E0%2E0-beta1+scope#query:Branch%20merges%
20and%203.0.0-beta1%20scope+
; like to add to 3.1.0 is YARN Oversubscription (YARN-1011)
>
> Best,
> Haibo
>
> On Wed, Sep 6, 2017 at 11:13 AM, Wangda Tan wrote:
>
>> Hi all,
>>
>> As we discussed on [1], there were proposals from Steve / Vinod etc to
>> have
>> a faster c
Thanks Arun Suresh for creating the page.
+1 to have a page to track all planned releases, I also updated 3.1 release
plans.
Several suggestions:
1) Only put large features / changes which needed to be included by the
release, otherwise we will have too long list of JIRAs.
2) For release updates,
miss something?
> >
> > For those who haven't followed the feature closely, there are really two
> > features here. Resource types allows for declarative extension of the
> > resource system in YARN. Resource profiles builds on top of resource
> > types to
+1 to add Hadoop docker image for easier testing / prototyping, it gonna be
super helpful!
Thanks,
Wangda
On Wed, Sep 13, 2017 at 10:48 AM, Miklos Szegedi <
miklos.szeg...@cloudera.com> wrote:
> Marton, thank you for working on this. I think Official Docker images for
> Hadoop would be very usef
>
> > There were 15 subtasks completed for this feature.
> >
> > Huge thanks to everyone who helped with reviews, commits, guidance, and
> > technical discussion/design, including Carlo Curino, Xuan Gong, Subru
> > Krishnan, Min Shen, Konstantin Shvachko, Carl S
Hi,
Do we still have nightly (or even weekly) unit test run for Hadoop
projects? I couldn't find it on Jenkins dashboard and I haven't seen
reports set to dev lists for a while.
Thanks,
Wangda
and it sends e-mail to dev lists.
>> https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/
>>
>> Regards,
>> Akira
>>
>>
>> On 2017/10/19 7:54, Wangda Tan wrote:
>>
>>> Hi,
>>>
>>> Do we still have nightly (or eve
Thanks Junping,
+1 (binding).
Deployed a single node cluster and ran some simple jobs.
- Wangda
On Mon, Oct 23, 2017 at 4:05 PM, Chris Douglas wrote:
> +1 (binding)
>
> Looked through the src distribution. Checksum, signatures match, ran
> some of the unit tests. Also checked the site docs;
Thanks all for the great works!
+1 (Binding). Tried to use native services to build and run applications
successfully.
- Wangda
On Fri, Nov 3, 2017 at 11:50 AM, Arun Suresh wrote:
> +1 (binding)
>
> Cheers
> -Arun
>
> On Nov 3, 2017 11:44 AM, "Chandni Singh" wrote:
>
> > +1
> > Thanks,
> > Ch
Sunil / Rohith,
Could you check if your configs are same as Jonathan posted configs?
https://issues.apache.org/jira/browse/YARN-7453?focusedCommentId=16242693&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16242693
And could you try if using Jonathan's configs can s
Thanks Vinod for staring this,
I'm also leaning towards the plan (A):
* (A)-- Make 2.9.x the last minor release off branch-2-- Have a
maintenance release that bridges 2.9 to 3.x-- Continue to make more
maintenance releases on 2.8 and 2.9 as necessary*
The only part I'm not sure is
+1 (Binding).
Built from source, deployed pseudo cluster, ran sample jobs.
Thanks,
Wangda
On Wed, Nov 15, 2017 at 8:34 PM, Brahma Reddy Battula
wrote:
> +1 ( non-binding)
>
> -Built from the source
> -Installed 3 Node HA cluster and a pseudo cluster
> -Verified through hdfs shell commands
> -V
Thanks Junping for driving this.
For the bug fix vs. improvement, it is actually very hard to define,
improvement could be self-contained and useful, bug fix could be dangerous
in some cases. To me, If an improvement fixed some existing use case, and
the fix is self-contained. I will be open to br
are running this in our
> development cluster for last couple of months and undergone good amount of
> testing. Branch code is run against trunk and tracked via [4].
>
> We would love to get your thoughts before opening a voting thread.
>
> Special thanks to a team of folks who wo
+1, thanks Sunil!
Wangda Tan
On Wed, Nov 29, 2017 at 5:56 PM, Sunil G wrote:
> Hi All,
>
>
> Based on the discussion at [1], I'd like to start a vote to merge feature
> branch
>
> YARN-5881 to trunk. Vote will run for 7 days, ending Wednesday Dec 6 at
> 6:00P
+1 (Binding).
Built from source and deployed a cluster, jobs can run successfully.
Thanks Junping for driving this.
Best,
Wangda
On Tue, Dec 12, 2017 at 5:18 PM, Chandni Singh
wrote:
> +1
> Built the source code.
> Deployed a single node cluster and ran example jobs. Also tested RM
> recover
Thanks Andrew for driving this.
+1 (Binding)
Ran SLS + CS's Perf unit test and saw similar performance compared to
trunk.
Compiled from source, deployed single node cluster and ran several jobs.
Best,
Wangda
On Wed, Dec 13, 2017 at 7:29 AM, Sunil G wrote:
> +1 (binding)
>
> Thanks Andrew
line with Vinod to get help on release-management given
this is my first release. He agreed to help do this release jointly.
Thoughts?
Thanks,
Wangda Tan
[1]
https://lists.apache.org/thread.html/c11506c3250c9481852130616b3cb09a0e222f5c2465c015f9906dab@%3Cyarn-dev.hadoop.apache.org%3E
[2] "p
15, 2017 at 1:20 PM, Wangda Tan wrote:
> Hi all,
>
> Congratulations on the 3.0.0-GA release!
>
> As we discussed in the previous email thread [1], I'd like to restart
> 3.1.0 release plans.
>
> a) Quick summary:
> a.1 Release status
> We started 3.1 release disc
re the deadline.
>
> Regards,
> Uma
>
> On 1/17/18, 11:35 AM, "Wangda Tan" wrote:
>
> Hi All,
>
> Since we're fast approaching previously proposed feature freeze date
> (Jan
> 30, about 13 days from today). If you've any features which live in
of the design choices.
>
> Daniel
>
>
> On 1/17/18 11:33 AM, Wangda Tan wrote:
>
>> Hi All,
>>
>> Since we're fast approaching previously proposed feature freeze date (Jan
>> 30, about 13 days from today). If you've any features which live in a
>> bran
Thanks Arun
+1,
Best,
Wangda
On Fri, Jan 26, 2018 at 7:46 AM, Arun Suresh wrote:
> Hello yarn-dev@
>
> We feel that the YARN-6592 dev branch mostly in shape to be merged into
> trunk. This branch adds support for placing containers in YARN using rich
> placement constraints. For example, this
+1
On Sat, Jan 27, 2018 at 2:05 AM, Chris Douglas wrote:
> +1 Looking forward to this. -C
>
> On Fri, Jan 26, 2018 at 7:28 AM, Arun Suresh wrote:
> > Hello yarn-dev@
> >
> > Based on the positive feedback from the DISCUSS thread [1], I'd like to
> > start a formal vote to merge YARN-6592 [2] to
22, 2018 at 1:49 PM, Gangumalla, Uma
wrote:
> Sure, Wangda.
>
> Regards,
> Uma
>
> On 1/18/18, 10:19 AM, "Wangda Tan" wrote:
>
> Thanks Uma,
>
> Could you update this thread once the merge vote started?
>
> Best,
> Wangda
>
key
> implementation from HDFS-12995, by HDFS-13075.
>
> We are planning to start vote by tomorrow (29th PST time). So, we request
> you to give us time for running vote. We will keep SPS off by default. So,
> interested users only can enable explicitly.
>
>
>
> Regards,
Will keep updated here.
>
> Regards,
> Uma
>
>
> On 1/28/18, 5:31 PM, "Wangda Tan" wrote:
>
> Hi Uma,
>
> Thanks, I saw HDFS-13050 has been resolved 4 hours ago, I don't see any
> other blockers under HDFS-10285. I think you guys should b
I would not be able to put my
> efforts in it. Meanwhile Rakesh/Surendra will update if any changes in the
> plan.
>
>
>
> So, to conclude, you can proceed cutting the branch and we will merge
> after reviews closed, that may go into 3.2.
>
>
>
> Regards,
>
> U
e with that. Let's see what we
> can to do get profiles nailed down so that 3.1 can go forward.
>
> Daniel
>
>
> On 1/18/18 10:25 AM, Wangda Tan wrote:
>
> Thanks Daniel,
>
> We need to make a decision about this: https://issues.apache.
> org/jira/browse/YA
arget Version/s" = 3.1.0 ORDER
BY key ASC, priority DESC
Thanks,
Wangda Tan
Hi all,
As proposed in [1], code freeze of 3.1.0 is already started. I created
branch-3.1 from trunk and will set target version of trunk to 3.2.0.
Please note that only blockers/criticals can be committed to 3.1.0, and all
such commits should be cherry-picked to branch-3.1.
[1]
https://lists.ap
3.1.x
> trunk: 3.2.x
>
> Code freezes in branch-3.1.0 which only allows blocks.
> However, did you mean you created branch-3.1 for 3.1.0? In this case, what
> branch should be used for 3.1.x?
>
> --
> Weiwei
>
> On 11 Feb 2018, 11:11 AM +0800, Wangda Tan , wrote:
>
Hi All,
Thanks for helping with 3.1.0 releases. After many patches resolved or
moved, now we have 9 blockers/criticals [1] (which is down from 33
blockers/criticals in one week before!).
Among these 9 blockers/critical:
- All 3 YARN JIRAs will be resolved in a few days.
- 3 fs/s3 related JIRAs [1
I like the idea of same source / same release and put Ozone's source under
a different directory.
Like Owen mentioned, It gonna be important for all parties to keep a
regular and shorter release cycle for Hadoop, e.g. 3-4 months between minor
releases. Users can try features and give feedbacks to
Hi mapreduce/yarn/common/hdfs-devs,
As of now, we have all blockers done for 3.1.0 release [1]. The release is
running behind schedule due to a few security-related issues. Because of
this and since branch-3.1 is cut 5 weeks before on Feb 8, trunk 3.2 is
already diverging. There're 64 commits in t
look like resetting will destabilize 3.1, +1 for
> doing this.
>
> Thanks
> +Vinod
>
> > On Mar 14, 2018, at 1:54 PM, Wangda Tan wrote:
> >
> > Hi mapreduce/yarn/common/hdfs-devs,
> >
> > As of now, we have all blockers done for 3.1.0 release [1]. The re
ing branch-3.1.
>
> Thanks,
> Akira
>
>
> On 2018/03/18 12:51, Wangda Tan wrote:
>
>> Thanks for sharing your thoughts.
>>
>> We have done build and single node cluster deploy / test for the latest
>> trunk code (commit: 49c747ab187d0650143205ba57ca19607e
. AliyunOSS: move files under a directory in parallel when
rename a directory. Contributed by Jinhu Wu.
MAPREDUCE-7066. TestQueue fails on Java9
YARN-8028. Support authorizeUserAccessToQueue in RMWebServices.
Contributed by Wangda Tan.
YARN-8040. [UI2] New YARN UI webapp does not respect
ce I noticed that the branch will be reset to trunk.
>
> If you have no other concern, I will check pick HADOOP-15262 to the new
> 3.1 branch today.
>
>
> Thanks,
> Sammi
> -----Original Message-
> From: Wangda Tan [mailto:wheele...@gmail.com]
> Sent: Tuesday, M
Devs,
Today I updated fix version of all 3.1.0 JIRAs and moved all unresolved
JIRA with target version = 3.1.0 to 3.2.0.
I've created branch-3.1.0 and working on the RC0 now (still got various of
issues while doing the release, but hopefully, I can get the RC0 done
soon). If you have *ANY fix* w
Hi folks,
Thanks to the many who helped with this release since Dec 2017 [1]. We've
created RC0 for Apache Hadoop 3.1.0. The artifacts are available here:
http://people.apache.org/~wangda/hadoop-3.1.0-RC0/
The RC tag in git is release-3.1.0-RC0.
The maven artifacts are available via repository.
doop-1086/
>
>
> Thanks,
> Bharat
>
>
> On 3/21/18, 11:44 PM, "Wangda Tan" wrote:
>
> Hi folks,
>
> Thanks to the many who helped with this release since Dec 2017 [1].
> We've
> created RC0 for Apache Hadoop 3.1.0. The artifacts
Wangda, thanks for handling this release.
>
> +1 (non-binding)
>
> - verified binary checksum
> - launched single node RM
> - verified refreshQueues functionality
> - verified capacity scheduler conf mutation disabled in this case
> - verified capacity scheduler conf mutation wit
op/common/KEYS. Would you
> please upload it there then we can go ahead to verify the signature of
> following RCs.Thanks!
>
> Thanks,
>
> Junping
>
> Wangda Tan 于2018年3月30日 周五上午12:01写道：
>
>> Thanks all for doing testing and reporting issues.
>>
>>
5578836&usg=AFQjCNGmbuboGWwPig-rtaTXEL7_CLYAfQ>
.
Thanks,
Wangda
On Thu, Mar 29, 2018 at 11:16 AM, Wangda Tan wrote:
> Thanks Junping for reporting this,
>
> I did append my keys to https://svn.apache.org/
> repos/asf/hadoop/common/dist/KEYS, I'm not sure how to propagate it to
>
Hi folks,
Thanks to the many who helped with this release since Dec 2017 [1]. We've
created RC1 for Apache Hadoop 3.1.0. The artifacts are available here:
http://people.apache.org/~wangda/hadoop-3.1.0-RC1
The RC tag in git is release-3.1.0-RC1. Last git commit SHA is
16b70619a24cdcf5d3b0fcf4b58c
>> - Verified old UI and new YARN UI for labels.
>> - Submitted apps to labelled cluster and it works fine.
>> - Also performed few cli commands related to nodelabel.
>>- Test basic HA cases and seems correct.
>>- Tested new YARN UI . All pages are g
checksum file (because MD5 is too broken).
>
> https://www.apache.org/dev/release-distribution#sigs-and-sums
>
>
>
> On Apr 2, 2018, at 7:03 AM, Wangda Tan wrote:
>
> Hi Gera,
>
> It's my bad, I thought only src/bin tarball is enough.
>
> I just uploaded all ot
Thanks Arpit for reporting this and helping investigate the issue offline!
I follow the same tutorial so the previously RC1 maven repo has the same
issue. Just deployed jars by removing -DskipShade and shaded jars have
correct sizes.
Will post an update to RC1 voting thread.
- Wangda
On Mon, A
://people.apache.org/~wangda/hadoop-3.1.0-RC1/). I think we don't need
roll another RC, just update Maven repo should be sufficient.
Best,
Wangda
On Mon, Apr 2, 2018 at 2:39 PM, Wangda Tan wrote:
> Hi Arpit,
>
> Thanks for pointing out this.
>
> I just removed all .md5 files from ar
on r.a.o.
> * Built from source
> * Deployed to 3 node secure cluster with NameNode HA
> * Verified HDFS web UIs
> * Tried out HDFS shell commands
> * Ran sample MapReduce jobs
>
> Thanks!
>
>
> ------
> F
s well as
> the binaries to be consistent and correct. And then (b) Give a couple more
> days for folks who tested on the binaries to reverify - I count one such
> clear vote as of now.
>
> Thanks
> +Vinod
>
>
> On Apr 3, 2018, at 3:30 PM, Wangda Tan wrote:
>
> HI
Thanks everybody for voting!
The vote passes successfully with 11 binding +1 votes, 8 non-binding +1
votes and no -1s.
I will work on the staging and releases.
Best,
Wangda Tan
On Thu, Apr 5, 2018 at 10:46 AM, Vinod Kumar Vavilapalli wrote:
> That is a great observation. And I missed y
source and binary artifacts
>
> - Built from source
>
> - Deployed a single node cluster
>
> - Verified web UIs, include Namenode, RM, etc.
>
> * Tried shell commands of HDFS and YARN
>
> * Ran sample MR jobs, include PI, Sleep, Terasort, etc.
>
>
> Thanks,
es now, and I believe it should be fixed.
>
> Thanks,
> --Konstantin
>
> On Fri, Apr 6, 2018 at 2:01 PM, Wangda Tan wrote:
>
>> Thanks guys for the additional votes! I just sent out announcement email.
>>
>> Best,
>> Wangda
>>
>> On Fri, Apr 6, 20
to cut branch-3.1.1 on May 01 and vote for RC on the same day.
Please feel free to share your insights.
Thanks,
Wangda Tan
[1] project in (YARN, "Hadoop HDFS", "Hadoop Common", "Hadoop Map/Reduce")
AND fixVersion = 3.1.1
265 and I am helping in YARN-8236.
>
> - Sunil
>
>
> On Thu, May 10, 2018 at 2:25 PM Brahma Reddy Battula <
> brahmareddy.batt...@huawei.com> wrote:
>
>> Thanks Wangda Tan for driving the 3.1.1 release.Yes,This can be better
>> addition to 3.1 line release f
Hadoop Map/Reduce")
AND status = Resolved AND fixVersion = 3.1.1
[2] project in (YARN, HADOOP, MAPREDUCE, "Hadoop Development Tools") AND
priority in (Blocker, Critical) AND resolution = Unresolved AND "Target
Version/s" = 3.1.1 ORDER BY priority DESC
On Thu, May 10, 201
+1 (binding)
- Build from source.
- Ran sanity jobs successfully.
Thanks,
Wangda
On Mon, May 14, 2018 at 5:44 AM, Sunil G wrote:
> +1 (binding)
>
> 1. Build package from src
> 2. Ran few MR jobs and verified checked App Priority cases
> 3. Node Label basic functions are ok.
>
> Thanks
> Sunil
> > >
> > > that said, I'm -1 (non-binding). force pushes are extremely
> > > disruptive. there's no way to know who's updated their local git repo
> > > to include these changes in the last few hours. if a merge commit is
> > > so dis
Adding back hdfs/common/mr-dev again to cc list.
Here's the last merge revert commit:
https://github.com/apache/hadoop/commit/39ad98903a5f042573b97a2e5438bc57af7cc7a1
On Thu, Jul 5, 2018 at 2:17 PM Wangda Tan wrote:
> It looks like the latest revert is not correct, many of com
+1
On Thu, Jul 5, 2018 at 2:37 PM Subru Krishnan wrote:
> Folks,
>
> There was a merge commit accidentally pushed to trunk, you can find the
> details in the mail thread [1].
>
> I have raised an INFRA ticket [2] to reset/force push to clean up trunk.
>
> Can we have a quick vote for INFRA sign-
Thanks Sunil for volunteering to be RM of 3.2 release, +1 for that.
To concerns from Steve,
It is a good idea to keep the door open to get important changes / features
in before cutoff. I would prefer to keep the proposed release date to make
sure things can happen earlier instead of last minute
aint
> covered so users could start to explore this feature. Otherwise the
> functionality is pretty limited. It has been Patch Available for a while, I
> just promoted it targeting to 3.1.1. Hope that makes sense.
>
> Thanks!
>
> --
> Weiwei
>
> On 11 May 2018, 9:0
Hi all,
I'm working on RC for 3.1.1 now, if you have any commits to 3.1.x line,
please commit them to branch-3.1.
If it is a blocker for 3.1.1, please let me know so we can decide if we
want to roll another RC or not.
Thanks,
Wangda
On Thu, Jul 19, 2018 at 2:47 PM Wangda Tan wrote:
>
uster and distributed shell job. My +1
to start.
Best,
Wangda Tan
[1] project in (YARN, HADOOP, MAPREDUCE, HDFS) AND fixVersion in (3.1.1)
ORDER BY priority DESC
sanity check on NN UI
>
> Issue found
> * In "Browse the file system" under "Utilities" tab in NN UI, "Head the
> file" and "Tail the file" are not working.
>
> -Nanda
>
> On 8/3/18, 12:14 AM, "Wangda Tan" wrote
he queue balancing feature is enabled. This does not seem to be
>> > specific to this release.
>> > - The preemption-to-balance-queue-after-satisfied.enabled property seems
>> > to always be enabled, but again, that is not specific to this release.
>> >
>>
Tao Jie, Tao Yang, Ted Yu, Thomas Graves, Thomas Marquardt, Todd Lipcon,
Vinod Kumar Vavilapalli, Wangda Tan, Wei Yan, Wei-Chiu Chuang, Weiwei Yang,
Wilfred Spiegelenburg, Xiao Chen, Xiao Liang, Xintong Song, Xuan Gong, Yang
Wang, Yesha Vora, Yiqun Lin, Yiran Wu, Yongjun Zhang, Yuanbo Liu, Zian
+1, thanks for working on this, Marton!
Best,
Wangda
On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal
wrote:
> +1
>
> Thanks for initiating this Marton.
>
>
> On 8/31/18, 1:07 AM, "Elek, Marton" wrote:
>
> Bumping this thread at last time.
>
> I have the following proposal:
>
> 1. I
run against trunk and tracked via [4].
>
> We would love to get your thoughts before opening a voting thread.
>
> Special thanks to a team of folks who worked hard and contributed towards
> this efforts including design discussion / patch / reviews, etc.: Weiwei
> Yang, Bibin Chund
Hi all devs,
Today I found many subtickets doesn't show properly under parent.
For example, YARN-6875 is the parent of YARN-7072. But from YARN-6875's sub
ticket, YARN-7072 isn't shown here.
I found many sub-tickets are gone from parent JIRA, such as YARN-6223
(there were ~20+ sub tickets), YAR
Just checked the JIRA again, now the issue has gone. I think it might be
caused by some intermittent JIRA system issue.
Thanks,
Wangda
On Mon, Oct 1, 2018 at 10:52 AM Wangda Tan wrote:
> Hi all devs,
>
> Today I found many subtickets doesn't show properly under parent.
>
&g
Hi Eric,
replaceLabelsOnNode CLI syntax is different between 2.6 and 2.7.
As mentioned by Naga, In 2.6, you should use "node1<:port>,label
node2,label ..."
And in 2.7, you can use either "," or "=" to separate host and label.
So 2.7 is backward-compatible to 2.6, but it's not guaranteed that 2.7
+1 (binding)
- Deployed a local cluster.
- Configured node labels on queues/nodes.
* Run job with node labels successfully.
Regards,
Wangda
On Tue, Feb 9, 2016 at 10:36 PM, Wangda Tan wrote:
> Hi Eric,
>
> replaceLabelsOnNode CLI syntax is different between 2.6 and 2.7.
>
>
+1, we should close such staled JIRAs to avoid doing unnecessary checks for
every releases.
I'm working on reviewing YARN/MR critical/blocker patches currently, it
gonna very helpful if someone else can help with reviewing Common/HDFS
JIRAs.
Thanks,
Wangda
On Wed, May 11, 2016 at 4:20 PM, Sangj
lks can chime in if you agree
>
> Perhaps Wangda, you can go over the YARN/MR bugs. Sound like a plan?
>
> Thanks,
> Sangjin
>
> On Wed, May 11, 2016 at 4:26 PM, Wangda Tan wrote:
>
>> +1, we should close such staled JIRAs to avoid doing unnecessary checks
>> for
+1 (Non-binding)
Built from src, deployed a single node cluster, and tried to run some MR
jobs.
On Fri, Apr 10, 2015 at 4:44 PM, Vinod Kumar Vavilapalli wrote:
> Hi all,
>
> I've created a release candidate RC0 for Apache Hadoop 2.7.0.
>
> The RC is available at:
> http://people.apache.org/~vi
Hi Hadoop-dev,
Now we are working on branch-2.7 for 2.7.1 release but I found branch-2.7
may not be added to Jenkins white list. For example: YARN-3434 cannot
trigger Jenkins build.
Could anybody help to add it?
Thanks,
Wangda
Thanks Allen for explanation, I thought it's a whitelist in server side,
now I can better understand.
Wangda
On Mon, May 11, 2015 at 10:34 AM, Allen Wittenauer wrote:
>
> On May 11, 2015, at 10:23 AM, Wangda Tan wrote:
>
> > Hi Hadoop-dev,
> >
> > Now we are
+1 (non-binding)
Compiled and deployed a single node cluster, tried to change node labels
and run distributed_shell with node label specified.
On Mon, Jun 29, 2015 at 10:30 AM, Ted Yu wrote:
> +1 (non-binding)
>
> Compiled hbase branch-1 with Java 1.8.0_45
> Ran unit test suite which passed.
>
Can we add following two fixes to 2.6.1?
https://issues.apache.org/jira/browse/YARN-2922 and
https://issues.apache.org/jira/browse/YARN-3487.
They're not fatal issue, but they can cause lots of issue in a large
cluster.
Thanks,
Wangda
On Mon, Aug 3, 2015 at 1:21 PM, Sangjin Lee wrote:
> See
Deployed a local cluster, verified configured cluster with node labels, run
jobs with/without node labels.
+1 (non-binding)
Thanks!
On Thu, Sep 17, 2015 at 2:40 PM, Xuan Gong wrote:
> Update my vote from +1 (non-binding) to +1 binding
>
> Thanks
>
> Xuan Gong
>
> > On Sep 17, 2015, at 2:05 PM,
Hi Hadoop Devs,
As you know, we're pushing 2.8.0 releases recently, there're couple of
issues that block creating release artifacts from source code.
I tried following approaches:
1) Run build through Hadoop Jenkins Job:
https://builds.apache.org/job/HADOOP2_Release_Artifacts_Builder/
2) Run dev-
1 - 100 of 195 matches
Mail list logo
