See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/172/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 10220 lines...]
[INFO] Reactor Summary:
[INFO]
On Wed, Apr 22, 2015 at 2:10 AM, Allen Wittenauer a...@altiscale.com wrote:
* There have been a few runs which seems to indicate that *something* is
destroying the artifact directory in the middle of runs…. which is very
very odd and something I hadn’t seen in any of my testing. In any
Peng Zhang created MAPREDUCE-6329:
-
Summary: Failure of start map task on NM cause job hang
Key: MAPREDUCE-6329
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6329
Project: Hadoop Map/Reduce
Vinod Kumar Vavilapalli created MAPREDUCE-6331:
--
Summary: [Umbrella] Make MapReduce work with Timeline Service
Nextgen (YARN-2928)
Key: MAPREDUCE-6331
URL:
Hey gang,
Just so everyone is aware, if you are working on a patch for either a
feature branch or a major branch, if you name the patch with the branch name
following the spec in HowToContribute (and a few other ways… test-patch tries
to figure it out!), test-patch.sh
Does this mean HADOOP-7435 is no longer needed / closeable as dup?
Thanks
+Vinod
On Apr 22, 2015, at 12:34 PM, Allen Wittenauer a...@altiscale.com wrote:
Hey gang,
Just so everyone is aware, if you are working on a patch for either a
feature branch or a major branch, if you
More than likely. It probably needs more testing (esp under Jenkins).
It should be noted that the code in test-patch.sh has lots of problems with
branch-0, minor, and micro releases. But for major releases, it seems to work
well for me. :)
On Apr 22, 2015, at 8:45 PM, Vinod Kumar
Rohith created MAPREDUCE-6332:
-
Summary: Add more required API's to MergeManager interface
Key: MAPREDUCE-6332
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6332
Project: Hadoop Map/Reduce
It took a while for the artifact distribution to come around, I initially had
trouble pushing them from home too.
Anyways, I just updated the website too. Sending an announcement now..
Thanks,
+Vinod
On Apr 20, 2015, at 8:06 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com
wrote:
With 22
+dev lists.
Forgot about that, sure. I added this and my initial list to the Roadmap wiki.
Thank
+Vinod
On Apr 21, 2015, at 9:34 PM, Rohith Sharma K S rohithsharm...@huawei.com
wrote:
Dear Vinod
Regarding the road map of Hadoop-2.8.0, Can basic Application priority
working model
Siqi Li created MAPREDUCE-6333:
--
Summary: TestEvents,TestAMWebServicesTasks,TestAppController are
broken due to MAPREDUCE-6297
Key: MAPREDUCE-6333
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6333
You're absolutely right Steve. We should get the jobs under control.
At the very least, before we move to JDK 8 in Jenkins, we should get the
Java8 nightly builds working. I didn't realize we had these, and I had
thought all compiling and most test issues with JDK8 were already fixed
based on
Thanks for forking this Vinod,
Linux used to do the odd/even minor versions for unstable/stable, but that
went away when 2.6 lasted forever. With the 3.x and 4.x I think it's just
always stable. The odd/even though was at least a convention everyone knew
about.
Stack can comment better than I
Approach (1) seems like a good way to handle stability concerns people
might have. If we explicitly distinguish between current and stable (i.e.,
not set them both to the latest release). It would be nice to do a VOTE for
calling a release stable.
I would use approach (2) for compatibility
Hi Allen,
This sounds great.
Naming a patch foo-HDFS-7285.00.patch should get tested on the HDFS-7285
branch.
Does it happen locally in developer's machine when running test-patch.sh, or
also mean something in Hadoop Jenkins building when a JIRA becoming patch
available? Thanks.
Regards,
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2121/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 31433 lines...]
[INFO] Reactor Summary:
[INFO]
Oh, this is also in the release notes, but one can use a git reference # as
well. :) (with kudos to OOM for the idea.)
On Apr 22, 2015, at 8:57 PM, Allen Wittenauer a...@altiscale.com wrote:
More than likely. It probably needs more testing (esp under Jenkins).
It should be noted that
Forking the thread.
In the previous 2.7.1 thread [1], there were enough yays to my proposal to wait
for a bug-fix release or two before calling a 2.x release stable. There were
some concerns about the naming.
We have two options, taking 2.8 as an example
(1) Release 2.8.0, call it as an alpha
Some status:
* So far, HADOOP-11627 was filed which is luckily an extremely easy bug to fix.
* There have been a few runs which seems to indicate that *something* is
destroying the artifact directory in the middle of runs…. which is very very
odd and something I hadn’t seen in any of my
Err, first jira mentioned should be HADOOP-11861.
On Apr 22, 2015, at 8:10 AM, Allen Wittenauer a...@altiscale.com wrote:
Some status:
* So far, HADOOP-11627 was filed which is luckily an extremely easy bug to
fix.
* There have been a few runs which seems to indicate that *something*
On 21 Apr 2015, at 23:31, Andrew Wang andrew.w...@cloudera.com wrote:
Hey Robert,
As a first step, could we try switching all our precommit and nightly
builds over to use 1.8? This is a prerequisite for HADOOP-11858, and safe
to do in any case since it'll still target 1.7.
+1
we have
Ryu Kobayashi created MAPREDUCE-6330:
Summary: Fix typo in some Task Attempt API's URL
Key: MAPREDUCE-6330
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6330
Project: Hadoop Map/Reduce
I took the code from https://github.com/raghuveerm/MRPcapParser and updated it
to parse binary pcap files. I have large number of small files to be processed.
Following are the steps i have already tried to resolve the issue:
- Tried setting mapred.child.java.opts=-Xmx2048m
- Tried
23 matches
Mail list logo
