Apache Hadoop qbt Report: trunk+JDK8 on Linux/ppc64le

2017-01-04 Thread Apache Jenkins Server
For more details, see 
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/207/

[Jan 3, 2017 1:49:29 PM] (brahma) Revert "HDFS-11280. Allow WebHDFS to reuse 
HTTP connections to NN.
[Jan 3, 2017 5:58:00 PM] (wang) HDFS-11156. Add new op GETFILEBLOCKLOCATIONS to 
WebHDFS REST API.
[Jan 3, 2017 8:13:32 PM] (rkanter) YARN-5529. Create new DiskValidator class 
with metrics (yufeigu via
[Jan 3, 2017 9:08:38 PM] (liuml07) HADOOP-13946. Document how HDFS updates 
timestamps in the FS spec;
[Jan 3, 2017 9:16:06 PM] (cnauroth) HADOOP-13922. Some modules have 
dependencies on hadoop-client jar
[Jan 3, 2017 10:44:26 PM] (liuml07) Revert "HADOOP-13946. Document how HDFS 
updates timestamps in the FS
[Jan 3, 2017 10:46:41 PM] (wangda) Fix synchronization issues of 
AbstractYarnScheduler#nodeUpdate and its
[Jan 3, 2017 10:53:13 PM] (wangda) Revert "Fix synchronization issues of 
AbstractYarnScheduler#nodeUpdate
[Jan 3, 2017 10:53:36 PM] (wangda) YARN-6025. Fix synchronization issues of
[Jan 3, 2017 11:03:38 PM] (jdu) YARN-5923. Unable to access logs for a running 
application if
[Jan 4, 2017 2:25:46 AM] (xyao) HDFS-11279. Cleanup unused 
DataNode#checkDiskErrorAsync(). Contributed
[Jan 4, 2017 5:10:36 AM] (aajisaka) HADOOP-12733. Remove references to obsolete 
io.seqfile configuration
[Jan 4, 2017 6:39:29 AM] (rohithsharmaks) YARN-5988. RM unable to start in 
secure setup. Contributed by Ajith S.




-1 overall


The following subsystems voted -1:
compile unit


The following subsystems voted -1 but
were configured to be filtered/ignored:
cc javac


The following subsystems are considered long running:
(runtime bigger than 1h  0m  0s)
unit


Specific tests:

Failed junit tests :

   hadoop.fs.viewfs.TestViewFileSystemLocalFileSystem 
   hadoop.fs.viewfs.TestViewFileSystemWithAuthorityLocalFileSystem 
   hadoop.hdfs.TestEncryptionZones 
   hadoop.hdfs.TestReadStripedFileWithMissingBlocks 
   hadoop.hdfs.security.TestDelegationTokenForProxyUser 
   hadoop.hdfs.tools.offlineImageViewer.TestOfflineImageViewer 
   hadoop.hdfs.TestDFSRSDefault10x4StripedOutputStreamWithFailure 
   hadoop.hdfs.server.mover.TestStorageMover 
   hadoop.hdfs.TestDFSStripedOutputStreamWithFailure080 
   hadoop.hdfs.web.TestWebHdfsTimeouts 
   hadoop.yarn.server.timeline.TestRollingLevelDB 
   hadoop.yarn.server.timeline.TestTimelineDataManager 
   hadoop.yarn.server.timeline.TestLeveldbTimelineStore 
   hadoop.yarn.server.timeline.webapp.TestTimelineWebServices 
   hadoop.yarn.server.timeline.recovery.TestLeveldbTimelineStateStore 
   hadoop.yarn.server.timeline.TestRollingLevelDBTimelineStore 
   
hadoop.yarn.server.applicationhistoryservice.TestApplicationHistoryServer 
   hadoop.yarn.server.resourcemanager.TestRMEmbeddedElector 
   hadoop.yarn.server.resourcemanager.recovery.TestLeveldbRMStateStore 
   hadoop.yarn.server.resourcemanager.TestRMRestart 
   hadoop.yarn.server.TestMiniYarnClusterNodeUtilization 
   hadoop.yarn.server.TestContainerManagerSecurity 
   hadoop.yarn.client.TestApplicationMasterServiceProtocolOnHA 
   hadoop.yarn.server.timeline.TestLevelDBCacheTimelineStore 
   hadoop.yarn.server.timeline.TestOverrideTimelineStoreYarnClient 
   hadoop.yarn.server.timeline.TestEntityGroupFSTimelineStore 
   hadoop.yarn.applications.distributedshell.TestDistributedShell 
   hadoop.mapred.TestShuffleHandler 
   hadoop.mapreduce.v2.app.rm.TestRMCommunicator 
   hadoop.mapreduce.v2.app.TestMRAppComponentDependencies 
   hadoop.mapreduce.v2.app.launcher.TestContainerLauncher 
   hadoop.mapreduce.v2.hs.TestHistoryServerLeveldbStateStoreService 
   hadoop.mapreduce.v2.TestMRJobsWithProfiler 
   hadoop.hdfs.TestNNBench 
   hadoop.mapred.gridmix.TestResourceUsageEmulators 

Timed out junit tests :

   
org.apache.hadoop.hdfs.server.datanode.TestDataNodeVolumeFailureReporting 
   org.apache.hadoop.hdfs.server.datanode.TestFsDatasetCache 
   org.apache.hadoop.mapreduce.v2.TestUberAM 
   org.apache.hadoop.mapreduce.v2.TestMRJobs 
  

   compile:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/207/artifact/out/patch-compile-root.txt
  [120K]

   cc:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/207/artifact/out/patch-compile-root.txt
  [120K]

   javac:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/207/artifact/out/patch-compile-root.txt
  [120K]

   unit:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/207/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt
  [132K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/207/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
  [1.3M]
   

[jira] [Created] (YARN-6054) TimelineServer fails to start when some LevelDb state files are missing.

2017-01-04 Thread Ravi Prakash (JIRA)
Ravi Prakash created YARN-6054:
--

 Summary: TimelineServer fails to start when some LevelDb state 
files are missing.
 Key: YARN-6054
 URL: https://issues.apache.org/jira/browse/YARN-6054
 Project: Hadoop YARN
  Issue Type: Bug
Affects Versions: 3.0.0-alpha2
Reporter: Ravi Prakash


We encountered an issue recently where the TimelineServer failed to start 
because some state files went missing.

{code}
2016-11-21 20:46:43,134 INFO org.apache.hadoop.service.AbstractService: Service 
org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer
 failed in state INITED
; cause: org.apache.hadoop.service.ServiceStateException: 
org.fusesource.leveldbjni.internal.NativeDB$DBException: Corruption: 9 missing 
files; e.g.: /timelines
erver/leveldb-timeline-store.ldb/127897.sst
org.apache.hadoop.service.ServiceStateException: 
org.fusesource.leveldbjni.internal.NativeDB$DBException: Corruption: 9 missing 
files; e.g.: /timelineserver/lev
eldb-timeline-store.ldb/127897.sst

2016-11-21 20:46:43,135 FATAL 
org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer:
 Error starting ApplicationHistoryServer
org.apache.hadoop.service.ServiceStateException: 
org.fusesource.leveldbjni.internal.NativeDB$DBException: Corruption: 9 missing 
files; e.g.: 
/timelineserver/leveldb-timeline-store.ldb/127897.sst
at 
org.apache.hadoop.service.ServiceStateException.convert(ServiceStateException.java:59)
at 
org.apache.hadoop.service.AbstractService.init(AbstractService.java:172)
at 
org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
at 
org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:104)
at 
org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at 
org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:172)
at 
org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:182)
Caused by: org.fusesource.leveldbjni.internal.NativeDB$DBException: Corruption: 
9 missing files; e.g.: 
/timelineserver/leveldb-timeline-store.ldb/127897.sst
at 
org.fusesource.leveldbjni.internal.NativeDB.checkStatus(NativeDB.java:200)
at org.fusesource.leveldbjni.internal.NativeDB.open(NativeDB.java:218)
at org.fusesource.leveldbjni.JniDBFactory.open(JniDBFactory.java:168)
at 
org.apache.hadoop.yarn.server.timeline.LeveldbTimelineStore.serviceInit(LeveldbTimelineStore.java:229)
at 
org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
... 5 more
2016-11-21 20:46:43,136 INFO org.apache.hadoop.util.ExitUtil: Exiting with 
status -1
{code}
Ideally we shouldn't have any missing state files. However I'd posit that the 
TimelineServer should have graceful degradation instead of failing to start at 
all.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



