Zhijie Shen created MAPREDUCE-5940:
--
Summary: Avoid negative elapsed time in JHS/MRAM web UI and
services
Key: MAPREDUCE-5940
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5940
Project: Hadoop
On Jun 24, 2014, at 4:22 PM, Andrew Wang wrote:
> Since Hadoop apps can and do depend on the Hadoop classpath, the classpath
> is effectively part of our API. I'm sure there are user apps out there that
> will break if we make incompatible changes to the classpath. I haven't read
> up on the MR
Alejandro,
On Tue, Jun 24, 2014 at 4:44 PM, Alejandro Abdelnur
wrote:
> After reading this thread and thinking a bit about it, I think it should be
> OK such move up to JDK7 in Hadoop 2 for the following reasons:
>
> * Existing Hadoop 2 releases and related projects are running
> on JDK7 in p
+1, though I think 2.5 may be premature if we want to send a warning note
"last ever". That's an issue for followon "when in branch 2".
Guava and protobuf.jar are two things we have to leave alone, with the
first being unfortunate, but their attitude to updates is pretty dramatic.
The latter? We a
On 24 June 2014 16:22, Andrew Wang wrote:
> Steve can do a better job explaining
> this to me, but we haven't bumped things like Jetty or Guava because they
> are on the classpath and are not compatible. There is this line in the
> compat guidelines:
>
The current jetty version has unreliability
After reading this thread and thinking a bit about it, I think it should be
OK such move up to JDK7 in Hadoop 2 for the following reasons:
* Existing Hadoop 2 releases and related projects are running
on JDK7 in production.
* Commercial vendors of Hadoop have already done lot of
work to ensure
Hi all,
On dependencies, we've bumped library versions when we think it's safe and
the APIs in the new version are compatible. Or, it's not leaked to the app
classpath (e.g the JUnit version bump). I think the JIRAs Arun mentioned
fall into one of those categories. Steve can do a better job explai
While we haven't codified this in our compatibility guidelines, dropping a
Java version seems to me like change that needs to happen alongside a major
release. In plain talk, it has the ability to break everything for users
who aren't doing anything particularly unreasonable.
I don't think we sho
+1
Vinod
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 the change to by-laws I'm proposing.
>
> Please vote, the vote will the usual period of 7 days.
Tx for the new thread Andrew, hopefully it can attract more eyes.
Here's what I am behind - a modified proposal C.
- Overall I wouldn't think about EOL of JDK7 and/or JDK8 specifically given
how long it has taken for JDK6 life-cycle to end. We should try to focus on
JDK7 only for now.
- As we
That classpath policy was explicitly added because we can't lock down our
dependencies for security/bug fix reasons, and also because if we do update
something explicitly, their transitive dependencies can change -beyond our
control.
https://issues.apache.org/jira/browse/HADOOP-9555 is an example
Andrew,
Thanks for starting this thread. I'll edit the wiki to provide more context
around rolling-upgrades etc. which, as I pointed out in the original thread,
are key IMHO.
On Jun 24, 2014, at 11:17 AM, Andrew Wang wrote:
> https://wiki.apache.org/hadoop/MovingToJdk7and8
>
> I think based
Hi David,
UserGroupInformation.createRemoteUser does not attach credentials to the
returned ugi. I expect the server side is rejecting the connection due to
lack of credentials. This is actually by design. The
UserGroupInformation.createRemoteUser method is primarily intended for use
on the ser
+1
On Tue, Jun 24, 2014 at 11:13 AM, Chris Douglas wrote:
> +1 -C
>
> On Tue, 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 the change to by-la
+1 -C
On Tue, 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 the change to by-laws I'm proposing.
>
> Please vote, the vote will the usual period of 7 days.
+1 (binding)
Chris Nauroth
Hortonworks
http://hortonworks.com/
On Tue, Jun 24, 2014 at 10:58 AM, Jakob Homan wrote:
> +1 (binding)
>
>
> On Tue, Jun 24, 2014 at 10:33 AM, Zhijie Shen
> wrote:
>
> > +1 (non-binding)
> >
> >
> > On Wed, Jun 25, 2014 at 1:26 AM, Aaron T. Myers
> wrote:
> >
> >
+1 (binding)
On Tue, Jun 24, 2014 at 10:33 AM, Zhijie Shen wrote:
> +1 (non-binding)
>
>
> On Wed, Jun 25, 2014 at 1:26 AM, Aaron T. Myers wrote:
>
> > +1 (binding)
> >
> > --
> > Aaron T. Myers
> > Software Engineer, Cloudera
> >
> >
> > On Tue, Jun 24, 2014 at 1:53 AM, Arun C Murthy
> > wro
+1 (non-binding)
(2014/06/24 10:33), Zhijie Shen wrote:
+1 (non-binding)
On Wed, Jun 25, 2014 at 1:26 AM, Aaron T. Myers wrote:
+1 (binding)
--
Aaron T. Myers
Software Engineer, Cloudera
On Tue, Jun 24, 2014 at 1:53 AM, Arun C Murthy
wrote:
Folks,
As discussed, I'd like to call a v
+1 (non-binding)
On Wed, Jun 25, 2014 at 1:26 AM, Aaron T. Myers wrote:
> +1 (binding)
>
> --
> Aaron T. Myers
> Software Engineer, Cloudera
>
>
> On Tue, 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 chan
+1 (binding)
--
Aaron T. Myers
Software Engineer, Cloudera
On Tue, 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 the change to by-laws I'm proposing.
>
>
+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 (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 the change to by-laws I'm proposing.
>
> Please vote, the vote will the usual pe
+1 (non-binding)
On Tue, Jun 24, 2014 at 8:54 AM, Jason Lowe
wrote:
> +1 (binding)
>
> Jason
>
>
> On 06/24/2014 03: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 th
+1 (binding)
Jason
On 06/24/2014 03: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 the change to by-laws I'm proposing.
Please vote, the vote will the usual period of 7 days.
tha
+1 (binding)
-Sandy
On Tue, Jun 24, 2014 at 7:53 AM, Devaraj K wrote:
> +1
>
> Thanks
> Devaraj K
>
>
> On Tue, Jun 24, 2014 at 2:23 PM, 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.
> >
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1811/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 35040 lines...]
Running org.apache.hadoop.mapreduce.
+1 (non-binding)
Deployed in a two node cluster and ran few M/R Jobs, everything works fine.
On Thu, Jun 19, 2014 at 8:44 PM, Thomas Graves <
tgra...@yahoo-inc.com.invalid> wrote:
> Hey Everyone,
>
> There have been various bug fixes that have went into
> branch-0.23 since the 0.23.10 releas
+1
Thanks
Devaraj K
On Tue, Jun 24, 2014 at 2:23 PM, 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 the change to by-laws I'm proposing.
>
> Please vote, the vote will the usual pe
+1
On Tue, Jun 24, 2014 at 6:42 AM, Thomas Graves <
tgra...@yahoo-inc.com.invalid> wrote:
> +1
>
> Tom
>
> On 6/24/14, 3: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 atta
+1
Tom
On 6/24/14, 3: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 the change to by-laws I'm proposing.
>
> Please vote, the vote will the usual period of 7 days.
>
>thanks,
>A
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 the change to by-laws I'm proposing.
Please vote, the vote will the usual period of 7 days.
thanks,
Arun
[main]$ svn diff
Index: author/src/documentation/conte
31 matches
Mail list logo
