Write pipeline heartbeat interval should be determined by client timeout, not DN
Key: HDFS-917
URL: https://issues.apache.org/jira/browse/HDFS-917
Project: Hadoop HDFS
Rewrite DFSOutputStream to use a single thread with NIO
---
Key: HDFS-916
URL: https://issues.apache.org/jira/browse/HDFS-916
Project: Hadoop HDFS
Issue Type: Improvement
Componen
Hung DN stalls write pipeline for far longer than its timeout
-
Key: HDFS-915
URL: https://issues.apache.org/jira/browse/HDFS-915
Project: Hadoop HDFS
Issue Type: Bug
Comp
Refactor DFSOutputStream and DFSInputStream out of DFSClient
Key: HDFS-914
URL: https://issues.apache.org/jira/browse/HDFS-914
Project: Hadoop HDFS
Issue Type: Improvement
TestRename won't run automatically from 'run-test-hdfs-faul-inject' target
--
Key: HDFS-913
URL: https://issues.apache.org/jira/browse/HDFS-913
Project: Hadoop HDFS
Issu
sed in build.xml fails
---
Key: HDFS-912
URL: https://issues.apache.org/jira/browse/HDFS-912
Project: Hadoop HDFS
Issue Type: Bug
Environment: ant 1.7.1
Solaris
Reporter: Allen Wittenauer
test-cactus fails with timeout error on trunk
-
Key: HDFS-911
URL: https://issues.apache.org/jira/browse/HDFS-911
Project: Hadoop HDFS
Issue Type: Bug
Components: contrib/hdfsproxy
Steve,
A DoS could not be done using excludedNodes.
The blacklisting takes place only at DFSClientLevel. The NN will return a
list of block locations that excludes the nodes the client decided. This
list isn't persisted anywhere on the server. So if a client excludes the
entire set of DNs other
+1
Hairong
On Fri, Jan 22, 2010 at 10:51 AM, Dhruba Borthakur wrote:
> +1 for making this patch go into 0.21.
>
> thanks,
> dhruba
>
> On Fri, Jan 22, 2010 at 10:25 AM, Todd Lipcon wrote:
>
> > Hi Steve,
> >
> > All of the below may be good ideas, but I don't think they're relevant to
> > the
+1 for making this patch go into 0.21.
thanks,
dhruba
On Fri, Jan 22, 2010 at 10:25 AM, Todd Lipcon wrote:
> Hi Steve,
>
> All of the below may be good ideas, but I don't think they're relevant to
> the discussion at hand. Specifically, none of them can enter 0.21 without a
> vote as they'd be
Hi Steve,
All of the below may be good ideas, but I don't think they're relevant to
the discussion at hand. Specifically, none of them can enter 0.21 without a
vote as they'd be new features, and it doesn't even sound like there's a
JIRA out for them yet. Let's not put off a well-known improvement
> tweaked Hadoop to allow the datanodes to get the entire list
are you referring to datanodes or dfs clients here?
The client already gets the entire list of replica locations for a block
from the namenode. and one could always develop a DFS client that is free to
choose whatever locations it dec
Stack wrote:
I'm being 0 on this
-I would worry if the exclusion list was used by the NN to do its
blacklisting, I'm glad to see this isn't happening. Yes, you could pick
up datanode failure faster, but you would also be vulnerable to a user
doing a DoS against the cluster by reporting every
+1
On 1/22/10 3:24 AM, "Andrew Purtell" wrote:
> +1
>
> This makes an observed big difference for stability of small/test clusters.
>
> I second Ryan's specific point about stability of small clusters being
> important.
>
> - Andy
>
>
> On Thu Jan 21st, 2010 2:46 PM PST Ryan Rawson wro
[
https://issues.apache.org/jira/browse/HDFS-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon reopened HDFS-877:
--
This bug fix should go in 0.21 as well, I think. The current patch doesn't
apply, but I'll try to get to one
15 matches
Mail list logo