Re: Planning for 3.0.0-alpha2

2017-01-04 Thread Andrew Wang
Hi folks,

Thanks to the hard work of many contributors, we've been steadily burning
down alpha2 blockers. There are only 4 remaining, three of which are PA and
likely to be committed shortly.

Once those three go in (hopefully this week), I'm going to cut the alpha2
branch and wait for that last blocker. Normal development activity can
continue on trunk and branch-2, and doesn't need to be committed to the
alpha2 branch.

Since we still have some significant code to wrap up (Tomcat->Jetty
conversion, EC work, rolling upgrade compatibility), it's likely there will
also be an alpha3 before we freeze for beta1. I've updated the Hadoop 3
wiki page [1] to reflect this.

Thanks,
Andrew

[1]: https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3.0.0+release

On Mon, Oct 17, 2016 at 1:57 PM, Andrew Wang 
wrote:

> Hi folks,
>
> It's been a month since 3.0.0-alpha1, and we've been incorporating fixes
> based on downstream feedback. Thus, it's getting to be time for
> 3.0.0-alpha2. I'm using this JIRA query to track open issues:
>
> https://issues.apache.org/jira/issues/?jql=project%20in%
> 20(HADOOP%2C%20HDFS%2C%20MAPREDUCE%2C%20YARN)%20AND%
> 20%22Target%20Version%2Fs%22%20in%20(3.0.0-alpha2%2C%203.0.
> 0-beta1%2C%202.8.0)%20AND%20statusCategory%20not%20in%
> 20(Complete)%20ORDER%20BY%20priority
>
> If alpha2 goes well, we can declare feature freeze, cut branch-3, and move
> onto beta1. My plan for the 3.0.0 release timeline looks like this:
>
> * alpha2 in early November
> * beta1 in early Jan
> * GA in early March
>
> I'd appreciate everyone's help in resolving blocker and critical issues on
> the above JIRA search.
>
> Thanks,
> Andrew
>


Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

