HADOOP/Hadoop+2.7.4
>
> If you want to edit this wiki, please ping me.
>
> Regards,
> Akira
>
>
> On 2017/05/23 4:42, Brahma Reddy Battula wrote:
>
> Hi Konstantin Shvachko
>
>
>
> how about creating a wiki page for 2.7.4 release status like 2.8 and
>
ight now, I'll let him elaborate.
>> Erik, you should probably respond on Apache dev list, as I think it could
>> be interesting for other people as well, asince we planned to open source
>> it. You can fork the "About 2.7.4 Release" thread with a new subjec
orking
>> on this project right now, I'll let him elaborate.
>> Erik, you should probably respond on Apache dev list, as I think it could
>> be interesting for other people as well, asince we planned to open source
>> it. You can fork the "About 2.7.4 Release"
ki, please ping me.
>>>>>
>>>>> Regards,
>>>>> Akira
>>>>>
>>>>>
>>>>> On 2017/05/23 4:42, Brahma Reddy Battula wrote:
>>>>>
>>>>> Hi Konstantin Shvachko
>>>>>&
gmail.com>
> >wrote:
> >
> >> Hi Tianyi,
> >>
> >> Glad you are interested in Dynamometer. Erik (CC-ed) is actively working
> >> on this project right now, I'll let him elaborate.
> >> Erik, you should probably respond on Ap
27;ll let him elaborate.
>> Erik, you should probably respond on Apache dev list, as I think it could
>> be interesting for other people as well, asince we planned to open source
>> it. You can fork the "About 2.7.4 Release" thread with a new subject and
>> give some det
Apache dev list, as I think it could
> be interesting for other people as well, asince we planned to open source
> it. You can fork the "About 2.7.4 Release" thread with a new subject and
> give some details about Dynamometer there.
>
> Thanks,
> --Konstantin
>
>
gt;>> On 2017/05/23 4:42, Brahma Reddy Battula wrote:
>>>>
>>>> Hi Konstantin Shvachko
>>>>>
>>>>>
>>>>> how about creating a wiki page for 2.7.4 release status like 2.8 and
>>>>> trunk in following link.??
&
t;
>>>> how about creating a wiki page for 2.7.4 release status like 2.8 and
>>>> trunk in following link.??
>>>>
>>>>
>>>> https://cwiki.apache.org/confluence/display/HADOOP
>>>>
>>>>
>>>> _
wing link.??
https://cwiki.apache.org/confluence/display/HADOOP
From: Konstantin Shvachko
Sent: Saturday, May 13, 2017 3:58 AM
To: Akira Ajisaka
Cc: Hadoop Common; Hdfs-dev; mapreduce-...@hadoop.apache.org;
yarn-...@hadoop.apache.org
Subject: Re: About 2.7.4 Rel
link.??
>>
>>
>> https://cwiki.apache.org/confluence/display/HADOOP
>>
>>
>>
>> From: Konstantin Shvachko
>> Sent: Saturday, May 13, 2017 3:58 AM
>> To: Akira Ajisaka
>> Cc: Hadoop Common; Hdfs-dev; mapreduce-...@hadoop.apache.org;
>> yarn-...
Subject: Re: About 2.7.4 Release
Latest update on the links and filters. Here is the correct link for the
filter:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?requestId=12340814
Also updated: https://s.apache.org/Dzg4
Had to do some Jira debugging. Sorry for confusion.
Thanks
: Hadoop Common; Hdfs-dev; mapreduce-...@hadoop.apache.org;
yarn-...@hadoop.apache.org
Subject: Re: About 2.7.4 Release
Latest update on the links and filters. Here is the correct link for the
filter:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?requestId=12340814
Also updated: https
ache.org/jira/browse/HDFS-9311===Life Line Protocol
>>>> https://issues.apache.org/jira/browse/HDFS-10987===Deecommission
>>>> Expensive when lot's of blocks are present
>>>>
>>>> https://issues.apache.org/jira/browse/HDFS-9902===
>>>&g
n
>>> Expensive when lot's of blocks are present
>>>
>>> https://issues.apache.org/jira/browse/HDFS-9902===
>>> "dfs.datanode.du.reserved" per Storage Type
>>>
>>> For Security:
>>> =
>>> https://issu
ions
Regards
Brahma Reddy Battula
-Original Message-
From: Erik Krogen [mailto:ekro...@linkedin.com.INVALID]
Sent: 06 May 2017 02:40
To: Konstantin Shvachko
Cc: Zhe Zhang; Hadoop Common; Hdfs-dev; mapreduce-...@hadoop.apache.org;
yarn-...@hadoop.apache.org
Subject: Re: About 2.7.4 Release
List
est version to fix vulnerability in old versions
>
>
>
> Regards
> Brahma Reddy Battula
>
> -Original Message-
> From: Erik Krogen [mailto:ekro...@linkedin.com.INVALID]
> Sent: 06 May 2017 02:40
> To: Konstantin Shvachko
> Cc: Zhe Zhang; Hadoop Common; Hdfs-dev; mapre
en [mailto:ekro...@linkedin.com.INVALID]
Sent: 06 May 2017 02:40
To: Konstantin Shvachko
Cc: Zhe Zhang; Hadoop Common; Hdfs-dev; mapreduce-...@hadoop.apache.org;
yarn-...@hadoop.apache.org
Subject: Re: About 2.7.4 Release
List LGTM Konstantin!
Let's say that we will only create a new track
List LGTM Konstantin!
Let's say that we will only create a new tracking JIRA for patches which do
not backport cleanly, to avoid having too many lying around. Otherwise we
can directly attach to old ticket. If a clean backport does happen to break
a test the nightly build will help us catch it.
E
Great Zhe. Let's monitor the build.
I marked all jiras I knew of for inclusion into 2.7.4 as I described before.
Target Version/s: 2.7.4
Label: release-blocker
Here is the link to the list: https://s.apache.org/Dzg4
Please let me know if I missed anything.
And feel free to pick up any. Most of ba
Thanks for volunteering as RM Konstantin! The plan LGTM.
I've created a nightly Jenkins job for branch-2.7 (unit tests):
https://builds.apache.org/job/Hadoop-branch2.7-nightly/
On Wed, May 3, 2017 at 12:42 AM Konstantin Shvachko
wrote:
> Hey guys,
>
> I and a few of my colleagues would like to
Hey guys,
I and a few of my colleagues would like to help here and move 2.7.4 release
forward. A few points in this regard.
1. Reading through this thread since March 1 I see that Vinod hinted on
managing the release. Vinod, if you still want the job / have bandwidth
will be happy to work with yo
Can we wait for 2.7.4 first? There are still backports happening to
branch-2.7. After that, there shouldn't be many backports since both 2.8.x
and 2.7.x will be up-to-date with what's in 3.0.0-alpha1 and 3.0.0-alpha2.
On Tue, May 2, 2017 at 4:07 PM, Allen Wittenauer
wrote:
>
> Is there any reas
Is there any reason to not Close -alpha1+resolved state JIRAs? It's been quite
a while and those definitely should not getting re-opened anymore. What about
-alpha2's that are also resolved?
-
To unsubscribe, e-mail: hdfs-dev-
On Mon, May 1, 2017 at 3:44 PM, Allen Wittenauer
wrote:
>
> > On May 1, 2017, at 2:27 PM, Andrew Wang
> wrote:
> > I believe I asked about this on dev-yetus a while back. I'd prefer that
> the presence of the fix version be sufficient to indicate whether a JIRA is
> included in a release branch.
> On May 1, 2017, at 2:27 PM, Andrew Wang wrote:
> I believe I asked about this on dev-yetus a while back. I'd prefer that the
> presence of the fix version be sufficient to indicate whether a JIRA is
> included in a release branch. Yetus requires that the JIRA be resolved as
> "Fixed" to show
I didn't close JIRAs after the 3.0.0-alpha1 or alpha2 releases since
closing makes the JIRAs read-only. This makes it more annoying to backport
to older releases and for concurrent releases in general.
I believe I asked about this on dev-yetus a while back. I'd prefer that the
presence of the fix
Thanks Allen for the additional information.
> At one point, JIRA was configured to refuse re-opening after a
release is cut.
In the past, release manager closed the tickets and the process is
written in the wiki: https://wiki.apache.org/hadoop/HowToRelease
> 10. In JIRA, close issues resol
> On Apr 25, 2017, at 12:35 AM, Akira Ajisaka wrote:
> > Maybe we should create a jira to track this?
>
> I think now either way (reopen or create) is fine.
>
> Release doc maker creates change logs by fetching information from JIRA, so
> reopening the tickets should be avoided when a release
oop Common; yarn-...@hadoop.apache.org; Hdfs-dev;
mapreduce-...@hadoop.apache.org
Subject: Re: About 2.7.4 Release
> It would be great to backport HDFS-9710 to 2.7.4 as this is one of the >
critical fixes on scalability.
Sounds good.
> Maybe we should create a jira to track this?
Akira Ajisaka [mailto:aajis...@apache.org]
Sent: 25 April 2017 15:36
To: Haohui Mai
Cc: Brahma Reddy Battula; Andrew Wang; Sangjin Lee; Vinod Kumar Vavilapalli;
Marton Elek; Hadoop Common; yarn-...@hadoop.apache.org; Hdfs-dev;
mapreduce-...@hadoop.apache.org
Subject: Re: About 2.7.4 Release
>
dera.com]
Sent: 08 March 2017 04:22
To: Sangjin Lee
Cc: Marton Elek; Hadoop Common; yarn-...@hadoop.apache.org; Hdfs-dev;
mapreduce-...@hadoop.apache.org
Subject: Re: About 2.7.4 Release
Our release steps are documented on the wiki:
2.6/2.7:
https://wiki.apache.org/hadoop/HowToReleasePreDSBC
this..
>>
>>
>>
>> Regards
>> Brahma Reddy Battula
>>
>> -Original Message-
>> From: Andrew Wang [mailto:andrew.w...@cloudera.com]
>> Sent: 08 March 2017 04:22
>> To: Sangjin Lee
>> Cc: Marton Elek; Hadoop Common; yarn-...@hadoop.
ttula
-Original Message-
From: Andrew Wang [mailto:andrew.w...@cloudera.com]
Sent: 08 March 2017 04:22
To: Sangjin Lee
Cc: Marton Elek; Hadoop Common; yarn-...@hadoop.apache.org; Hdfs-dev;
mapreduce-...@hadoop.apache.org
Subject: Re: About 2.7.4 Release
Our release steps are documented on the
-...@hadoop.apache.org; Hdfs-dev;
mapreduce-...@hadoop.apache.org
Subject: Re: About 2.7.4 Release
Our release steps are documented on the wiki:
2.6/2.7:
https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
2.8+:
https://wiki.apache.org/hadoop/HowToRelease
I think given the push toward 2.8 and 3.0, there&#
> On Mar 8, 2017, at 1:54 PM, Allen Wittenauer
> wrote:
>
> This is already possible:
> * don’t use —asfrelease
> * use —sign, —native, and, if appropriate for your platform,
> —docker and —dockercache
Oh yeah, I forgot about this:
https://effective
> On Mar 8, 2017, at 10:55 AM, Marton Elek wrote:
>
> I think the main point here is the testing of the release script, not the
> creation of the official release.
… except the Hadoop PMC was doing exactly this from 2.3.0 up until
recently. Which means we have a few years worth of rel
-...@hadoop.apache.org; Hdfs-dev;
mapreduce-...@hadoop.apache.org
Subject: Re: About 2.7.4 Release
> On Mar 7, 2017, at 2:51 PM, Andrew Wang wrote:
> I think it'd be nice to
> have a nightly Jenkins job that builds an RC,
Just a reminder that any such build cannot be used
PM
To: Sangjin Lee
Cc: Marton Elek; common-...@hadoop.apache.org; yarn-...@hadoop.apache.org;
Hdfs-dev; mapreduce-...@hadoop.apache.org
Subject: Re: About 2.7.4 Release
I was planning to take this up, celebrating my return from my paternity leave
of absence for quite a while.
Marton, let me know
> On Mar 7, 2017, at 2:51 PM, Andrew Wang wrote:
> I think it'd be nice to
> have a nightly Jenkins job that builds an RC,
Just a reminder that any such build cannot be used for an actual
release:
http://www.apache.org/legal/release-policy.html#owned-controlled-hardware
I was planning to take this up, celebrating my return from my paternity leave
of absence for quite a while.
Marton, let me know if you do want to take this up instead and we can work
together.
Thanks
+Vinod
> On Mar 7, 2017, at 9:13 AM, Sangjin Lee wrote:
>
> If we have a volunteer for relea
appy to do any task for new
> > maintenance releases (or more frequent releases).
> >
> > Regards,
> > Marton
> >
> >
> > ____________
> > From: Akira Ajisaka
> > Sent: Tuesday, March 07, 2017 7:34 AM
> &
egards,
> Marton
>
>
>
> From: Akira Ajisaka
> Sent: Tuesday, March 07, 2017 7:34 AM
> To: Brahma Reddy Battula; Hadoop Common; yarn-...@hadoop.apache.org;
> Hdfs-dev; mapreduce-...@hadoop.apache.org
> Subject: Re: Ab
Regards,
Marton
From: Akira Ajisaka
Sent: Tuesday, March 07, 2017 7:34 AM
To: Brahma Reddy Battula; Hadoop Common; yarn-...@hadoop.apache.org; Hdfs-dev;
mapreduce-...@hadoop.apache.org
Subject: Re: About 2.7.4 Release
Probably 2.8.0 will be relea
Probably 2.8.0 will be released soon.
https://issues.apache.org/jira/browse/HADOOP-13866?focusedCommentId=15898379&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15898379
I'm thinking 2.7.4 release process starts after 2.8.0 release,
so 2.7.4 will be released in Apr
Hi All
It has been six months for branch-2.7 release.. is there any near plan for
2.7.4..?
Thanks&Regards
Brahma Reddy Battula
46 matches
Mail list logo
