[jira] Commented: (HDFS-611) Heartbeats times from Datanodes increase when there are plenty of blocks to delete

2009-11-08 Thread dhruba borthakur (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774751#action_12774751
 ] 

dhruba borthakur commented on HDFS-611:
---

I was able to recreate the test failure with TestBlockReport... not sure yet on 
whether this test failure is because of this patch or not.

> Heartbeats times from Datanodes increase when there are plenty of blocks to 
> delete
> --
>
> Key: HDFS-611
> URL: https://issues.apache.org/jira/browse/HDFS-611
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: data-node
>Affects Versions: 0.20.1, 0.21.0, 0.22.0
>Reporter: dhruba borthakur
>Assignee: Zheng Shao
> Fix For: 0.20.2, 0.21.0, 0.22.0
>
> Attachments: HDFS-611.branch-19.patch, HDFS-611.branch-19.v2.patch, 
> HDFS-611.branch-20.patch, HDFS-611.branch-20.v2.patch, HDFS-611.trunk.patch, 
> HDFS-611.trunk.v2.patch, HDFS-611.trunk.v3.patch, HDFS-611.trunk.v4.patch, 
> HDFS-611.trunk.v5.patch, HDFS-611.trunk.v6.patch
>
>
> I am seeing that when we delete a large directory that has plenty of blocks, 
> the heartbeat times from datanodes increase significantly from the normal 
> value of 3 seconds to as large as 50 seconds or so. The heartbeat thread in 
> the Datanode deletes a bunch of blocks sequentially, this causes the 
> heartbeat times to increase.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (HDFS-245) Create symbolic links in HDFS

2009-11-08 Thread Eli Collins (JIRA)

 [ 
https://issues.apache.org/jira/browse/HDFS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eli Collins updated HDFS-245:
-

Attachment: symlink22-hdfs.patch
symlink22-common.patch

Uploaded patches per the last comment that incorporate Doug's review and minor 
fixes like getting the offline image viewer test to work with symlinks. Also 
verified that hdfs oiv using a fsimage with symlinks look OK. 

> Create symbolic links in HDFS
> -
>
> Key: HDFS-245
> URL: https://issues.apache.org/jira/browse/HDFS-245
> Project: Hadoop HDFS
>  Issue Type: New Feature
>Reporter: dhruba borthakur
>Assignee: dhruba borthakur
> Attachments: 4044_20081030spi.java, designdocv1.txt, designdocv2.txt, 
> HADOOP-4044-strawman.patch, symlink-0.20.0.patch, symLink1.patch, 
> symLink1.patch, symLink11.patch, symLink12.patch, symLink13.patch, 
> symLink14.patch, symLink15.txt, symLink15.txt, symlink16-common.patch, 
> symlink16-hdfs.patch, symlink16-mr.patch, symlink17-common.txt, 
> symlink17-hdfs.txt, symlink18-common.txt, symlink19-common-delta.patch, 
> symlink19-common.txt, symlink19-common.txt, symlink19-hdfs-delta.patch, 
> symlink19-hdfs.txt, symlink20-common.patch, symlink20-hdfs.patch, 
> symlink21-common.patch, symlink21-hdfs.patch, symlink22-common.patch, 
> symlink22-hdfs.patch, symLink4.patch, symLink5.patch, symLink6.patch, 
> symLink8.patch, symLink9.patch
>
>
> HDFS should support symbolic links. A symbolic link is a special type of file 
> that contains a reference to another file or directory in the form of an 
> absolute or relative path and that affects pathname resolution. Programs 
> which read or write to files named by a symbolic link will behave as if 
> operating directly on the target file. However, archiving utilities can 
> handle symbolic links specially and manipulate them directly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (HDFS-712) Move libhdfs from mr to hdfs

2009-11-08 Thread dhruba borthakur (JIRA)

 [ 
https://issues.apache.org/jira/browse/HDFS-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

dhruba borthakur updated HDFS-712:
--

   Resolution: Fixed
Fix Version/s: 0.22.0
 Release Note: Moved the libhdfs package to the HDFS subproject.
   Status: Resolved  (was: Patch Available)

I did not use the patch file attached to this JIRA because I wanted to preserve 
the svn history of these files. Instead, I moved the libhdfs code by doing a 
"svn move". The libhdfs code i now part of the HDFS subproject. I can build it 
for a 64 bit rel

> Move libhdfs from mr to hdfs 
> -
>
> Key: HDFS-712
> URL: https://issues.apache.org/jira/browse/HDFS-712
> Project: Hadoop HDFS
>  Issue Type: Task
>Reporter: Eli Collins
>Assignee: Eli Collins
> Fix For: 0.22.0
>
> Attachments: addlibhdfs.patch
>
>
> Here's an hdfs jira for MAPREDUCE-665. During the project split libhdfs was 
> put in the mapreduce repo instead of hdfs, lets move it to hdfs.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (HDFS-712) Move libhdfs from mr to hdfs

2009-11-08 Thread dhruba borthakur (JIRA)

 [ 
https://issues.apache.org/jira/browse/HDFS-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

dhruba borthakur updated HDFS-712:
--

Component/s: contrib/libhdfs

> Move libhdfs from mr to hdfs 
> -
>
> Key: HDFS-712
> URL: https://issues.apache.org/jira/browse/HDFS-712
> Project: Hadoop HDFS
>  Issue Type: Task
>  Components: contrib/libhdfs
>Reporter: Eli Collins
>Assignee: Eli Collins
> Fix For: 0.22.0
>
> Attachments: addlibhdfs.patch
>
>
> Here's an hdfs jira for MAPREDUCE-665. During the project split libhdfs was 
> put in the mapreduce repo instead of hdfs, lets move it to hdfs.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Created: (HDFS-756) libhdfs unit tests do not run

2009-11-08 Thread dhruba borthakur (JIRA)
libhdfs unit tests do not run 
--

 Key: HDFS-756
 URL: https://issues.apache.org/jira/browse/HDFS-756
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: contrib/libhdfs
Reporter: dhruba borthakur
 Fix For: 0.22.0


The libhdfs unit tests (ant test-c++-libhdfs -Dislibhdfs=1) do not run yet 
because the scripts are in the common subproject,

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.