[jira] [Reopened] (HDFS-7915) The DataNode can sometimes allocate a ShortCircuitShm slot and fail to tell the DFSClient about it because of a network error

[ https://issues.apache.org/jira/browse/HDFS-7915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe reopened HDFS-7915: oops, I just saw that jenkins didn't run on v6 yet. sigh... > The DataNode can sometime

[jira] [Resolved] (HDFS-6118) Code cleanup

[ https://issues.apache.org/jira/browse/HDFS-6118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haohui Mai resolved HDFS-6118. -- Resolution: Fixed > Code cleanup > > > Key: HDFS-6118 > URL:

[jira] [Resolved] (HDFS-6496) WebHDFS cannot open file

[ https://issues.apache.org/jira/browse/HDFS-6496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haohui Mai resolved HDFS-6496. -- Resolution: Invalid > WebHDFS cannot open file > > > Key: HDFS-6

[jira] [Resolved] (HDFS-7050) Implementation of NameNodeMXBean.getLiveNodes() skips DataNodes started on the same host

[ https://issues.apache.org/jira/browse/HDFS-7050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haohui Mai resolved HDFS-7050. -- Resolution: Duplicate Fixed in HDFS-7303 > Implementation of NameNodeMXBean.getLiveNodes() skips DataNod

[jira] [Resolved] (HDFS-7191) WebHDFS prematurely closes connections under high concurrent loads

[ https://issues.apache.org/jira/browse/HDFS-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haohui Mai resolved HDFS-7191. -- Resolution: Duplicate HDFS-7279 should fix this problem. > WebHDFS prematurely closes connections under

[jira] [Resolved] (HDFS-5193) Unifying HA support in HftpFileSystem, HsftpFileSystem and WebHdfsFileSystem

[ https://issues.apache.org/jira/browse/HDFS-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haohui Mai resolved HDFS-5193. -- Resolution: Won't Fix As hftp is phasing out there are few motivations to get this fixed. > Unifying HA

[jira] [Resolved] (HDFS-1841) Enforce read-only permissions in FUSE open()

[ https://issues.apache.org/jira/browse/HDFS-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe resolved HDFS-1841. Resolution: Duplicate duplicate of HDFS-4139 from 2012 > Enforce read-only permissio

[jira] [Created] (HDFS-7933) fsck should also report decommissioning replicas.

Jitendra Nath Pandey created HDFS-7933: -- Summary: fsck should also report decommissioning replicas. Key: HDFS-7933 URL: https://issues.apache.org/jira/browse/HDFS-7933 Project: Hadoop HDFS

[jira] [Created] (HDFS-7932) Speed up the shutdown of datanode during rolling upgrade

Kihwal Lee created HDFS-7932: Summary: Speed up the shutdown of datanode during rolling upgrade Key: HDFS-7932 URL: https://issues.apache.org/jira/browse/HDFS-7932 Project: Hadoop HDFS Issue Type

Re: upstream jenkins build broken?

I filed HDFS-7917 to change the way to simulate disk failures. But I think we still need infrastructure folks to help with jenkins scripts to clean the dirs left today. On Fri, Mar 13, 2015 at 1:38 PM, Mai Haohui wrote: > Any updates on this issues? It seems that all HDFS jenkins builds are > st

Re: upstream jenkins build broken?

Any updates on this issues? It seems that all HDFS jenkins builds are still failing. Regards, Haohui On Thu, Mar 12, 2015 at 12:53 AM, Vinayakumar B wrote: > I think the problem started from here. > > https://builds.apache.org/job/PreCommit-HDFS-Build/9828/testReport/junit/org.apache.hadoop.hdfs

[jira] [Created] (HDFS-7931) Spurious Error message "Could not find uri with key [dfs.encryption.key.provider.uri] to create a key" appears even when Encryption is dissabled

Arun Suresh created HDFS-7931: - Summary: Spurious Error message "Could not find uri with key [dfs.encryption.key.provider.uri] to create a key" appears even when Encryption is dissabled Key: HDFS-7931 URL: https://is

[jira] [Created] (HDFS-7930) commitBlockSynchronization() does not remove locations, which were not confirmed

Konstantin Shvachko created HDFS-7930: - Summary: commitBlockSynchronization() does not remove locations, which were not confirmed Key: HDFS-7930 URL: https://issues.apache.org/jira/browse/HDFS-7930

[jira] [Created] (HDFS-7929) inotify unable fetch pre-upgrade edit log segments once upgrade starts

Zhe Zhang created HDFS-7929: --- Summary: inotify unable fetch pre-upgrade edit log segments once upgrade starts Key: HDFS-7929 URL: https://issues.apache.org/jira/browse/HDFS-7929 Project: Hadoop HDFS

Build failed in Jenkins: Hadoop-Hdfs-trunk #2063

See Changes: [xgong] YARN-3338. Exclude jline dependency from YARN. Contributed by Zhijie [szetszwo] HDFS-6833. DirectoryScanner should not register a deleting block with memory of DataNode. Contributed by Shinichi Yamashita [cmc

Build failed in Jenkins: Hadoop-Hdfs-trunk-Java8 #122

See Changes: [xgong] YARN-3338. Exclude jline dependency from YARN. Contributed by Zhijie [szetszwo] HDFS-6833. DirectoryScanner should not register a deleting block with memory of DataNode. Contributed by Shinichi Yamashita

Hadoop-Hdfs-trunk-Java8 - Build # 122 - Still Failing

See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/122/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 8427 lines...] main: [mkdir] Created dir: /hom

Hadoop-Hdfs-trunk - Build # 2063 - Still Failing

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/2063/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 7563 lines...] main: [mkdir] Created dir: /home/jen

[jira] [Created] (HDFS-7928) Scanning blocks from disk during rolling upgrade startup takes a lot of time if disks are busy

Rushabh S Shah created HDFS-7928: Summary: Scanning blocks from disk during rolling upgrade startup takes a lot of time if disks are busy Key: HDFS-7928 URL: https://issues.apache.org/jira/browse/HDFS-7928

Re: How the ack sent back to upstream of a pipeline when write data to HDFS

On 3/13/2015 7:55 AM, xiaohe lan wrote: Hi experts, When HDFS client sends a packet of data to a DN in the pipeline, the packet will then be sent to the next DN in the pipeline. What confuses me is when the ack from a DN in the pipeline will be sent back ? In which order ? It is sent from the la

How the ack sent back to upstream of a pipeline when write data to HDFS

Hi experts, When HDFS client sends a packet of data to a DN in the pipeline, the packet will then be sent to the next DN in the pipeline. What confuses me is when the ack from a DN in the pipeline will be sent back ? In which order ? It is sent from the last to first or in other ways ? Thanks, Xi

[jira] [Created] (HDFS-7927) Fluentd unable to write events to MaprFS using httpfs

Roman Slysh created HDFS-7927: - Summary: Fluentd unable to write events to MaprFS using httpfs Key: HDFS-7927 URL: https://issues.apache.org/jira/browse/HDFS-7927 Project: Hadoop HDFS Issue Type: