Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <995746633.1206050604530.JavaMail.jira@brutus>
Date: Thu, 20 Mar 2008 15:03:24 -0700 (PDT)
From: =?utf-8?Q?Andr=C3=A9_Martin_=28JIRA=29?= <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3051) DataXceiver: java.io.IOException:
 Too many open files
In-Reply-To: <2082866017.1205964984801.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HADOOP-3051?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D125=
80942#action_12580942 ]=20

Andr=C3=A9 Martin commented on HADOOP-3051:
--------------------------------------

I increased the fd limit to 4096 :-) It performs way better now...

Anyway I would recommend to set the default to "not to use extra fds" since=
 I assume that a bunch of other users will have the same experience when up=
grading from earlier releases...?!?


> DataXceiver: java.io.IOException: Too many open files
> -----------------------------------------------------
>
>                 Key: HADOOP-3051
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3051
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.17.0
>            Reporter: Andr=C3=A9 Martin
>            Assignee: Raghu Angadi
>
> I just ran an experiment with the latest nightly build hadoop-2008-03-15 =
available and after 2 minutes I'm getting a tons of "java.io.IOException: T=
oo many open files" exceptions as shown here:
> {noformat} 2008-03-19 20:08:09,303 ERROR org.apache.hadoop.dfs.DataNode:=
=20
> 141.30.xxx.xxx:50010:DataXceiver: java.io.IOException: Too many open file=
s
>      at sun.nio.ch.IOUtil.initPipe(Native Method)
>      at sun.nio.ch.EPollSelectorImpl.<init>(Unknown Source)
>      at sun.nio.ch.EPollSelectorProvider.openSelector(Unknown Source)
>      at sun.nio.ch.Util.getTemporarySelector(Unknown Source)
>      at sun.nio.ch.SocketAdaptor.connect(Unknown Source)
>      at org.apache.hadoop.dfs.DataNode$DataXceiver.writeBlock(DataNode.ja=
va:1114)
>      at org.apache.hadoop.dfs.DataNode$DataXceiver.run(DataNode.java:956)
>      at java.lang.Thread.run(Unknown Source){noformat}
> I ran the same experiment with same high workload (50 dfs clients with 40=
 streams each writing concurrently files on a 8 nodes DFS cluster) with the=
 0.16.1 release and no exception is thrown. So it looks like a bug to me...

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