You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Mubarak Seyed (JIRA)" <ji...@apache.org> on 2012/07/20 08:35:34 UTC
[jira] [Commented] (FLUME-1370) HDFSEventSink - file name collision
in bucket path
[ https://issues.apache.org/jira/browse/FLUME-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418958#comment-13418958 ]
Mubarak Seyed commented on FLUME-1370:
--------------------------------------
One option is to use UUID in filename bucket path, it would look like
{code}
/logs/event1/07122012/22/2/Event1.f47ac10b-58cc-4372-a567-0e02b2c3d479.tmp
{code}
> HDFSEventSink - file name collision in bucket path
> --------------------------------------------------
>
> Key: FLUME-1370
> URL: https://issues.apache.org/jira/browse/FLUME-1370
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.2.0
> Environment: Linux, Java 1.6.0.24, hadoop-0.20.205, flume-1.2.0
> Reporter: Mubarak Seyed
> Labels: newbie
>
> It appears from test that two HDFS sinks (from different agent/machines) are trying to create same file name
> {code}
> 2012-07-12 22:18:51,820 WARN org.apache.hadoop.hdfs.StateChange: DIR* NameSystem.startFile: failed to create file /logs/event1/07122012/22/2/Event1.1342130410188.tmp for DFSClient_-1690064085 on client 0.0.0.1, because this file is already being created by DFSClient_1581651201 on 0.0.0.2
> 2012-07-12 22:18:51,820 INFO org.apache.hadoop.ipc.Server: IPC Server handler 8 on 8020, call create(/logs/event1/07122012/22/2/Event1.1342130410188.tmp, rwxr-xr-x, DFSClient_-1690064085, true, 3, 134217728) from 0.0.0.1:54280: error: org.apache.hadoop.hdfs.protocol.AlreadyBeingCreatedException: failed to create file /logs/event1/07122012/22/2/Event1.1342130410188.tmp for DFSClient_-1690064085 on client 0.0.0.1, because this file is already being created by DFSClient_1581651201 on 0.0.0.2
> org.apache.hadoop.hdfs.protocol.AlreadyBeingCreatedException: failed to create file /logs/event1/07122012/22/2/Event1.1342130410188.tmp for DFSClient_-1690064085 on client 0.0.0.1, because this file is already being created by DFSClient_1581651201 on 0.0.0.2
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.recoverLeaseInternal(FSNamesystem.java:1338)
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInternal(FSNamesystem.java:1178)
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFile(FSNamesystem.java:1126)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.create(NameNode.java:585)
> at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:557)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1434)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1430)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:396)
> at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1127)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:1428)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira