I¹m pretty sure there is no guarantee of isolation on a shared
.m2/repository directory for multiple concurrent Maven processes. I¹ve
had a theory for a while that one build running ³mvm install² can
overwrite the snapshot artifact that was just installed by another
concurrent build. This can
Biju Nair created HDFS-7810:
---
Summary: Datanode registration process fails in hadoop 2.6
Key: HDFS-7810
URL: https://issues.apache.org/jira/browse/HDFS-7810
Project: Hadoop HDFS
Issue Type: Bug
Rakesh R created HDFS-7813:
--
Summary: TestDFSHAAdminMiniCluster#testFencer testcase is failing
ferquently
Key: HDFS-7813
URL: https://issues.apache.org/jira/browse/HDFS-7813
Project: Hadoop HDFS
Hmm. I guess my thought would be that we would have a fixed number of
slots (i.e. executors on a single node with associated .m2
directories). Then we wouldn't clear each .m2 in between runs, but we
would ensure that only one slot at a time had access to each
directory.
In that case, build
See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/99/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 7017 lines...]
[INFO] ---
Kihwal Lee created HDFS-7809:
Summary: Block and lease recovery failure caused by snapshot issue
Key: HDFS-7809
URL: https://issues.apache.org/jira/browse/HDFS-7809
Project: Hadoop HDFS
Issue
Akira AJISAKA created HDFS-7812:
---
Summary: Remove httpclient dependency from hadoop-hdfs
Key: HDFS-7812
URL: https://issues.apache.org/jira/browse/HDFS-7812
Project: Hadoop HDFS
Issue Type:
