hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rodrigo Schmidt (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-1518) On contrib/raid, the RaidNode currently runs the deletion check for parity files on directories too. It would be better if it didn't.
Date Thu, 04 Mar 2010 23:51:27 GMT

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

Rodrigo Schmidt updated MAPREDUCE-1518:
---------------------------------------

    Attachment: MAPREDUCE-1518.0.patch

> On contrib/raid, the RaidNode currently runs the deletion check for parity files on directories
too. It would be better if it didn't.
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1518
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1518
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: contrib/raid
>         Environment: On contrib/raid, the RaidNode currently runs the deletion check
for parity files on directories too. It runs okay because the directory is not empty and trying
to delete it non-recursively fails, but such failure messages only polute the log file.
> My proposal is the following:
> If recursePurge is checking a directory, it should call itself recursively.
> If it's checking a file, it should do the deletion check.
>            Reporter: Rodrigo Schmidt
>            Assignee: Rodrigo Schmidt
>         Attachments: MAPREDUCE-1518.0.patch
>
>


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


Mime
View raw message