+1 (non-binding),
Built from rc1 source code
Installed single node cluster.
Ran several YARN applications and get passed.
Thanks,
Wangda
On Sun, Jun 22, 2014 at 9:07 AM, Zhijie Shen zs...@hortonworks.com wrote:
+1 (non-binding)
Successfully redo the steps for rc0 before for rc1 as well.
Hi Karthik,
I found I cannot access the filter: http://s.apache.org/vJg. Could you
please check its permission? I'd like to know if there's any related issues
to me. :)
Thanks,
Wangda
On Thu, Jul 17, 2014 at 5:54 AM, Karthik Kambatla ka...@cloudera.com
wrote:
We are down to 4 blockers and
raised YARN-2247 as the blocker of 2.5.0.
On Thu, Jul 17, 2014 at 9:42 AM, Wangda Tan wheele...@gmail.com wrote:
Hi Karthik,
I found I cannot access the filter: http://s.apache.org/vJg. Could you
please check its permission? I'd like to know if there's any related
issues
to me
Hi Hadoop developers,
I found recently, I cannot access Jenkins generated results, like:
*Test
results: https://builds.apache.org/job/PreCommit-YARN-Build/5039//testReport/
https://builds.apache.org/job/PreCommit-YARN-Build/5039//testReport/Findbugs
warnings:
to the build to get it
working post-git
before that patch the builds weren't working at all ... now its just
getting the URLs wrong.
If you can work out the right URLs we can fix this easily enough
On 19 September 2014 09:24, Wangda Tan wheele...@gmail.com wrote:
Hi Hadoop developers,
I found
Thanks Arun for creating the RC.
Tried to build and deploy it on a local distributed cluster, can
successfully run distributed shell job with node labels.
+1 (non-binding),
Thanks,
Wangda
On Tue, Nov 11, 2014 at 2:06 PM, Robert Kanter rkan...@cloudera.com wrote:
Hi Arun,
We were testing
Thanks Arun!
Have tried compile, deploy and configured a local cluster and can
successfully execute a job with node labels.
+1 (non-binding)
Thanks,
Wangda
On Thu, Nov 13, 2014 at 3:39 PM, Ravi Prakash ravi...@ymail.com wrote:
Thanks for the respin Arun!
I've verified all checksums, and
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 a...@altiscale.com wrote:
On May 11, 2015, at 10:23 AM, Wangda Tan wheele...@gmail.com wrote:
Hi Hadoop-dev,
Now we
+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 vino...@apache.org
wrote:
Hi all,
I've created a release candidate RC0 for Apache Hadoop 2.7.0.
The RC is available at:
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
+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
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 /
___
> > From: Tsuyoshi Ozawa [oz...@apache.org]
> > Sent: Wednesday, October 28, 2015 23:13
> > To: Vinod Vavilapalli
> > Cc: yarn-...@hadoop.apache.org; hdfs-...@hadoop.apache.org;
> > common-dev@hadoop.apache.org; Vinod Kumar Vavilapalli; Wangda Tan;
> > Tsuyoshi O
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
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
Thanks Junping,
+1 (binding). Deploy a cluster locally, run distributed shell and MR job,
both successfully finished.
Regards,
Wangda
On Tue, Dec 15, 2015 at 12:43 PM, Naganarasimha Garla <
naganarasimha...@gmail.com> wrote:
> Hi Junping,
>
> +0 (non binding)
>
> Though everything else is
+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:
>
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 <wheele...@gmail.com> wrote:
> >>
> >> Hi folks,
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
kport should be possible,
> and hopefully without backporting all the conflicting JIRAs. Maybe another
> bash-savvy contributor could attempt it?
>
>
>
> On Tue, Jun 7, 2016 at 2:45 PM, Wangda Tan <wheele...@gmail.com> wrote:
>
>> >
>> > I'm not the one
>
> I'm not the one who cherry-picked them into branch-2, so I don't
> care either way. I've been extremely open about targeting my code for the
> past three years for trunk. With few exceptions, I generally only commit
> code I write or even review to branch-2 if someone practically begs
om>
wrote:
>
> > On Jun 6, 2016, at 10:50 PM, Wangda Tan <wheele...@gmail.com> wrote:
> >
> > 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 sour
+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 <wheele...@gmail.com> wrote:
> Hi Eric,
>
> replaceLabelsOnNode CLI syntax is different betw
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
Hi Allen,
YARN-3368 is using Ember.JS and Ember.JS depends on npm (Node.JS Package
Manager) to manage packages.
One thing to clarify is: npm dependency is only required by build stage (JS
build is stitching source files and renaming variables). After JS build
completes, there's no dependency of
eactive UI
> > design. I think the decision of using ember.js exclusively might worth
> > revisiting. To me it makes more sense to move both HDFS / YARN towards
> > React and go from there.
> >
> > ~Haohui
> >
> > On Mon, Feb 29, 2016 at 5:14 PM, Wangda Tan <wheele...@gm
of tomcat packages.
On Tue, May 17, 2016 at 3:11 PM, Allen Wittenauer <allenwittena...@yahoo.com
> wrote:
>
> > On May 17, 2016, at 2:08 PM, Wangda Tan <wheele...@gmail.com> wrote:
> >
> > Then I investigated a little more, there're two issues from what I can
ere. Then folks 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 <wheele...@gmail.com> wrote:
>
>> +1, we should close such staled JIRAs to avoi
+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,
Hi YARN-dev/Common-dev,
I noticed lots of "javac: invalid target release: 1.8" failures happen on
YARN precommit runs since yesterday, not sure if other projects like HDFS
face the same issue.
Filed HADOOP-13167 to track the issue.
Thanks,
Wangda
Thanks Allen,
I just triggered other tests to run, will report here if any other issues
found.
- Wangda
On Tue, May 17, 2016 at 11:10 AM, Allen Wittenauer <a...@apache.org> wrote:
>
> > On May 17, 2016, at 10:54 AM, Wangda Tan <wheele...@gmail.com> wrote:
> >
Hi common-devs,
When I tried to build Hadoop trunk today, Maven build failed because kms
failed to download:
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.44/bin/apache-tomcat-6.0.44.tar.gz
.
When I open the link from browser, it shows bandwidth limit exceeded:
===
Bandwidth limit
actively working on these items, any helps will be
appreciated.
Thanks,
Wangda
On Tue, Jul 26, 2016 at 11:16 AM, Vinod Kumar Vavilapalli <
vino...@apache.org> wrote:
> +1
>
> Thanks
> +Vinod
>
> On Jul 26, 2016, at 7:39 AM, Wangda Tan <wheele...@gmail.com> wrote:
Hi Andrew,
Please wait updating fix version for branch-2 committed tickets before we
get a consensus on this. Updating fix versions for them could bring lots of
troubles for on going two releases (2.7.3 / 2.8.0).
Thanks,
Wangda
On Mon, Jul 25, 2016 at 11:02 AM, Andrew Wang
I agree with what Vinod mentioned: we need to revisit all incompatible
changes and revert unnecessary ones. Even if we don't have any
compatibility guarantees between 2.x and 3.x. But make user to be less
frustrated while trying 3.x is always a better option to me.
To achieve this we need to run
I just filed ticket https://issues.apache.org/jira/browse/HADOOP-13423 to
track running JDIFF on trunk and analyze results for Hadoop-common. I will
work on that and keep the JIRA and this thread updated. We need to do the
same work for YARN/MR/HDFS.
On Mon, Jul 25, 2016 at 5:47 PM, Wangda Tan
Thanks Andrew for sharing your thoughts,
It looks better if we can put multiple versions on the fix version, with
that we can at least do some queries on JIRA to check the issues like "in
branch-2.6.5 but not in branch-2.7.4".
I still have a couple of questions:
*1) How CHANGES.txt (or release
Thanks Vinod.
+1 (Binding)
- Built from source and deploy a pseudo cluster locally
- Run DS on YARN
- With/Without node labels enabled.
- Wangda
On Mon, Jul 25, 2016 at 1:55 PM, Mingliang Liu wrote:
> Thanks Vinod.
>
> +1 (non-binding)
>
> * Downloaded and built from
lt;bus...@cloudera.com> wrote:
>
> Just so I don't waste time chasing my tail, should I interpret this
> email and the associated JIRA as the PMC preferring I not spend
> volunteer time providing a compatibility breakdown as previously
> discussed?
>
>> On Mon, Jul 25, 20
+1 Binding.
- Built and deploy a single node cluster from source code.
- Ran some example jobs.
Thanks,
Wangda
On Tue, Aug 23, 2016 at 12:35 PM, Naganarasimha Garla <
naganarasimha...@apache.org> wrote:
> +1 (non-binding)
>
> - Downloaded source and tar verified the checksum
> - Installed
Thanks Sangjin for cutting this release!
+1 (Binding)
- Downloaded binary tar ball and setup a single node cluster.
- Submit a few applications and which can successfully run.
Thanks,
Wangda
On Fri, Oct 7, 2016 at 10:33 AM, Zhihai Xu wrote:
> Thanks Sangjin for
list the ASF snapsphot repo first
>
> On 1 Oct 2016, at 17:37, Wangda Tan <wheele...@gmail.com> wrote:
> >
> > Hi YARN-dev,
> >
> > (cc common-dev),
> >
> > YARN timeline service currently sometimes downloads maven-metadata.xml
>
Filed: https://issues.apache.org/jira/browse/HBASE-16749
On Mon, Oct 3, 2016 at 10:18 AM, Wangda Tan <wheele...@gmail.com> wrote:
> Thanks Sangjin/Ted/Steve for your comments/suggestions, I will file a
> HBase JIRA later.
>
> Regards,
> Wangda
>
> On Mon, Oct 3, 2016
Hi YARN-dev,
(cc common-dev),
YARN timeline service currently sometimes downloads maven-metadata.xml from
a personal apache site, log looks like:
[INFO]
[INFO] Building Apache Hadoop YARN Timeline Service
This looks like bug caused by npm, looking into it now.
Thanks,
Wangda
On Thu, Nov 10, 2016 at 4:00 PM, Zhe Zhang wrote:
> https://builds.apache.org/job/PreCommit-HDFS-Build/17517/
> artifact/patchprocess/patch-compile-root.txt
>
> Looks related to yarn-ui? The HDFS-10872
e's question, I don't think maven downloads anything from
> that location (it's a very old content). It just does a wasted effort by
> hitting this repo.
>
> On Mon, Oct 3, 2016 at 10:25 AM, Wangda Tan <wheele...@gmail.com> wrote:
>
>> Filed: https://issues.apache.org/j
into what's happening?
>
> On Wed, Dec 14, 2016 at 11:01 AM, Wangda Tan <wheele...@gmail.com> wrote:
>
>> Thanks folks for reply, I tried to change some parameters of maven (like
>> useCache=true), but it still doesn'
d help with this
>>>> > build time taken issue. I will start looking into this upgrade right
>>>> > away.
>>>> >
>>>> > Thanks
>>>> > Vrushali
>>>> >
>>>> > > On Dec 13, 2016, at 3:02 PM, Li Lu <llu.u...@gmai
Thanks Junping for doing this.
*+1 (Binding),*
Built from source code, deployed a single node cluster. Enabled node labels
and tried to run sample jobs. Haven't seen any issue so far.
Thanks,
Wangda
On Mon, Mar 20, 2017 at 10:02 AM, Junping Du wrote:
> Thank you for
t.
>
> Best,
> Andrew
>
> On Thu, Aug 17, 2017 at 8:27 PM, Wangda Tan <wheele...@gmail.com> wrote:
>
>> +hdfs/common/mr
>>
>> On Thu, Aug 17, 2017 at 1:28 PM, Wangda Tan <wheele...@gmail.com> wrote:
>>
>> > Hi all,
>> >
>&
+hdfs/common/mr
On Thu, Aug 17, 2017 at 1:28 PM, Wangda Tan <wheele...@gmail.com> wrote:
> Hi all,
>
> I want to hear your thoughts of merging YARN resource profile branch into
> trunk in the next few weeks. The goal is to get it in for Hadoop 3.0 beta1.
>
> *Regardi
+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
zookeeper implementation are supported.
> >
> > 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,
-beta1
> (3.0.0-beta1-SNAPSHOT). This way we can merge GA features to branch-3.0 but
> not branch-3.0.0-beta1.
>
> Best,
> Andrew
>
> On Tue, Aug 29, 2017 at 11:18 AM, Wangda Tan <wheele...@gmail.com> wrote:
>
>> Vrushali,
>>
>> Sure we can wait TSv2 merg
Vrushali,
Sure we can wait TSv2 merged before merge resource profile branch.
Andrew,
My understanding is you're going to cut branch-3.0 for 3.0-beta1, and the
same branch (branch-3.0) will be used for 3.0-GA as well. So my question
is, there're several features (TSv2, resource profile,
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+page:1+mid
N feature I'd
> 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 <wheele...@gmail.com> wrote:
>
>> Hi all,
>>
>> As we discussed on [1], there were proposals from Steve
> types to allow a user to request a group of resources as a profile, much
> > like EC2 instance types, e.g. "fast-compute" might mean 32GB RAM, 8
> > vcores, and 2 GPUs.
> >
> > Daniel
> >
> > On 8/23/17 11:49 AM, Wangda Tan wrote:
> > >
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
Andrew,
Thanks for your help to pushing this release.
Echoing what Vinod said, all contributors in these branches are putting
months to years of time working on these features, we don't have to decide
excluded features now since we have 25 days till 3.0-beta1 planned release
time.
The best
Hi Andrew,
Thanks for updating the proposal, +1.
- Wangda
On Fri, Aug 25, 2017 at 12:16 PM, Allen Wittenauer wrote:
>
> > On Aug 25, 2017, at 10:36 AM, Andrew Wang
> wrote:
>
> > Until we need to make incompatible changes, there's no
and contributed towards
this effort including design discussion/development/reviews, etc.: Varun
Vasudev, Sunil Govind, Daniel Templeton, Vinod Vavilapalli, Yufei Gu,
Karthik Kambatla, Jason Lowe, Arun Suresh.
Regards,
Wangda Tan
[1]
http://mail-archives.apache.org/mod_mbox/hadoop-yarn-dev/20170
Resource profile is similar to TSv2, the feature is:
- Alpha feature, we will not freeze new added APIs. And all added APIs are
explicitly marked to @Unstable.
- Allow rolling upgrade from branch-2.
- Touched existing code, but we have, and will continue tests to make sure
changes are safe.
+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
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
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
te:
>
>> Yes, qbt runs nightly 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,
>>
to-end and we 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
+1, thanks Sunil!
Wangda Tan
On Wed, Nov 29, 2017 at 5:56 PM, Sunil G <sun...@apache.org> 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 Wedn
th 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] "project in
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
+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
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
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
+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
Sunil / Rohith,
Could you check if your configs are same as Jonathan posted configs?
https://issues.apache.org/jira/browse/YARN-7453?focusedCommentId=16242693=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16242693
And could you try if using Jonathan's configs can still
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"
+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.
gt; Yes, Billie is reviewing YARN-8265 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
>&
p 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, 2018
0 PM, Wangda Tan <wheele...@gmail.com> 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 di
rethink some 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
>>
h the tasks sooner
> before the deadline.
>
> Regards,
> Uma
>
> On 1/17/18, 11:35 AM, "Wangda Tan" <wheele...@gmail.com> wrote:
>
> Hi All,
>
> Since we're fast approaching previously proposed feature freeze date
> (Jan
> 30, about 13
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
ize the
> comments and decide.
> Will keep updated here.
>
> Regards,
> Uma
>
>
> On 1/28/18, 5:31 PM, "Wangda Tan" <wheele...@gmail.com> wrote:
>
> Hi Uma,
>
> Thanks, I saw HDFS-13050 has been resolved 4 hours ago, I don't see any
> ot
+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
> >
, Gangumalla, Uma <uma.ganguma...@intel.com>
wrote:
> Sure, Wangda.
>
> Regards,
> Uma
>
> On 1/18/18, 10:19 AM, "Wangda Tan" <wheele...@gmail.com> wrote:
>
> Thanks Uma,
>
> Could you update this thread once the merge vote started?
>
>
ouple of days I will be in travel, 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.
&g
and we finished the 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.
>
&
I would tend to agree 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.apac
ion/s" = 3.1.0 ORDER
BY key ASC, priority DESC
Thanks,
Wangda Tan
Hi guys,
I was trying to run JACC build for 3.1.0 release. When I run JACC to
compare branch-2.9 or branch-3.0 with branch-3.1, I found the Jenkins build
got killed after 1 hour. For example:
https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-trunk-JACC/1828/consoleFull
I think there're
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]
.1.0: 3.1.0
> branch-3.1: 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 +
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
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
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:
> Hi
eue 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.
>> >
>> >
c 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:
>
1 - 100 of 233 matches
Mail list logo