You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Ramya Sunil (Created) (JIRA)" <ji...@apache.org> on 2011/10/26 01:32:32 UTC
[jira] [Created] (MAPREDUCE-3271) Lost nodes list and count not
updated
Lost nodes list and count not updated
-------------------------------------
Key: MAPREDUCE-3271
URL: https://issues.apache.org/jira/browse/MAPREDUCE-3271
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: mrv2
Affects Versions: 0.23.0
Reporter: Ramya Sunil
Fix For: 0.23.0
When nodemanagers are lost, the "Lost Nodes" list and the count is not incremented. Either we,
1. Fix the lost nodes list when a nodemanager is lost - The problem with tracking lost nodes is, if the nodemanager joins back, there would be duplicate entries in active and lost nodes with different port numbers.
2. Do not track lost nodemanagers
--
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
[jira] [Assigned] (MAPREDUCE-3271) Lost nodes list and count not
updated
Posted by "Jason Lowe (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Lowe reassigned MAPREDUCE-3271:
-------------------------------------
Assignee: Jason Lowe
> Lost nodes list and count not updated
> -------------------------------------
>
> Key: MAPREDUCE-3271
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3271
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Ramya Sunil
> Assignee: Jason Lowe
> Priority: Critical
> Fix For: 0.23.1
>
>
> When nodemanagers are lost, the "Lost Nodes" list and the count is not incremented. Either we,
> 1. Fix the lost nodes list when a nodemanager is lost - The problem with tracking lost nodes is, if the nodemanager joins back, there would be duplicate entries in active and lost nodes with different port numbers.
> 2. Do not track lost nodemanagers
--
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
[jira] [Resolved] (MAPREDUCE-3271) Lost nodes list and count not
updated
Posted by "Jason Lowe (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Lowe resolved MAPREDUCE-3271.
-----------------------------------
Resolution: Duplicate
The patch being worked on in MAPREDUCE-3360 includes tracking lost nodes and decrementing lost counts when they rejoin the cluster.
> Lost nodes list and count not updated
> -------------------------------------
>
> Key: MAPREDUCE-3271
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3271
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Ramya Sunil
> Assignee: Jason Lowe
> Priority: Critical
> Fix For: 0.23.1
>
>
> When nodemanagers are lost, the "Lost Nodes" list and the count is not incremented. Either we,
> 1. Fix the lost nodes list when a nodemanager is lost - The problem with tracking lost nodes is, if the nodemanager joins back, there would be duplicate entries in active and lost nodes with different port numbers.
> 2. Do not track lost nodemanagers
--
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
[jira] [Commented] (MAPREDUCE-3271) Lost nodes list and count not
updated
Posted by "Jonathan Eagles (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160168#comment-13160168 ]
Jonathan Eagles commented on MAPREDUCE-3271:
--------------------------------------------
Currently the count is now incremented upon lost nodes, but is not decremented upon rejoin. Lost nodes list may be the same as in MAPREDUCE-3360.
> Lost nodes list and count not updated
> -------------------------------------
>
> Key: MAPREDUCE-3271
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3271
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Ramya Sunil
> Priority: Critical
> Fix For: 0.23.1
>
>
> When nodemanagers are lost, the "Lost Nodes" list and the count is not incremented. Either we,
> 1. Fix the lost nodes list when a nodemanager is lost - The problem with tracking lost nodes is, if the nodemanager joins back, there would be duplicate entries in active and lost nodes with different port numbers.
> 2. Do not track lost nodemanagers
--
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
[jira] [Updated] (MAPREDUCE-3271) Lost nodes list and count not
updated
Posted by "Hitesh Shah (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hitesh Shah updated MAPREDUCE-3271:
-----------------------------------
Priority: Critical (was: Major)
> Lost nodes list and count not updated
> -------------------------------------
>
> Key: MAPREDUCE-3271
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3271
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Ramya Sunil
> Priority: Critical
> Fix For: 0.23.1
>
>
> When nodemanagers are lost, the "Lost Nodes" list and the count is not incremented. Either we,
> 1. Fix the lost nodes list when a nodemanager is lost - The problem with tracking lost nodes is, if the nodemanager joins back, there would be duplicate entries in active and lost nodes with different port numbers.
> 2. Do not track lost nodemanagers
--
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