Looks following link is not correct.. https://s.apache.org/Dzg4
It should be like following..? https://s.apache.org/wi3U Apart from Konstantin mentioned,Following also good to go..? let me know your thoughts on this. For Large Cluster: ============= https://issues.apache.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=== "dfs.datanode.du.reserved" per Storage Type For Security: ========= https://issues.apache.org/jira/browse/HDFS-8312===Trash does not descent into child directories to check for permission https://issues.apache.org/jira/browse/HADOOP-14100===Upgrade Jsch jar to latest 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; 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 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. Erik On Thu, May 4, 2017 at 7:21 PM, Konstantin Shvachko <shv.had...@gmail.com> wrote: > 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 <z...@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.had...@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 > > >
