hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yiqun Lin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-10400) hdfs dfs -put exits with zero on error
Date Sat, 14 May 2016 11:53:13 GMT

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

Yiqun Lin commented on HDFS-10400:

I have looked into the code. When the src local files's num is more than one, it will invoke
its parent method. And the potenial IOException in method {{processArgument}} is catched in
{{Command}} and not be threw again.
  protected void processArguments(LinkedList<PathData> args)
  throws IOException {
    for (PathData arg : args) {
      try {
      } catch (IOException e) {
The similar case is also happens in {{Commands#processPaths}}. And these method will be involed
in {{processRawArguments(args);}}, its IOException will not be thred here. The numErrors will
also not be incrased.
  public int run(String...argv) {
    LinkedList<String> args = new LinkedList<String>(Arrays.asList(argv));
    try {
      if (isDeprecated()) {
            "DEPRECATED: Please use '"+ getReplacementCommand() + "' instead.");
    } catch (CommandInterruptException e) {
      return 130;
    } catch (IOException e) {
    return (numErrors == 0) ? exitCode : exitCodeForError();
So I think this is likely the reason. 
I'm glad to do further work for this, who can assign this JIRA to me? It seems that I can't
assign JIRA to myself now, thanks.

> hdfs dfs -put exits with zero on error
> --------------------------------------
>                 Key: HDFS-10400
>                 URL: https://issues.apache.org/jira/browse/HDFS-10400
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Jo Desmet
> On a filesystem that is about to fill up, execute "hdfs dfs -put" for a file that is
big enough to go over the limit. As a result, the command fails with an exception, however
the command terminates normally (exit code 0).
> Expectation is that any detectable failure generates an exit code different than zero.
> Documentation on https://hadoop.apache.org/docs/r1.2.1/file_system_shell.html#put states:
> Exit Code:
> Returns 0 on success and -1 on error. 
> following is the exception generated: 
> 16/05/11 13:37:07 INFO hdfs.DFSClient: Exception in createBlockOutputStream
> java.io.EOFException: Premature EOF: no length prefix available
>                 at org.apache.hadoop.hdfs.protocolPB.PBHelper.vintPrefixed(PBHelper.java:2282)
>                 at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.createBlockOutputStream(DFSOutputStream.java:1352)
>                 at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.nextBlockOutputStream(DFSOutputStream.java:1271)
>                 at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:464)
> 16/05/11 13:37:07 INFO hdfs.DFSClient: Abandoning BP-1964113808-
> 16/05/11 13:37:08 INFO hdfs.DFSClient: Excluding datanode DatanodeInfoWithStorage[,DS-eed7039a-8031-499e-85a5-7216b9d766a8,DISK]

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message