[jira] [Resolved] (HDFS-1374) TestBlockRecovery#testZeroLenReplicas fails

[ https://issues.apache.org/jira/browse/HDFS-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko resolved HDFS-1374. --- Resolution: Not A Problem Assignee: Eli Collins > TestBlockRecovery#testZero

[jira] [Reopened] (HDFS-1374) TestBlockRecovery#testZeroLenReplicas fails

[ https://issues.apache.org/jira/browse/HDFS-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko reopened HDFS-1374: --- Reopening to change resolution. > TestBlockRecovery#testZeroLenReplicas f

RE: Blocks are getting corrupted under very high load

Hi Todd, Thanks a lot for taking a look. Yes, I also suspect the same initially. But after analysing the logs, we found below client trace logs in DN, which means block finalization completed. ./hadoop-root-datanode-xx-xx-132-22.log.1:2011-11-20 18:18:45,498 INFO DataNode.clienttrace (BlockRec

Re: Blocks are getting corrupted under very high load

Can you look on the DN in question and see whether it was succesfully finalized when the write finished? It doesn't sound like a successful write -- should have moved it out of the bbw directory into current/ -Todd On Tue, Nov 22, 2011 at 3:16 AM, Uma Maheswara Rao G wrote: > Hi All, > > > > I h

Hadoop-Hdfs-trunk-Commit - Build # 1389 - Failure

See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/1389/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 8900 lines...] 2536 KB 2540 KB 2544 KB 25

[jira] [Reopened] (HDFS-2257) HftpFileSystem should implement getDelegationTokens

[ https://issues.apache.org/jira/browse/HDFS-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth reopened HDFS-2257: -- {{getDelegationToken}} was deprecated in favor of {{getDelegationTokens}} - likely along with the i

[jira] [Created] (HDFS-2587) Add WebHDFS apt doc

Add WebHDFS apt doc --- Key: HDFS-2587 URL: https://issues.apache.org/jira/browse/HDFS-2587 Project: Hadoop HDFS Issue Type: Task Components: documentation Reporter: Tsz Wo (Nicholas), SZE As

[jira] [Resolved] (HDFS-2552) Add WebHdfs Forrest doc

[ https://issues.apache.org/jira/browse/HDFS-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE resolved HDFS-2552. -- Resolution: Fixed Hi Alejandro, Since URL query is case sensitive by default, w

[jira] [Reopened] (HDFS-2552) Add WebHdfs Forrest doc

[ https://issues.apache.org/jira/browse/HDFS-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur reopened HDFS-2552: -- Nicholas, the issue about spec-ing case sensitivity of param names and values in the query

[jira] [Resolved] (HDFS-2552) Add WebHdfs Forrest doc

[ https://issues.apache.org/jira/browse/HDFS-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE resolved HDFS-2552. -- Resolution: Fixed Fix Version/s: 0.23.1 0.24.0

[jira] [Created] (HDFS-2586) Add protobuf service and implementation for HAServiceProtocol

Add protobuf service and implementation for HAServiceProtocol - Key: HDFS-2586 URL: https://issues.apache.org/jira/browse/HDFS-2586 Project: Hadoop HDFS Issue Type: Sub-task

[jira] [Created] (HDFS-2585) dfs.https.port is a bit confusing

dfs.https.port is a bit confusing - Key: HDFS-2585 URL: https://issues.apache.org/jira/browse/HDFS-2585 Project: Hadoop HDFS Issue Type: Improvement Affects Versions: 0.23.0 Reporter: Joe Croba

[jira] [Resolved] (HDFS-298) BlockSender and BlockReceiver should be refactored into separate classes

[ https://issues.apache.org/jira/browse/HDFS-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-298. -- Resolution: Not A Problem This seems to have already been done long ago. We have separated classes today for the

[jira] [Resolved] (HDFS-72) IOException at task startup "No valid local directories in property: dfs.client.buffer.dir"

[ https://issues.apache.org/jira/browse/HDFS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-72. - Resolution: Not A Problem This appears to have been long resolved after we changed the way we did writes.

Jenkins build is unstable: Hadoop-Hdfs-trunk #871

See

Hadoop-Hdfs-trunk - Build # 871 - Still unstable

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/871/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 10608 lines...] [INFO] Building Apache Hadoop HDFS Project

Hadoop-Hdfs-0.23-Build - Build # 84 - Still Unstable

See https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/84/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 12061 lines...] [INFO] ---

Jenkins build is still unstable: Hadoop-Hdfs-0.23-Build #84

See

RE: What does hdfs balancer do after adding more disks to existing datanode.

Hi, Current volume choosing policy is round robin fashion, Since the DN got new disk, balancer will balance some blocks to this node. But the volume choosing will be same when palcing the block. AFAIK, it wont do any special balancing between disks in the same node. please correct me if i under

Blocks are getting corrupted under very high load

Hi All, I have backported HDFS-1779 to our Hadoop version which is based on 0.20-Append branch. We are running a load test, as usual. (We want to ensure the reliability of the system under heavy loads.) My cluster has 8 DataNodes and a Namenode Each machine has 16 CPUs and 12 hard disks, each

[jira] [Resolved] (HDFS-2557) Naming convention for files being moved into HDFS

[ https://issues.apache.org/jira/browse/HDFS-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-2557. --- Resolution: Duplicate > Naming convention for files being moved into HDFS > --