hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantin Shvachko <shv.had...@gmail.com>
Subject Re: About 2.7.4 Release
Date Fri, 05 May 2017 02:21:33 GMT
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 backports are pretty straightforward,
but not all.

We can create tracking jiras for backporting if you need to run Jenkins on
the patch (and since Allen does not allow reopening them).
But I think the final patch should be attached to the original jira.
Otherwise history will be hard to follow.

Thanks,
--Konstantin

On Wed, May 3, 2017 at 4:53 PM, Zhe Zhang <zhz@apache.org> wrote:

> 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 <shv.hadoop@gmail.com>
> wrote:
>
>> 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 you.
>> Otherwise I am glad to volunteer as the release manager.
>>
>> 2. In addition to current blockers and criticals, I would like to propose
>> a
>> few issues to be included in the release, see the list below. Those are
>> mostly bug fixes and optimizations, which we already have in our internal
>> branch and run in production. Plus one minor feature "node labeling",
>> which
>> we found very handy, when you have heterogeneous environments and mixed
>> workloads, like MR and Spark.
>>
>> 3. For marking issues for the release I propose to
>>  - set the target version to 2.7.4, and
>>  - add a new label "release-blocker"
>> That way we will know issues targeted for the release without reopening
>> them for backports.
>>
>> 4. I see quite a few people are interested in the release. With all the
>> help I think we can target to release by the end of May.
>>
>> Other things include fixing CHANGES.txt and fixing Jenkins build for 2.7.4
>> branch.
>>
>> Thanks,
>> --Konstantin
>>
>> ==========  List of issue for 2.7.4  ===========
>> ------ Backports
>> HADOOP-12975 <https://issues.apache.org/jira/browse/HADOOP-12975>. Add du
>> jitters
>> HDFS-9710 <https://issues.apache.org/jira/browse/HDFS-9710>. IBR batching
>> HDFS-10715 <https://issues.apache.org/jira/browse/HDFS-10715>. NPE when
>> applying AvailableSpaceBlockPlacementPolicy
>> HDFS-2538 <https://issues.apache.org/jira/browse/HDFS-2538>. fsck removal
>> of dot printing
>> HDFS-8131 <https://issues.apache.org/jira/browse/HDFS-8131>.
>> space-balanced
>> policy for balancer
>> HDFS-8549 <https://issues.apache.org/jira/browse/HDFS-8549>. abort
>> balancer
>> if upgrade in progress
>> HDFS-9412 <https://issues.apache.org/jira/browse/HDFS-9412>. skip small
>> blocks in getBlocks
>>
>> YARN-1471 <https://issues.apache.org/jira/browse/YARN-1471>. SLS
>> simulator
>> YARN-4302 <https://issues.apache.org/jira/browse/YARN-4302>. SLS
>> YARN-4367 <https://issues.apache.org/jira/browse/YARN-4367>. SLS
>> YARN-4612 <https://issues.apache.org/jira/browse/YARN-4612>. SLS
>>
>> ----- Node labeling
>> MAPREDUCE-6304 <https://issues.apache.org/jira/browse/MAPREDUCE-6304>
>> YARN-2943 <https://issues.apache.org/jira/browse/YARN-2943>
>> YARN-4109 <https://issues.apache.org/jira/browse/YARN-4109>
>> YARN-4140 <https://issues.apache.org/jira/browse/YARN-4140>
>> YARN-4250 <https://issues.apache.org/jira/browse/YARN-4250>
>> YARN-4925 <https://issues.apache.org/jira/browse/YARN-4925>
>>
> --
> Zhe Zhang
> Apache Hadoop Committer
> http://zhe-thoughts.github.io/about/ | @oldcap
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message