Thanks Viany for starting discussion.
+1
hadoop-thirdparty's release is required for 3.3.0 release because the
package includes shaded protobuf which 3.3.0 branch will depend on.
The plan sounds reasonable to me.
- Tsuyoshi
On Sat, Feb 22, 2020 at 6:31 AM Ayush Saxena wrote:
>
> Thanx Vinay fo
+1
Thanks
- Tsuyoshi
On Thu, May 14, 2020 at 19:42 Rakesh Radhakrishnan
wrote:
> +1
>
> Thanks,
> Rakesh
>
> On Wed, May 13, 2020 at 1:23 PM Elek, Marton wrote:
>
> >
> >
> > I would like to start a discussion to make a separate Apache project for
> > Ozone
> >
> >
> >
> > ### HISTORY [1]
> >
Forwarding this discussion to Klaus.
- Tsuyoshi
On Tue, Jul 19, 2016 at 4:46 PM, Tsuyoshi Ozawa wrote:
> Hi developers,
>
> Klaus mentioned the availability of an official docker image of Apache
> Hadoop. Is it time that we start to distribute an official docker
> image
Hi developers,
I'd like to discuss how to make an advance towards dependency
management in Apache Hadoop trunk code since there has been lots work
about updating dependencies in parallel. Summarizing recent works and
activities as follows:
0) Currently, we have merged minimum update dependencies
sues.apache.org/jira/browse/HADOOP-13397
>
>
> Da (Klaus) Ma (马达), PMP® | Software Architect
> IBM Spectrum, STG, IBM GCG
> +86-10-8245 4084 | klaus1982...@gmail.com | http://k82.me
>
> On Jul 21, 2016, at 13:33, Tsuyoshi Ozawa wrote:
>
> Forwarding this discussion to Klaus.
ncies.
> This can be achieved by flexible Dockerfile which uses configuration
> passed from environment variables.
>
> Thanks
>
> Kai Sasaki
>
>
> On Jul 19, 2016, at 4:46 PM, Tsuyoshi Ozawa > wrote:
>
> Hi developers,
>
> Klaus mentioned the availability of an offic
Hi Vinod,
Thanks all guys for starting discussion!
My suggestion is adding the date when branch cut is done: like
3.0.0-alpha1-20160724, 2.8.0-20160730 or something.
Pros:-) It's totally ordered. If we have a policy such as backporting
to maintainance branches after the date, users can find that
> Andrew: I bet many would assume it's the release date, like how Ubuntu
releases are numbered.
Good point. Maybe I confuse you because of lack of explanation.
I assume that "branch-cut off timing" mean the timing of freezing branch
like when starting the release vote. It's because that the relea
this problem is also pretty rare in practice, since users normally
> upgrade to the highest maintenance release within a major/minor. Thus
> they'll only hit this if their upgrade cycle is faster than it takes for a
> change released in e.g. 2.6.x to then also be released in a 2.7.x
Thanks for making this forward hardly, Andrew!
In fact, I hit an error similar to Eric's one regardless of
configuring yarn.app.mapreduce.am.env and mapreduce.admin.user.env...
does anyone hit same error?
2016-09-02 16:49:35,223 INFO mapreduce.Job: The url to track the job:
http://ip-172-31-7-12
I'm sorry, very big typo I did... s/hardly/very hard/
Best
- Tsuyoshi
On Sat, Sep 3, 2016 at 1:53 AM, Tsuyoshi Ozawa wrote:
> Thanks for making this forward hardly, Andrew!
>
> In fact, I hit an error similar to Eric's one regardless of
> configuring yarn.ap
ne regardless of
configuring yarn.app.mapreduce.am.env and mapreduce.admin.user.env...
does anyone hit same error?
This was because of completely my wrong configuration. Please ignore this.
Best,
- Tsuyoshi
On Sat, Sep 3, 2016 at 1:53 AM, Tsuyoshi Ozawa wrote:
> Thanks for making this forwar
Hi developers,
Chiwan Park reported Hadoop incompatibility by the change of HADOOP-11252.
Now, HADOOP-13579 is committed to branch-2.6 and branch-2.7.
Should we release 2.6.5 and 2.7.4 soon?
Thanks,
- Tsuyoshi
-
To unsubscribe,
> Chiwan Park reported Hadoop incompatibility by the change of HADOOP-11252.
> Now, HADOOP-13579 is committed to branch-2.6 and branch-2.7.
complement: HADOOP-13579 fixes the problem of incompatibility by HADOOP-11252.
Thanks,
- Tsuyoshi
On Fri, Sep 9, 2016 at 2:42 PM, Tsuyoshi Ozawa
+1,
IMO, it's okay remove. I've not heard that it's used in production.
Thanks,
- Tsuyoshi
On Thu, Oct 13, 2016 at 9:52 AM, Ravi Prakash wrote:
> +1. Even though I committed it, I admit we haven't done a good job of
> maintaining the alpha code.
>
> On Wed, Oct 12, 2016 at 9:57 AM, Karthik Kamb
Dear Hadoop developers,
After shaded client, introduced by HADOOP-11804, is merged,
we can more easily update some dependency with minimizing the impact
of backward compatibility on trunk. (Thanks Sean and Sanjin for taking
the issue!)
Then, is it time to update protobuf's version to the latest o
Forwarding to common-dev, hdfs-dev, mapreduce-dev too.
Thanks
- Tsuyoshi
2017年3月27日(月) 21:16 Tsuyoshi Ozawa :
> Dear Hadoop developers,
>
> After shaded client, introduced by HADOOP-11804, is merged,
> we can more easily update some dependency with minimizing the impact
&
> Stack mentioned a compatibility mode that uses the proto2 semantics.
We can define protobuf's version by using syntax = "proto2" or syntax
= "proto3" in proto files with proto3 compiler. I think this is what
Stack mentioned as compatibility mode.
https://github.com/golang/protobuf/blob/master/p
'version at
compilation time by using syntax = "proto2""...
- Tsuyoshi
On Wed, Mar 29, 2017 at 9:13 AM, Tsuyoshi Ozawa wrote:
>> Stack mentioned a compatibility mode that uses the proto2 semantics.
>
> We can define protobuf's version by using syntax = "proto2&quo
Hi Steve,
Thanks for your help.
> 2. it's "significant"
This change includes upgrading not only Jersey, but also its
dependencies like grizzly, asm, and so on.
> I'll try to rebuild a YARN app (slider) with the patch to see how it fares
It helps us a lot. I'd like to suggest that the incompat
targetting this only at trunk /
> 3.0 based on the "target version" and the incompatibility discussion?
>
> best,
> Colin
>
> On Mon, Oct 26, 2015 at 7:07 AM, Tsuyoshi Ozawa wrote:
>
>> Hi Steve,
>>
>> Thanks for your help.
>>
>> >
same risk of regressions or
> > incompatibilities as code changes.
> >
> > --Chris Nauroth
> >
> >
> >
> >
> > On 7/16/15, 12:38 AM, "Tsuyoshi Ozawa" >
> wrote:
> >
> >> Hi,
> >>
> >> thank you for startin
nk we need HDFS-8950 and HDFS-7725 in 2.7.2.It should be easy to
> backport/cherry-pick HDFS-7725. For HDFS-8950, it will be nice if Ming can
> chime in.
> Kihwal
>
> From: Tsuyoshi Ozawa
> To: "common-...@hadoop.apache.org"
> Cc: Chris Nauroth ; "yarn-d
the support in Mapreduce for labels in
>> MAPREDUCE-6304,
>>
>> Regards,
>> + Naga
>>
>> From: Tsuyoshi Ozawa [oz...@apache.org]
>> Sent: Wednesday, October 28, 2015 14:28
>> To: yarn-dev@hadoop.apache.org
>> Cc: hdfs-...@hadoop.apache.org; common-...@
Thank you for starting discussion, Steve. It sounds good to me. I'll
check the test failures.
- Tsuyoshi
On Sun, Nov 22, 2015 at 9:21 PM, Steve Loughran wrote:
>
> Jenkins is pretty much dead in the water these days; a test run that works is
> a rare miracle rather than the default state. Whic
Hi Junping,
Thank you for starting the voting.
I cannot access the tar.gz file because of permission error. Could you
check the permission to access the files?
> Forbidden
> You don't have permission to access
> /~junping_du/hadoop-2.6.3-RC0/hadoop-2.6.3-RC0-src.tar.gz on this server.
Thanks,
-
+1 (binding)
- verified checksums
- built Spark and Tez with -Dhadoop.version=2.6.3. About Tez, ran
tests and all of them passed.
Thanks,
- Tsuyoshi
On Thu, Dec 17, 2015 at 1:30 AM, Sangjin Lee wrote:
> +1 (non-binding)
>
> - downloaded source and binary and verified the signatures (although I
Thanks Wangda for reporting issue. I'm also +1 for recreating a new
branch-2.8 based on current branch-2.8 too. After that, we can revert
2.9.0-only patches on the branch. I will help you if necessary, so
please let me know.
Thanks,
- Tsuyoshi
On Thu, Dec 17, 2015 at 10:51 AM, Jing Zhao wrote:
>
+1
- downloaded src and bin tar balls and verified signatures.
- built Tez and Spark with 2.7.2 artifacts and JDK7.
- ran tests of Tez with 2.7.2 artifacts, it passed.
FYI: YARN-4348, reported by Jian, is one of critical issues of 2.7.2
release.It's better to release 2.7.3 as soon as possible aft
Hi Vinod,
thank you for the clarification.
> - Pull these 16 tickets into 2.7.2 and roll a new RC
> > What do people think? Do folks expect “any fix in 2.6.3 to be there in all
> > releases that get out after 2.6.3 release date (December 16th)”?
I personally prefer to pull these tickets into 2
+1 (binding)
- Verified checksum.
- Built from source code.
- Ran some tests and mr examples.
Thanks,
- Tsuyoshi
On Fri, Jan 15, 2016 at 1:57 PM, Vinod Kumar Vavilapalli
wrote:
> Hi all,
>
> I've created an updated release candidate RC2 for Apache Hadoop 2.7.2.
>
> As discussed before, this is
+1(binding)
- Verified signatures.
- Ran tests for Apache Tez with the artifacts. All tests passed.
- Ran local cluster and ran some examples on it.
- Tsuyoshi
On Wed, Feb 10, 2016 at 2:18 AM, Sunil Govind wrote:
> +1 (non-binding) with one note,
>
> - Installed tar ball from source and brought
Thanks for your work, Sid!
I'll throw some patches I have and help to fix TODOs against the new branch.
- Tsuyoshi
On Thursday, August 23, 2012, Siddharth Seth wrote:
> I've created a branch to continue work on MAPREDUE-3902 since the changes
> are reasonably big and intrusive. A branch should a
, Tsuyoshi OZAWA
wrote:
> Thanks for your work, Sid!
> I'll throw some patches I have and help to fix TODOs against the new branch.
>
> - Tsuyoshi
>
> On Thursday, August 23, 2012, Siddharth Seth wrote:
>>
>> I've created a branch to continue work on MAPREDUE-
Sandy, it also depends on the timing. For instance, in MapReduce's case,
MRAppMaster requests the containers for each task separately. Could you
explain the timing when you issue each request?
On Thu, Jan 3, 2013 at 5:52 AM, Robert Evans wrote:
> Mappers and reducers are requested at different
Hi,
Recently, I've tackled with dependency problems about Guava, Jetty,
and Jersey. Essentially, it's similar to "DLL hell".
I've seen that Google Guice uses jarjar-maven-plugin to avoid
classpath conflicts between user-side dependency and library-side
dependency.
http://sonatype.github.io/jarja
gt; shading the hadoop client. Have you reviewed his proposal?
>
> Best,
> Andrew
>
> On Tue, Jun 9, 2015 at 12:17 PM, Tsuyoshi Ozawa wrote:
>
>> Hi,
>>
>> Recently, I've tackled with dependency problems about Guava, Jetty,
>> and Jersey. Essentially, it&#
Hi Vinod,
Thank you for working to release 2.7!
YARN-3798 looks a critical issue for branch-2.7. I'll mark it as a
blocker of 2.7.1 if possible.
Thanks,
- Tsuyoshi
On Tue, Jun 16, 2015 at 6:58 AM, Vinod Kumar Vavilapalli
wrote:
> We are down to one blocker and a few critical tickets. I’ll try t
Thank you for starting voting, Vinod.
I tried to untar the tarball, but the command exited with an error. Is
binary tarball broken?
$ tar xzvf hadoop-2.7.1-RC0.tar.gz
...
hadoop-2.7.1/share/hadoop/httpfs/tomcat/webapps/webhdfs/WEB-INF/lib/hadoop-common-2.7.1.jar
gzip: stdin: unexpected end of fil
tar (GNU tar) 1.23
>
> uname -a
> Linux a.com 2.6.32-504.el6.x86_64 #1 SMP Wed Oct 15 04:27:16 UTC 2014
> x86_64 x86_64 x86_64 GNU/Linux
>
> I was able to expand the tarball.
>
> Can you use another machine ?
>
> Cheers
>
>
> On Fri, Jul 3, 2015 at 9:53 AM,
+1, thanks Allen and Andrew for taking lots effort!
> Is there any possibility that, we can restrict someone from editing the
> issue in jira once its marked as "closed" after release?
Vinay's comment looks considerable for us to me. What do you think?
- Tsuyoshi
On Wed, Jul 8, 2015 at 3:57 PM,
Hi,
thank you for starting the discussion about 2.7.2 release.
> The focus obviously is to have blocker issues [2], bug-fixes and *no*
features / improvements.
I've committed YARN-3170, which is an improvement of documentation. I
thought documentation pages which can be fit into branch-2.7 can b
+1 (non-binding)
1. Built from source.
2. Verified signature of bin tar ball and source tar ball.
3. Running some examples.
4. Running Spark on YARN with spark-shell. It works well.
I think 4 verifies compatibility is preserved.
Thanks everyone for working to release 2.6.1.
Thanks,
- Tsuyoshi
O
Hi commiters and users of Hadoop stack,
I’ll share the current status of JDK-8 support here. We can take a
two-step approach to support JDK-8 - runtime-level support and
source-level support.
About runtime-level support, I’ve tested Hadoop stack with JDK-8 e.g.
MapReduce, Spark, Tez, Flink on YA
Tue, Oct 6, 2015 at 9:35 AM, Tsuyoshi Ozawa wrote:
> Hi commiters and users of Hadoop stack,
>
> I’ll share the current status of JDK-8 support here. We can take a
> two-step approach to support JDK-8 - runtime-level support and
> source-level support.
>
> About runtime-level su
the
> sentiment that we should preserve the java 7 support on branch-2 (not not
> move to java 8 source level) but can consider it for trunk. My 2 cents.
>
> Thanks,
> Sangjin
>
> On Fri, Oct 9, 2015 at 10:43 AM, Steve Loughran
> wrote:
>
>>
>> > On 7 Oc
> We should target source-level support of JDK 8 too, around which you outlined
> a bunch of issues around dependencies. I also found a bunch of issues around
> generating documentation, site etc. I propose that we track them under the
> umbrella JIRA and make progress there first.
OK. I will s
Thanks for your notification, Sangjin. I'll backport YARN-3798 soon.
- Tsuyoshi
On Wed, Oct 21, 2015 at 10:09 AM, Sangjin Lee wrote:
> If you have backported bugfixes to 2.7.2, please take a moment to consider
> if it is relevant (and important) for 2.6.x too, and if so backport it to
> branch-2
Hi YARN developers,
CC: Sangjin,
I noticed CHANGES.txt is not synced up between branch-2.6 and the
other branches when pushing YARN-3798, so I updated it. Please ping me
if something is wrong by this change.
Thanks,
- Tsuyoshi
Done.
- Tsuyoshi
On Wed, Oct 21, 2015 at 8:53 PM, Tsuyoshi Ozawa wrote:
> Thanks for your notification, Sangjin. I'll backport YARN-3798 soon.
>
> - Tsuyoshi
>
> On Wed, Oct 21, 2015 at 10:09 AM, Sangjin Lee wrote:
>> If you have backported bugfixes to 2.7.2, please
Hi,
I created slack channel for Hadoop community unofficially and experimentally:
https://hadoopdev.slack.com/
I know that there is IRC channel and it's good to log. However, Slack
is very also good tool to join easily and have a communication
interactively. It will be also useful to join followi
Hi developers,
We’ve worked on upgrading jersey(HADOOP-9613) for a years. It's
essential change to support complication with JDK8. It’s almost there.
One concern to merge this to trunk is incompatibility. After the
release of Jersey 1.13, the root element whose content is empty
collection is chan
> Before cutting 3.0.0-alpha RC, I'd like to drop JDK7 support in trunk.
Sounds good. To do so, we need to check the blockers of 3.0.0-alpha
RC, especially upgrading all dependencies which use refractions at
first.
Thanks,
- Tsuyoshi
On Tue, May 10, 2016 at 8:32 AM, Akira AJISAKA
wrote:
> Hi de
Hi YARN developers,
Could you check this thread? I think YARN web UI is affected by this change.
Thanks,
- Tsuyoshi
-- Forwarded message --
From: Tsuyoshi Ozawa
Date: Mon, May 9, 2016 at 12:12 PM
Subject: [DISCUSS] Merge Jersey upgrade(HADOOP-9613) to trunk
To: "c
On Sat, May 14, 2016 at 9:24 AM, Sangjin Lee wrote:
> We're also checking from the timeline service v.2 perspective (YARN-2928).
>
> On Fri, May 13, 2016 at 3:33 PM, Tsuyoshi Ozawa wrote:
>>
>> Hi YARN developers,
>>
>> Could you check this thread? I thi
Hi Asanjar,
Thanks for your contribution! I'm ashamed to say, but I don't know how
to change the build machine.
Adding "to" Allen, who is a PMC of Yetus project. Hey Allen, do you
know how to add Power based Jenkins slave(s) to Apache Hadoop CI?
Thanks,
- Tsuyoshi
On Wed, May 18, 2016 at 11:18
ime, YARN-3368 (new UI branch) may also need some tests?
>
> Li Lu
>
> On May 18, 2016, at 09:08, Sangjin Lee wrote:
>
> Li Lu was looking into this. Li, were you able to take a look?
>
> Thanks,
> Sangjin
>
> On Wed, May 18, 2016 at 7:44 AM, Tsuyoshi Ozawa wrote:
&
Thanks Sangjin for starting the discussion.
>> *First*, if the merge vote is approved, to which branch should this be
merged and what would be the release version?
As you mentioned, I think it's reasonable for us to target trunk and
3.0.0-alpha.
>> Slightly unrelated to the merge, do we plan to
Lu
>> >> > On Jun 21, 2016, at 15:51, Sangjin Lee wrote:
>> >> >
>> >> > Thanks Karthik and Tsuyoshi. Regarding alternate implementations, I'd
>> >> like
>> >> > to get a better sense of what you're thinking of. Are you inte
Hi,
Have anyone tried to submit jobs on trunk cluster?
I failed to launch jobs by class not found error with following error
messages. Should I change environment variables to setup from
branch-2's one? I'm using the same configuration as Hadoop 2 can run.
$ hadoop jar
./share/hadoop/mapreduce/h
ink it is modified for security reasons. I too did not find any JIRA id
> corresponding to this commit.
>
> Related discussion happened in the following JIRA.
> https://issues.apache.org/jira/browse/MAPREDUCE-6704
>
>
> Thanks & Regards
> Rohith Sharma K S
>
>
Hi developers,
I will plan to upgrade Google Guice dependency on trunk. The change
also includes asm and cglib upgrade.
I checked following points:
* Both HDFS and YARN UIs work well.
* All webIU-related tests pass as described on HADOOP-12064.
* Ran mapreduce job, and it works well.
https://iss
No objections here?
- Tsuyoshi
On Mon, Jun 27, 2016 at 6:01 AM, Tsuyoshi Ozawa wrote:
> Hi developers,
>
> I will plan to upgrade Google Guice dependency on trunk. The change
> also includes asm and cglib upgrade.
> I checked following points:
>
> * Both HDFS and YARN U
te:
>> > My strong expectation is that we’ll have a version of classpath
>> > isolation in our first release of 3.x. I’m planning to spending some cycles
>> > right away on this.
>> >
>> > Assuming classpath isolation gets in, it is reasonable to bump
I forgot to mention about importance point: it's a blocker issue to
compile Hadoop with JDK8. Hence, we need to merge it on both client
side and server slide anyway.
Thanks,
- Tsuyoshi
On Wed, Jun 29, 2016 at 12:24 PM, Tsuyoshi Ozawa wrote:
> Thanks Vinod, Sangjin, Sean for your
n 29, 2016 at 12:27 PM, Tsuyoshi Ozawa wrote:
>>
>> I forgot to mention about importance point: it's a blocker issue to
>> compile Hadoop with JDK8. Hence, we need to merge it on both client
>> side and server slide anyway.
>>
>> Thanks,
>> - Tsuy
+1(binding)
On Sat, Jul 2, 2016 at 9:41 AM, Joep Rottinghuis wrote:
> Perhaps superfluous as a contributor to this branch, but for the record:
> +1 (non-binding)
>
> Cheers,
>
> Joep
>
>> On Jul 1, 2016, at 9:00 AM, Sangjin Lee wrote:
>>
>> Hi folks,
>>
>> Per earlier discussion [1], I'd like to
u, Jun 30, 2016 at 12:03 PM, Tsuyoshi Ozawa wrote:
>>
>> Thanks, Andrew.
>>
>> Based on discussion here, I would like to merge it into *trunk* if
>> there are no objection tomorrow.
>>
>> Thanks,
>> - Tsuyoshi
>>
>> On Wed, Jun 29, 201
+1,
>From user's point of view, the high-level resource management API
without any additional dependency is much comfortable than using
low-level APIs. I believe the way should increase YARN applications
including long-running services. From developer's point of view, the
integration make YARN mor
Hi developers,
Klaus mentioned the availability of an official docker image of Apache
Hadoop. Is it time that we start to distribute an official docker
image at release time?
http://mail-archives.apache.org/mod_mbox/hadoop-user/201607.mbox/%3CSG2PR04MB162977CFE150444FA022510FB6370%40SG2PR04MB1629
gt; we can integrate it.
>> http://wiki.apache.org/hadoop/HowToUseJCarder
>>
>> Thanks & Regards
>> Rohith Sharma K S
>>
>> -Original Message-
>> From: Tsuyoshi Ozawa [mailto:oz...@apache.org]
>> Sent: 24 December 2014 16:38
>&
has support for evaluating reentrant locks.
Can we use the modified version of jcarder for the issue? It's very
useful for us.
Thanks,
- Tsuyoshi
On Tue, Jan 20, 2015 at 7:07 AM, Spandan Dutta wrote:
> @Tsuyoshi Ozawa. We have a jcarder jenkins job now setup internally at
> cloudera
Hi Robert,
No, there is no limitation about this. We can make the configuration
configurable. I think we should make the default value 4GB for
backward compatibility. Could you create a JIRA for tracking the
issue?
Thanks,
- Tsuyoshi
On Thu, Jan 22, 2015 at 1:27 AM, Robert Metzger wrote:
> Hi,
ce-monitoring";
>
> Or is there another approach you would prefer?
>
> I'll add a patch to the JIRA once I've found time to fix it.
>
>
> Regards,
>
> Robert
>
>
>
>
> On Thu, Jan 22, 2015 at 8:15 AM, Tsuyoshi Ozawa wrote:
>
>> Hi Rober
Hi,
I'd like to edit contributor list to add new contributors. Does anyone
know how to do that?
- Tsuyoshi
ARN/roles
>
> Ravi - you already had permissions to add contributors. Tsuyoshi - I just
> added you.
>
> On Tue, Jan 27, 2015 at 1:26 AM, Ravi Prakash wrote:
>
>> I too would like that capability. ~raviprak
>>
>>
>> On Friday, January 23, 2015 11:27 AM, Ts
Hi Suma,
I think ZooKeeper can handle thousands of updates, so thousands of
jobs can be "launched" at the same time.
More jobs can be running at the same time since the number of updates
against ZooKeeper is less than the number of jobs. Please free to ask
us if you face the scalability or perform
> I think ZooKeeper can handle thousands of updates,
I meant "thousands of updates per second".
Thanks,
- Tsuyoshi
On Fri, Feb 13, 2015 at 3:59 PM, Tsuyoshi Ozawa wrote:
> Hi Suma,
>
> I think ZooKeeper can handle thousands of updates, so thousands of
> jobs can be &q
Hi hadoop developers,
Last 2 weeks, a bug of JDK about TimSort, related to Collections#sort,
is reported. How can we deal with this problem?
http://envisage-project.eu/timsort-specification-and-verification/
https://bugs.openjdk.java.net/browse/JDK-8072909
The bug causes ArrayIndexOutOfBoundsEx
algorithms for stability.
Thanks,
- Tsuyoshi
On Thu, Feb 26, 2015 at 5:04 PM, Tsuyoshi Ozawa wrote:
> Hi hadoop developers,
>
> Last 2 weeks, a bug of JDK about TimSort, related to Collections#sort,
> is reported. How can we deal with this problem?
>
> http://envisage-project.
Allen and Steve,
Should we mark HADOOP-11602 as a blocker issue?
Thanks,
- Tsuyoshi
On Mon, Mar 2, 2015 at 4:58 AM, Arun Murthy wrote:
> Sounds good, thanks for the help Vinod!
>
> Arun
>
>
> From: Vinod Kumar Vavilapalli
> Sent: Sunday, March 01, 2015 1
Hi Allen,
Thank you for the great suggestion. Let's do this!
Thanks,
- Tsuyoshi
On Fri, Mar 20, 2015 at 2:34 AM, Allen Wittenauer wrote:
>
> Hi folks,
>
> There are ~6,000 Hadoop JIRA issues that have gone unaddressed,
> including ~900 with patches waiting to be reviewed. Among other
+1 (non-binding)
- Verified checksums on source and binary tar ball.
- Built from source and launched single cluster.
- Checked to launch some jobs successfully.
- Killing application via RM UI.
Thanks,
- Tsuyoshi
On Mon, Apr 13, 2015 at 7:43 AM, Junping Du wrote:
> +1. (Non-binding)
> - Downlo
Hey Akira, could you target the issues to 2.7.1?
Thanks,
- Tsuyoshi
On Wed, Apr 15, 2015 at 2:51 PM, Akira AJISAKA
wrote:
> +0 (non-binding)
>
> - Downloaded source
> - Built from source
> - Ran a pseudo-distributed cluster
> - Read documents downloaded from binary tarball
> - Looked Web UIs
>
>
I'd like to agree with Vinod's suggestion.
Thanks,
- Tsuyoshi
On Fri, Apr 17, 2015 at 9:12 AM, Vinod Kumar Vavilapalli
wrote:
> Quick look tells me this is a bug that needs fixing.
>
> Am on the road, so couldn't close the vote right after 5 days.
>
> Seeing as this is coming up beyond the votin
jobs after restart.
>
> I believe we should at least investigate this further to see what could
> have been going on.
Thanks,
- Tsuyoshi
On Fri, Apr 17, 2015 at 12:47 PM, Tsuyoshi Ozawa wrote:
> I'd like to agree with Vinod's suggestion.
>
> Thanks,
> - Tsuyosh
Hi Grandl,
Hadoop Wiki's HowToContribute page is useful for you.
http://wiki.apache.org/hadoop/HowToContribute
CodeReviewChecklist may also be useful for you, because it describes
how committers check your patch.
https://wiki.apache.org/hadoop/CodeReviewChecklist
Looking forward to your contribu
IMHO, it's useful to release 2.5 as intermediate release. The working
items which are not ready for 2.5 will be target for 2.6, right?
Thanks,
- Tsuyoshi
On Tue, Jun 10, 2014 at 5:03 PM, wrote:
> Arun,
>
> Any possibility of getting HDFS-6376 committed and backported into 2.5?
>
> Dave Marion
IMHO, I'd like to +1 to include YARN-1492 and work-preserving restart
in 2.6. I believe they are good improvement, but they are
work-in-progress and it takes a bit time to be done.
Thanks,
- Tsuyoshi
On Tue, Jun 24, 2014 at 7:13 AM, Jian He wrote:
> Just found the roadmap includes a wrong jira l
+1(non-binding)
On Wed, Jun 25, 2014 at 1:55 AM, Hitesh Shah wrote:
> +1 (binding)
>
> — Hitesh
>
> On Jun 24, 2014, at 1:53 AM, Arun C Murthy wrote:
>
>> Folks,
>>
>> As discussed, I'd like to call a vote on changing our by-laws to change
>> release votes from 7 days to 5.
>>
>> I've attached
+1(non-binding)
- Built from source.
- Ran tests.
-- Reproduced HADOOP-10510 on AWS instance(Ubuntu Server 14.04 LTS
(PV) - ami-bddaa2bc (64-bit)). I agree with that this problem will be
fixed after releases when voting at 2.4.0. I believe that this problem
is environment-depend one.
- Deployed si
Hi, I think you need to rebase a patch on trunk code because trunk
code by subversion or by git is changed.
Thanks,
- Tsuyoshi
On Mon, Jun 30, 2014 at 11:00 AM, Hou, GuoboX wrote:
> This is my patch:
> https://issues.apache.org/jira/secure/attachment/12651387/trust.patch
> This is the output:
: Monday, June 30, 2014 10:27 AM
>> > To: yarn-dev@hadoop.apache.org
>> > Subject: Re: Submitting patch
>> >
>> > There is no QA run for non-trunk branches.
>> >
>> > Please attach re-generated patch for trunk.
>> > trust001.patch
>> >
Hi,
To edit the document you mentioned, please edit
hadoop-common/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/WritingYarnApplications.apt.vm
The document of apt.vm is written in "APT format", which is described
in the following document:
http://maven.apache.org/doxia/references/
Hi Wangda,
The following link is same link as Karthik mentioned:
https://issues.apache.org/jira/browse/YARN-2247?jql=project%20in%20(Hadoop%2C%20HDFS%2C%20YARN%2C%20%22Hadoop%20Map%2FReduce%22)%20AND%20resolution%20%3D%20Unresolved%20AND%20%22Target%20Version%2Fs%22%20%3D%202.5.0%20AND%20priority
+1 for Karthik's suggestion.
- Tsuyoshi
On Wed, Jul 23, 2014 at 6:54 AM, Karthik Kambatla wrote:
> Hi devs
>
> As you might have noticed, we have several classes and methods in them that
> are not annotated at all. This is seldom intentional. Avoiding incompatible
> changes to all these classes
Thank you for great suggestion, Karthik. +1(non-binding) to use git.
I'm also using private git repository.
Additionally, I have one question. Will we accept github-based
development like Apache Spark? IHMO, it allow us to leverage Hadoop
development, because the cost of sending pull request is ver
pens up the possibility for better review workflows, but we can
> discuss that on a different thread.
>
> A few different people have also mentioned Gerrit, so that'd be in the
> running along with Github (and I guess ReviewBoard).
>
> Thanks,
> Andrew
>
>
> On Mon, A
-1 (non-binding).
* Downloaded source and verified signature.
* Built from source.
* Ran tests and some MR jobs.
* Ran RM-HA with manual failover mode.
- Documents are missing.
Good catch, Akira. As he mentioned, the documents including javadocs
are missing from the binary tar ball. We should inc
+1(non-binding)
Thanks,
- Tsuyoshi
On Sat, Aug 9, 2014 at 11:57 AM, Karthik Kambatla wrote:
> I have put together this proposal based on recent discussion on this topic.
>
> Please vote on the proposal. The vote runs for 7 days.
>
>1. Migrate from subversion to git for version control.
>
1 - 100 of 198 matches
Mail list logo
