xluren created HADOOP-13788:
---
Summary: datatransfer.Receiver.processOp error
Key: HADOOP-13788
URL: https://issues.apache.org/jira/browse/HADOOP-13788
Project: Hadoop Common
Issue Type: Bug
John Zhuge created HADOOP-13787:
---
Summary: testGlobStatusThrowsExceptionForUnreadableDir failed
Key: HADOOP-13787
URL: https://issues.apache.org/jira/browse/HADOOP-13787
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-13717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wang resolved HADOOP-13717.
--
Resolution: Invalid
Fix Version/s: (was: 3.0.0-alpha2)
Reverted and reclosing, than
[
https://issues.apache.org/jira/browse/HADOOP-13717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wang reopened HADOOP-13717:
--
> Normalize daemonization behavior of the diskbalancer with balancer and mover
> -
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/143/
[Nov 1, 2016 4:02:52 PM] (brahma) HDFS-10499.
TestNameNodeMetadataConsistency#testGenerationStampInFuture
[Nov 1, 2016 6:14:03 PM] (aengineer) HDFS-10633. DiskBalancer : Add the
description for the new set
[
https://issues.apache.org/jira/browse/HADOOP-13712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved HADOOP-13712.
-
Resolution: Won't Fix
> S3A open to avoid needless HEAD on the successful execution path
Steve Loughran created HADOOP-13786:
---
Summary: add output committer which uses s3guard for consistent
O(1) commits to S3
Key: HADOOP-13786
URL: https://issues.apache.org/jira/browse/HADOOP-13786
Pro
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/213/
[Nov 1, 2016 9:21:31 AM] (varunsaxena) YARN-5805. Add isDebugEnabled check for
debug logs in nodemanager (Bibin
[Nov 1, 2016 10:02:04 AM] (varunsaxena) YARN-5788. Apps not activiated and AM
limit resource
I do kind of concur, but also think we need to consider whether its time to
increase the jackson 2.x version ( HADOOP-12705 ).
Whether we do or don't, there will be classpath conflicts with downstream apps
(hello HBase! Hello Spark!) —but we get them already.
All that staying on an older one is