2017-01-04 Thread Apache Jenkins Server
For more details, see 
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/276/

[Jan 3, 2017 1:49:29 PM] (brahma) Revert "HDFS-11280. Allow WebHDFS to reuse 
HTTP connections to NN.
[Jan 3, 2017 5:58:00 PM] (wang) HDFS-11156. Add new op GETFILEBLOCKLOCATIONS to 
WebHDFS REST API.
[Jan 3, 2017 8:13:32 PM] (rkanter) YARN-5529. Create new DiskValidator class 
with metrics (yufeigu via
[Jan 3, 2017 9:08:38 PM] (liuml07) HADOOP-13946. Document how HDFS updates 
timestamps in the FS spec;
[Jan 3, 2017 9:16:06 PM] (cnauroth) HADOOP-13922. Some modules have 
dependencies on hadoop-client jar
[Jan 3, 2017 10:44:26 PM] (liuml07) Revert "HADOOP-13946. Document how HDFS 
updates timestamps in the FS
[Jan 3, 2017 10:46:41 PM] (wangda) Fix synchronization issues of 
AbstractYarnScheduler#nodeUpdate and its
[Jan 3, 2017 10:53:13 PM] (wangda) Revert "Fix synchronization issues of 
AbstractYarnScheduler#nodeUpdate
[Jan 3, 2017 10:53:36 PM] (wangda) YARN-6025. Fix synchronization issues of
[Jan 3, 2017 11:03:38 PM] (jdu) YARN-5923. Unable to access logs for a running 
application if
[Jan 4, 2017 2:25:46 AM] (xyao) HDFS-11279. Cleanup unused 
DataNode#checkDiskErrorAsync(). Contributed
[Jan 4, 2017 5:10:36 AM] (aajisaka) HADOOP-12733. Remove references to obsolete 
io.seqfile configuration
[Jan 4, 2017 6:39:29 AM] (rohithsharmaks) YARN-5988. RM unable to start in 
secure setup. Contributed by Ajith S.




-1 overall


The following subsystems voted -1:
asflicense unit


The following subsystems voted -1 but
were configured to be filtered/ignored:
cc checkstyle javac javadoc pylint shellcheck shelldocs whitespace


The following subsystems are considered long running:
(runtime bigger than 1h  0m  0s)
unit


Specific tests:

Failed junit tests :

   hadoop.yarn.server.timeline.webapp.TestTimelineWebServices 
   hadoop.yarn.server.resourcemanager.TestRMRestart 
   hadoop.yarn.server.TestContainerManagerSecurity 
   hadoop.yarn.server.TestMiniYarnClusterNodeUtilization 
  

   cc:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/276/artifact/out/diff-compile-cc-root.txt
  [4.0K]

   javac:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/276/artifact/out/diff-compile-javac-root.txt
  [164K]

   checkstyle:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/276/artifact/out/diff-checkstyle-root.txt
  [16M]

   pylint:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/276/artifact/out/diff-patch-pylint.txt
  [20K]

   shellcheck:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/276/artifact/out/diff-patch-shellcheck.txt
  [28K]

   shelldocs:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/276/artifact/out/diff-patch-shelldocs.txt
  [16K]

   whitespace:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/276/artifact/out/whitespace-eol.txt
  [11M]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/276/artifact/out/whitespace-tabs.txt
  [1.3M]

   javadoc:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/276/artifact/out/diff-javadoc-javadoc-root.txt
  [2.2M]

   unit:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/276/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-applicationhistoryservice.txt
  [12K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/276/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
  [56K]
   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/276/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-tests.txt
  [324K]

   asflicense:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/276/artifact/out/patch-asflicense-problems.txt
  [4.0K]

Powered by Apache Yetus 0.5.0-SNAPSHOT   http://yetus.apache.org



-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org

[jira] [Created] (YARN-6053) RM Web Service shows startedTime , finsihedTime as zero when RM is kerberized and ACL is setup

2017-01-04 Thread Prabhu Joseph (JIRA)
Prabhu Joseph created YARN-6053:
---

 Summary: RM Web Service shows startedTime , finsihedTime as zero 
when RM is kerberized and ACL is setup
 Key: YARN-6053
 URL: https://issues.apache.org/jira/browse/YARN-6053
 Project: Hadoop YARN
  Issue Type: Bug
Affects Versions: 2.7.3
Reporter: Prabhu Joseph
Priority: Minor


RM UI is Kerberized and ACL is setup, a user pjoseph has logged into RM UI and 
able to see the other user prabhu job’s startTime and finishTime but won’t be 
able to read the attempts of the application which is expected as ACL is setup. 
But on using RM Web Services, 
http://kerberos-3.openstacklocal:8088/ws/v1/cluster/apps/application_1482325548661_0002
 the startedTime,
finishedTime and elapsedTime are 0 [AppInfo.java sets this to zero if user does 
not have access]. We can display the correct values as anyway RM UI shows them.

Attached output of RM UI and RM WebService.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



[jira] [Created] (YARN-6052) Yarn RM UI % of Queue at application level is wrong

2017-01-04 Thread Prabhu Joseph (JIRA)
Prabhu Joseph created YARN-6052:
---

 Summary: Yarn RM UI % of Queue at application level is wrong
 Key: YARN-6052
 URL: https://issues.apache.org/jira/browse/YARN-6052
 Project: Hadoop YARN
  Issue Type: Bug
Affects Versions: 2.7.3
Reporter: Prabhu Joseph
Priority: Minor


Test Case:

yarn.scheduler.capacity.root.capacity=100
yarn.scheduler.capacity.root.queues=default,dummy
yarn.scheduler.capacity.root.default.capacity=20
yarn.scheduler.capacity.root.dummy.capacity=80
yarn.scheduler.capacity.root.dummy.child.capacity=50
yarn.scheduler.capacity.root.dummy.child2.capacity=50

Memory Total is 20GB, default queue share is 4GB and dummy queue share is 16GB. 
Child and Child1 queue gets 8GB share each.

A map reduce job is submitted  to child2 queue which asks 2 containers of 512 
MB. Now cluster Memory Used is 1GB.

Root queue usage = 100 / (total memory / used memory)  = 100 / (20 / 1) =  5%
Dummy queue usage = 100 / (16 /1) = 6.3%
Dummy.Child2 queue usage = 100 / (8/1) = 12.5%

At application level, % of queue is calculated as 100 / (50% of root queue 
capacity) = 100 / (50% of 20GB) = 10.0 instead of 
100 / (50% of dummy queue capacity) = 100 / (50% of 16GB) = 100 / 8 = 12.5

Where 50% is dummy.child2 capacity

Attached RM UI screenshot.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org



Re: [Continued] [Release thread] 2.8.0 release activities

2017-01-04 Thread Junping Du
Hi all Hadoopers,
 I just commit YARN-3866 which is the last blocker for branch-2.8, so since 
tomorrow I will kick off process to prepare the first RC for our 2.8.0 release. 
This release will include at least 2374 commits that never landed before in 
previous 2.x releases. Please check https://s.apache.org/RW5k for details. 
There are also 352 fixes marked in 2.7.1, 2.7.2 and 2.7.3 but not marked with 
2.8 (https://s.apache.org/RKti) that I need to double check all are landed in 
branch-2.8 and fix the versions before kicking off the first RC.
 Our progress is slightly behind my estimation weeks ago. However, 
considering we just go through holidays and Jenkins cleanup issues linger on 
for several projects (YARN, etc.), our achievement here is still great! Thanks 
everyone for keep calm and carry on the help for the release. Kudos to Wangda, 
Jian, Akira, Jason, Sangjin, Karthik and all for pushing hard on blockers 
during this time. Also, special thanks to Vinod and Andrew for sharing 
knowledge and practice (include scripts for auto version check) for releasing 
effort.
 Will try to prepare RC0 of 2.8 release for vote within this week. Stay 
tuned!

Thanks,

Junping


From: Junping Du 
Sent: Wednesday, December 07, 2016 11:31 AM
To: Akira Ajisaka; common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-dev@hadoop.apache.org
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

Thanks Akira for reporting this. Actually, HADOOP-2.8-JACC worked well for 
several runs before last weekend, but it get failed for latest several runs, 
probably affected by recently Jenkins down.
However, from my recent manual kick off, it seems to be good again: 
https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-2.8-JACC/9/. I will 
keep an eye for today's nightly run to see if it back to normal.


Thanks,

Junping


From: Akira Ajisaka 
Sent: Wednesday, December 07, 2016 12:12 AM
To: common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-dev@hadoop.apache.org
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

Thanks Junping and Andrew!

HADOOP-2.8-JACC is not working well, so I manually kicked a job to
compare 2.8 with 2.7.3.

https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-trunk-JACC/24/artifact/target/compat-check/report.html

Regards,
Akira

On 2016/12/02 2:08, Junping Du wrote:
> Thanks Andrew! That's also a nice suggestion. I already create a similar job: 
> https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-2.8-JACC/ for 2.8 
> and kick off several runs manually. Will monitor incompatible status from 
> there.
>
>
> Thanks,
>
>
> Junping
>
>
> 
> From: Andrew Wang 
> Sent: Wednesday, November 30, 2016 4:18 PM
> To: Junping Du
> Cc: Sangjin Lee; common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org; 
> mapreduce-...@hadoop.apache.org; yarn-dev@hadoop.apache.org; Vinod 
> Vavilapalli; Jian He; Wangda Tan; sj...@twitter.com
> Subject: Re: [Continued] [Release thread] 2.8.0 release activities
>
> I recommend giving the JACC report another look. I set up a parameterized 
> jenkins job which you can trigger manually for branch-2.8:
>
> https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-trunk-JACC/
>
> On Wed, Nov 30, 2016 at 4:06 PM, Junping Du 
> > wrote:
> Hi Sangjin and all,
>
>  That sounds good. If anyone have priority fix to backport , please 
> nominate it by following this email thread or ping me on JIRA directly. And I 
> agree that we should keep in mind that our bar for 2.8 release should be high 
> now as we want to move quickly on this release. Non-critical fixes can wait 
> for next one.
>
>   Any other comments and suggestions?
>
>
> Thanks,
>
>
> Junping
>
>
> 
> From: sjl...@gmail.com 
> > on behalf of Sangjin Lee 
> >
> Sent: Wednesday, November 30, 2016 3:24 PM
> To: Junping Du
> Cc: common-...@hadoop.apache.org; 
> hdfs-...@hadoop.apache.org; 
> mapreduce-...@hadoop.apache.org; 
> yarn-dev@hadoop.apache.org; Vinod 
> Vavilapalli; Jian He; Wangda Tan; sj...@twitter.com
> Subject: Re: [Continued] [Release thread] 2.8.0 release activities
>
> Thanks for picking this up Junping!
>
> I heard on email threads and offline discussions that there may be interests 
> in porting some fixes from branch-2 to branch-2.8. I still feel that the bar 
> should be pretty high to do that, but it might be good to have folks