You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Konstantin Shvachko (JIRA)" <ji...@apache.org> on 2007/07/10 08:44:04 UTC
[jira] Created: (HADOOP-1583) AlreadyBeingCreatedException because
pendingCreates is non-null
AlreadyBeingCreatedException because pendingCreates is non-null
---------------------------------------------------------------
Key: HADOOP-1583
URL: https://issues.apache.org/jira/browse/HADOOP-1583
Project: Hadoop
Issue Type: Bug
Affects Versions: 0.9.2
Reporter: Konstantin Shvachko
Fix For: 0.14.0
When a client lease expires the lease monitor removes it from the list of leases, but
does not release pendingCreates files. When the name-node sees a file in pendingCreates
which does not have a lease for the original client it throws AlreadyBeingCreatedException.
This was reported in several issues like HADOOP-1411, but has never been resolved.
I see two approaches:
# clean pendingCreates when leases expire, or
# reuse entries in pending creates for which there are no lease.
The first is preferable imo since it cleans memory at the right time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1583) AlreadyBeingCreatedException because
pendingCreates is non-null
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1583:
-------------------------------------
Fix Version/s: 0.15.0
> AlreadyBeingCreatedException because pendingCreates is non-null
> ---------------------------------------------------------------
>
> Key: HADOOP-1583
> URL: https://issues.apache.org/jira/browse/HADOOP-1583
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.9.2
> Reporter: Konstantin Shvachko
> Fix For: 0.15.0
>
>
> When a client lease expires the lease monitor removes it from the list of leases, but
> does not release pendingCreates files. When the name-node sees a file in pendingCreates
> which does not have a lease for the original client it throws AlreadyBeingCreatedException.
> This was reported in several issues like HADOOP-1411, but has never been resolved.
> I see two approaches:
> # clean pendingCreates when leases expire, or
> # reuse entries in pending creates for which there are no lease.
> The first is preferable imo since it cleans memory at the right time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1583) AlreadyBeingCreatedException because
pendingCreates is non-null
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1583:
-------------------------------------
Component/s: dfs
> AlreadyBeingCreatedException because pendingCreates is non-null
> ---------------------------------------------------------------
>
> Key: HADOOP-1583
> URL: https://issues.apache.org/jira/browse/HADOOP-1583
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.9.2
> Reporter: Konstantin Shvachko
> Priority: Blocker
> Fix For: 0.14.0
>
>
> When a client lease expires the lease monitor removes it from the list of leases, but
> does not release pendingCreates files. When the name-node sees a file in pendingCreates
> which does not have a lease for the original client it throws AlreadyBeingCreatedException.
> This was reported in several issues like HADOOP-1411, but has never been resolved.
> I see two approaches:
> # clean pendingCreates when leases expire, or
> # reuse entries in pending creates for which there are no lease.
> The first is preferable imo since it cleans memory at the right time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1583) AlreadyBeingCreatedException because
pendingCreates is non-null
Posted by "Nigel Daley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nigel Daley updated HADOOP-1583:
--------------------------------
Priority: Blocker (was: Major)
> AlreadyBeingCreatedException because pendingCreates is non-null
> ---------------------------------------------------------------
>
> Key: HADOOP-1583
> URL: https://issues.apache.org/jira/browse/HADOOP-1583
> Project: Hadoop
> Issue Type: Bug
> Affects Versions: 0.9.2
> Reporter: Konstantin Shvachko
> Priority: Blocker
> Fix For: 0.14.0
>
>
> When a client lease expires the lease monitor removes it from the list of leases, but
> does not release pendingCreates files. When the name-node sees a file in pendingCreates
> which does not have a lease for the original client it throws AlreadyBeingCreatedException.
> This was reported in several issues like HADOOP-1411, but has never been resolved.
> I see two approaches:
> # clean pendingCreates when leases expire, or
> # reuse entries in pending creates for which there are no lease.
> The first is preferable imo since it cleans memory at the right time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1583) AlreadyBeingCreatedException because
pendingCreates is non-null
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1583:
-------------------------------------
Priority: Major (was: Blocker)
This is not a regression from earlier releases, so i am removing the "Blocker" tag.
> AlreadyBeingCreatedException because pendingCreates is non-null
> ---------------------------------------------------------------
>
> Key: HADOOP-1583
> URL: https://issues.apache.org/jira/browse/HADOOP-1583
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.9.2
> Reporter: Konstantin Shvachko
> Fix For: 0.14.0
>
>
> When a client lease expires the lease monitor removes it from the list of leases, but
> does not release pendingCreates files. When the name-node sees a file in pendingCreates
> which does not have a lease for the original client it throws AlreadyBeingCreatedException.
> This was reported in several issues like HADOOP-1411, but has never been resolved.
> I see two approaches:
> # clean pendingCreates when leases expire, or
> # reuse entries in pending creates for which there are no lease.
> The first is preferable imo since it cleans memory at the right time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.