I meant we *haven't* done the compatibility check.
From: Zhijie Shen
Sent: Thursday, April 09, 2015 2:00 PM
To: yarn-...@hadoop.apache.org; common-...@hadoop.apache.org
Cc: hdfs-...@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; Vinod Kumar
Vavilapall
+1 for roll out 2.7.0 soon and continuing stabilization in 2.7.1.
Agree with Karthik, it's better to exclude all improvements unless it turns out
to blocking something.
In terms of jdiff, we have done the compatibility check for quite a while in
branch-2. Do we want to back port it to (some of)
+1. It has been a long delay for 2.7.0. It's a good time to push it out.
~Haohui
On Thu, Apr 9, 2015 at 12:56 PM, Steve Loughran wrote:
> There's a couple of S3a fixes coming along which could go into a 2.7.1;
> they've been held back to avoid rushing them in to 2.7.0 last-minute.
>
>> On 9 Apr
There's a couple of S3a fixes coming along which could go into a 2.7.1; they've
been held back to avoid rushing them in to 2.7.0 last-minute.
> On 9 Apr 2015, at 20:33, Junping Du wrote:
>
> +1 (non-binding).
> The plan sounds reasonable. We should make our release train more
> fast-moving, a
+1 (non-binding).
The plan sounds reasonable. We should make our release train more fast-moving,
and predictable - it could benefit our community and ecosystem in many aspects.
Thanks,
Junping
From: Arpit Agarwal
Sent: Thursday, April 09, 2015 8:23 PM
T
+1 for 2.7.1 and +1 for promoting it to 'stable', assuming it includes no new
features or gratuitous improvements.
Arpit
On 4/9/15, 11:48 AM, "Vinod Kumar Vavilapalli" wrote:
>Hi all,
>
>I feel like we haven't done a great job of maintaining the previous 2.x
>releases. Seeing as how long 2
Vinod,
Hmmm.. it is more a bug fix than an improvement. But if you feel this cant
make it to 2.7.0, Then I guess it should be in 2.7.1 (Don't think it should
wait till 2.8)
-Arun
On Thu, Apr 9, 2015 at 11:56 AM, Vinod Kumar Vavilapalli <
vino...@hortonworks.com> wrote:
> This seems like a follow
+1, full agreement with both Vinod and Karthik. Thanks!
Chris Nauroth
Hortonworks
http://hortonworks.com/
On 4/9/15, 12:07 PM, "Karthik Kambatla" wrote:
>Inline.
>
>On Thu, Apr 9, 2015 at 11:48 AM, Vinod Kumar Vavilapalli
>> wrote:
>
>> Hi all,
>>
>> I feel like we haven't done a great jo
Inline.
On Thu, Apr 9, 2015 at 11:48 AM, Vinod Kumar Vavilapalli wrote:
> Hi all,
>
> I feel like we haven't done a great job of maintaining the previous 2.x
> releases. Seeing as how long 2.7.0 release has taken, I am sure we will
> spend more time stabilizing it, fixing issues etc.
>
> I propo
Should be okay to remove.
The policy was intended for configs that continue to be relevant like
mapred.child.java.opts. In this case, since there is no TaskTracker
anymore, leaving this config purely for compat reasons seems unnecessary.
We could also improve the policies to clarify this.
On Thu,
This seems like a follow up to a recently added feature. I see more of these
type of patches for many new features added in 2.7.0. I'd like to avoid putting
more into the already dragged on 2.7.0. We can do two things
- I started an email thread on common-dev on 2.7.1. If this looks like a small
Hi all,
I feel like we haven't done a great job of maintaining the previous 2.x
releases. Seeing as how long 2.7.0 release has taken, I am sure we will
spend more time stabilizing it, fixing issues etc.
I propose that we immediately follow up 2.7.0 with a 2.7.1 within 2-3
weeks. The focus obvious
Hey Vinod,
I was wondering if you can include
https://issues.apache.org/jira/browse/HDFS-8091 too.. Without it, i kinda
makes https://issues.apache.org/jira/browse/HDFS-6826 incomplete..
Cheers
-Arun Suresh
On Thu, Apr 9, 2015 at 11:37 AM, Vinod Kumar Vavilapalli <
vino...@hortonworks.com> wrote
A couple of weeks late, but we are here.
There is one last blocker that I am about to commit in a little while.
I am starting the release process.
+Vinod
On Mar 25, 2015, at 9:53 AM, Vinod Kumar Vavilapalli
wrote:
> Progress has been really slow, but now we are down to four blockers across
Seems like they are already in, nothing more to do here..
+Vinod
On Apr 1, 2015, at 7:45 PM, Zhijie Shen wrote:
> Can we include YARN-3273 into 2.7? YARN-3430 needs it to fix the RM web UI
> bug.
>
> Thanks,
> Zhijie
>
> From: Vinod Kumar Vavilapalli
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2108/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 39527 lines...]
[INFO]
[INFO] hadoop-mapreduce-clie
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/159/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 18729 lines...]
[INFO]
[INFO] hadoop-mapreduce
We have done this before where the properties were documented in the .xml
file, but didn't exist anywhere in the Configuration files or the rest of
the code.
HDFS-7566 (committed)
YARN-2460 (committed)
MAPREDUCE-6057 (pending)
-Ray
On Thu, Apr 9, 2015 at 4:33 AM, Akira AJISAKA
wrote:
> Hi Folk
Hi Folks,
In MAPREDUCE-6307, I'd like to remove unused
"mapreduce.tasktracker.taskmemorymanager.monitoringinterval" property,
however, the compatibility document says "Hadoop-defined properties are
to be deprecated at least for one major release before being removed."
http://hadoop.apache.or
[
https://issues.apache.org/jira/browse/MAPREDUCE-6176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Hao resolved MAPREDUCE-6176.
-
Resolution: Duplicate
Target Version/s: (was: 2.4.0, 2.5.0, 2.4.1, 2.5.1, 2.5.2)
>
[
https://issues.apache.org/jira/browse/MAPREDUCE-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Hao reopened MAPREDUCE-6220:
-
> To forbid stderr and stdout for MapReduce job
> -
>
21 matches
Mail list logo
