Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <934255597.1226973404223.JavaMail.jira@brutus>
Date: Mon, 17 Nov 2008 17:56:44 -0800 (PST)
From: "Pete Wyckoff (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-4619) hdfs_write infinite loop when dfs
 fails and cannot write files > 2 GB
In-Reply-To: <1539217653.1226100944402.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Pete Wyckoff updated HADOOP-4619:
---------------------------------

    Attachment: HADOOP-4619.txt

good catch - attaching new patch that does the error checking on the size relative to SIZE_MAX rather than ULONG_MAX.

This does mean however that the size that can be written on a 32 bit machine is only 4GB.  Should we change from using size_t to using long long in this case?


> hdfs_write infinite loop when dfs fails and cannot write files > 2 GB
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-4619
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4619
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: libhdfs
>    Affects Versions: 0.19.0, 0.20.0
>            Reporter: Pete Wyckoff
>            Assignee: Pete Wyckoff
>             Fix For: 0.19.1, 0.20.0
>
>         Attachments: HADOOP-4619.txt, HADOOP-4619.txt, HADOOP-4619.txt, HADOOP-4619.txt, HADOOP-4619.txt
>
>
> 1. hdfs_write  does not check hdfsWrite return code so -1 return code is ignored.
> 2. hdfs_write uses int for overall file length

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