[jira] [Created] (HDFS-6499) can't tell why FileJournalManager's call to java.io.File.renameTo() fails

Yongjun Zhang created HDFS-6499: --- Summary: can't tell why FileJournalManager's call to java.io.File.renameTo() fails Key: HDFS-6499 URL: https://issues.apache.org/jira/browse/HDFS-6499 Project: Hadoop H

[jira] [Created] (HDFS-6498) Support squash and range in NFS static user id mapping

Brandon Li created HDFS-6498: Summary: Support squash and range in NFS static user id mapping Key: HDFS-6498 URL: https://issues.apache.org/jira/browse/HDFS-6498 Project: Hadoop HDFS Issue Type:

[jira] [Created] (HDFS-6497) Make TestAvailableSpaceVolumeChoosingPolicy deterministic

Colin Patrick McCabe created HDFS-6497: -- Summary: Make TestAvailableSpaceVolumeChoosingPolicy deterministic Key: HDFS-6497 URL: https://issues.apache.org/jira/browse/HDFS-6497 Project: Hadoop HDFS

Re: hedged read bug

Hello Lei, There is a known bug in 2.4.0 that can cause hedged reads to hang. I fixed it in HDFS-6231: https://issues.apache.org/jira/browse/HDFS-6231 This patch will be included in the forthcoming 2.4.1 release. I'm curious to see if applying this patch fixes the problem for you. Can you try

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

See Changes: [umamahesh] HDFS-6464. Support multiple xattr.name parameters for WebHDFS getXAttrs. Contributed by Yi Liu. [cmccabe] HDFS-6369. Document that BlockReader#available() can return more bytes than are remaining in the blo

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

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1766/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 13037 lines...] [INFO] --- maven-antrun-plugin:1.7:run (c

Re: Compatibility Yarn 2.4 with HDFS 2.0

Also I tested using hdfs client 2.0 access hdfs server 2.4, this also got no compatibility: "Incorrect header or version mismatch from 10.2.201.245:59310 got version 7 expected version 9" Does this mean if we update our production cluster from 2.0 to 2.4, all clients must be re-build? Any suggest

Re: Compatibility Yarn 2.4 with HDFS 2.0

You mean YARN will call some interfaces of FileSystem that not existed in 2.0? Because I think YARN and MR depend on FileSystem interface of hadoop-common. I want to hack as below: ---> HDFS 2.0 > Hadoop-common 2.0 / YARN and MR

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

Fengdong Yu created HDFS-6496: - Summary: WebHDFS cannot open file Key: HDFS-6496 URL: https://issues.apache.org/jira/browse/HDFS-6496 Project: Hadoop HDFS Issue Type: Bug Components: na

[jira] [Resolved] (HDFS-6495) In some case, the hedged read will lead to client infinite wait.

[ https://issues.apache.org/jira/browse/HDFS-6495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fengdong Yu resolved HDFS-6495. --- Resolution: Duplicate Duplicate with HDFS-6494 > In some case, the hedged read will lead to client

Re: Compatibility Yarn 2.4 with HDFS 2.0

Even if you done this, it's unstable, because Yarn2.4 added some IPC interfaces. then HDFS MUST has related interfaces. On Fri, Jun 6, 2014 at 4:22 PM, 张鹏 wrote: > Hi all, > > I want to upgrade to Yarn 2.4 only. But when it access Hdfs, IPC Server > version is mismached. > > HDFS (IPC v7) cant

[jira] [Created] (HDFS-6495) In some case, the hedged read will lead to client infinite wait.

LiuLei created HDFS-6495: Summary: In some case, the hedged read will lead to client infinite wait. Key: HDFS-6495 URL: https://issues.apache.org/jira/browse/HDFS-6495 Project: Hadoop HDFS Issue T

[jira] [Created] (HDFS-6494) In some case, the hedged read will lead to client infinite wait.

LiuLei created HDFS-6494: Summary: In some case, the hedged read will lead to client infinite wait. Key: HDFS-6494 URL: https://issues.apache.org/jira/browse/HDFS-6494 Project: Hadoop HDFS Issue T

Compatibility Yarn 2.4 with HDFS 2.0

Hi all, I want to upgrade to Yarn 2.4 only. But when it access Hdfs, IPC Server version is mismached. HDFS (IPC v7) cant respond to YARN (IPC v9) with below error log: WARN org.apache.hadoop.ipc.Server: Incorrect header or version mismatch from 127.0.0.1:47957 got version 9 expected version 7