> On Oct 6, 2016, at 1:39 PM, Akira Ajisaka wrote:
>
> > It wasn't 'renamed' to jenkins, prior releases were actually built by and
> > on the Jenkins infrastructure. Which was a very very bad idea: it's
> > insecure and pretty much against ASF policy.
>
> Sorry for the confusion. I should no
[
https://issues.apache.org/jira/browse/HDFS-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brahma Reddy Battula resolved HDFS-3908.
Resolution: Won't Fix
Closing as wn't fix as per discussion
[here|http://mail-archiv
[
https://issues.apache.org/jira/browse/HDFS-4613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brahma Reddy Battula resolved HDFS-4613.
Resolution: Won't Fix
Closing as wn't fix as per discussion
[here|http://mail-archiv
[
https://issues.apache.org/jira/browse/HDFS-10973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brahma Reddy Battula resolved HDFS-10973.
-
Resolution: Duplicate
[~xiaobingo] resolving as duplicate of HDFS-10972..Please fe
Zhe Zhang created HDFS-10977:
Summary: Balancer should query NameNode with a timeout
Key: HDFS-10977
URL: https://issues.apache.org/jira/browse/HDFS-10977
Project: Hadoop HDFS
Issue Type: Bug
Wei-Chiu Chuang created HDFS-10976:
--
Summary: Fsck should mark EC files explicitly
Key: HDFS-10976
URL: https://issues.apache.org/jira/browse/HDFS-10976
Project: Hadoop HDFS
Issue Type: Sub-
I think it's a good idea. We can still have the underlying data (in
*-version.properties) but we can consider removing the date and the build
person from the web UI. I'll file a JIRA to consider the idea.
I would greatly appreciate it if you folks can take a little time to take
the RC1 for a spin
I don't think it's a blocker, though I wonder what the point of that date
and attribution are on the WebUI.
Maybe file a follow-on JIRA to remove it for the future?
On Thu, Oct 6, 2016 at 3:09 PM, Sangjin Lee wrote:
> I looked into building it on jenkins earlier, but it appears that this
> jenk
I looked into building it on jenkins earlier, but it appears that this
jenkins job is busted (at least for 2.6.x):
https://builds.apache.org/job/HADOOP2_Release_Artifacts_Builder/
I don't have access to the job configuration, so I'm unable to fix it atm.
That said, I do think Allen has a point. I
Wei-Chiu Chuang created HDFS-10975:
--
Summary: fsck -list-corruptfileblocks does not report corrupt EC
files
Key: HDFS-10975
URL: https://issues.apache.org/jira/browse/HDFS-10975
Project: Hadoop HDFS
> It wasn't 'renamed' to jenkins, prior releases were actually built by
and on the Jenkins infrastructure. Which was a very very bad idea: it's
insecure and pretty much against ASF policy.
Sorry for the confusion. I should not have used the word 'rename'.
What I meant is that "would you change
Wei-Chiu Chuang created HDFS-10974:
--
Summary: Document replication factor for EC files.
Key: HDFS-10974
URL: https://issues.apache.org/jira/browse/HDFS-10974
Project: Hadoop HDFS
Issue Type:
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/116/
[Oct 5, 2016 2:02:11 PM] (stevel) HADOOP-12667 s3a to support
createNonRecursive API. Contributed by Sean
[Oct 5, 2016 5:52:50 PM] (jing9) HDFS-10826. Correctly report missing EC blocks
in FSCK. Contribute
+1 ( non- binding)
--Downloaded source and built from it.
--Installed 3 node cluster with HA deployed.
—Ran sample MR jobs and tested with basics operations.
— Integrated JCarder tool to find any potential deadlock cycles. And did not
observe any potential cycles.
Thanks & Regards
Rohith Sharm
Xiaobing Zhou created HDFS-10972:
Summary: Add unit test for HDFS command 'dfsadmin -getDatanodeInfo'
Key: HDFS-10972
URL: https://issues.apache.org/jira/browse/HDFS-10972
Project: Hadoop HDFS
Xiaobing Zhou created HDFS-10973:
Summary: Add unit test for HDFS command 'dfsadmin -getDatanodeInfo'
Key: HDFS-10973
URL: https://issues.apache.org/jira/browse/HDFS-10973
Project: Hadoop HDFS
Wei-Chiu Chuang created HDFS-10971:
--
Summary: Distcp should not copy replication factor if source file
is erasure coded
Key: HDFS-10971
URL: https://issues.apache.org/jira/browse/HDFS-10971
Project:
> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka wrote:
> Can we rename it?
>
> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed to
> jenkins.
That's not how that works.
It's literally storing the id of the person who built the classes. It
wasn't 'renamed' t
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/186/
[Oct 5, 2016 10:01:38 AM] (vvasudev) YARN-5704. Provide config knobs to control
enabling/disabling new/work
[Oct 5, 2016 11:41:08 AM] (aajisaka) HADOOP-13685. Document -safely option of
rm command. Contrib
Hi All , Recently we have upgraded our Cluster to Hadoop 2.7.1 version.
When i try to run Mover , it throws below exception :
2016-10-06 00:24:44,643 INFO
org.apache.hadoop.hdfs.server.datanode.DataNode: opCopyBlock
BP-1267816582-10.114.118.11-1392844883031:blk_12046985669_160995799
recei
20 matches
Mail list logo
