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 "Robert Chansler (JIRA)" <ji...@apache.org> on 2008/08/26 23:58:46 UTC
[jira] Created: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
NameNode should report status and performance for each replica of image and log
-------------------------------------------------------------------------------
Key: HADOOP-4029
URL: https://issues.apache.org/jira/browse/HADOOP-4029
Project: Hadoop Core
Issue Type: New Feature
Components: dfs
Affects Versions: 0.18.0
Reporter: Robert Chansler
The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654831#action_12654831 ]
Hudson commented on HADOOP-4029:
--------------------------------
Integrated in Hadoop-trunk #683 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/683/])
. Add NameNode storage information to the dfshealth page and move DataNode information to a separated page. (Boris Shkolnik via szetszwo)
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Fix For: 0.20.0
>
> Attachments: HADOOP-4029-1.patch, HADOOP-4029-2.patch, HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik reassigned HADOOP-4029:
--------------------------------------
Assignee: Boris Shkolnik
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.18.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-4029:
-----------------------------------
Attachment: HADOOP-4029.patch
This patch include the following changes:
1. additional storage directory (in Storage class) to keep removed(failed) storages and accessors to this list
2. changes to FSImage to add storages to this list (when IO failes)
3. changes to the dfshealth.jsp page to display both lists (valid and failed storages)
4. List of live/dead nodes is moved to a separate page.
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.18.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Attachments: HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-4029:
-----------------------------------
Status: Open (was: Patch Available)
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Attachments: HADOOP-4029-1.patch, HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Robert Chansler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Chansler updated HADOOP-4029:
------------------------------------
Release Note: Added name node storage information to the dfshealth page, and moved data node information to a separated page. (was: Add NameNode storage information to the dfshealth page and move DataNode information to a separated page.)
Hadoop Flags: [Incompatible change, Reviewed] (was: [Reviewed, Incompatible change])
Edit release note for publication.
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Fix For: 0.20.0
>
> Attachments: HADOOP-4029-1.patch, HADOOP-4029-2.patch, HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-4029:
-----------------------------------
Affects Version/s: (was: 0.18.0)
0.20.0
Status: Patch Available (was: Open)
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Attachments: HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-4029:
-----------------------------------
Status: Patch Available (was: Open)
implemented Konstantin's comments
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Attachments: HADOOP-4029-1.patch, HADOOP-4029-2.patch, HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-4029:
-----------------------------------
Status: Open (was: Patch Available)
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Attachments: HADOOP-4029-1.patch, HADOOP-4029-2.patch, HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsz Wo (Nicholas), SZE updated HADOOP-4029:
-------------------------------------------
Resolution: Fixed
Fix Version/s: 0.20.0
Release Note: Add NameNode storage information to the dfshealth page and move DataNode information to a separated page.
Hadoop Flags: [Incompatible change, Reviewed]
Status: Resolved (was: Patch Available)
I just committed this. Thanks, Boris!
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Fix For: 0.20.0
>
> Attachments: HADOOP-4029-1.patch, HADOOP-4029-2.patch, HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-4029:
-----------------------------------
Attachment: HADOOP-4029-2.patch
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Attachments: HADOOP-4029-1.patch, HADOOP-4029-2.patch, HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-4029:
-----------------------------------
Status: Patch Available (was: Open)
implemented suggestions given by Konstantin
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Attachments: HADOOP-4029-1.patch, HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-4029:
-----------------------------------
Attachment: (was: HADOOP-4029-2.patch)
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Attachments: HADOOP-4029-1.patch, HADOOP-4029-2.patch, HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652629#action_12652629 ]
Konstantin Shvachko commented on HADOOP-4029:
---------------------------------------------
# Storage.removedStorageDirs should be a member of FSImage rather than Storage class.
# In FSImage.java redundant import of StorageDirectory.
# Remove comments with test printouts from FSImage.processIOError();
# Replace tabs with spaces in FSImage.processIOError();
# In dfshealth.jsp
#- Instead of "FSImage Storage Configuration:" I'd rather say "NameNode Storage:"
#- Column "Dir" should rather be named "Storage Directory".
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Attachments: HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652610#action_12652610 ]
Boris Shkolnik commented on HADOOP-4029:
----------------------------------------
-1 findbugs
These warnings should be ignored. See JIRA HADOOP-4755
-1 core tests
Both failed tests are in mapred and not related to the changes in the patch.
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Attachments: HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654388#action_12654388 ]
Hadoop QA commented on HADOOP-4029:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12395466/HADOOP-4029-2.patch
against trunk revision 724229.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no tests are needed for this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
-1 findbugs. The patch appears to introduce 2 new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3686/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3686/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3686/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3686/console
This message is automatically generated.
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Attachments: HADOOP-4029-1.patch, HADOOP-4029-2.patch, HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653920#action_12653920 ]
Konstantin Shvachko commented on HADOOP-4029:
---------------------------------------------
Minor comments:
# {{FSImage.getStorageDirs()}} is redundant. You should use {{Storage.getNumStorageDirs()}} and {{Storage.getStorageDir(idx)}} instead.
# Could you please remove empty lines after {{it.remove()}} in FSImage.
# Unnecessary empty lines changes in dfshealth.jsp.
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Attachments: HADOOP-4029-1.patch, HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-4029:
-----------------------------------
Status: Patch Available (was: Open)
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Attachments: HADOOP-4029-1.patch, HADOOP-4029-2.patch, HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-4029:
-----------------------------------
Attachment: HADOOP-4029-1.patch
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Attachments: HADOOP-4029-1.patch, HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-4029:
-----------------------------------
Attachment: HADOOP-4029-2.patch
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Attachments: HADOOP-4029-1.patch, HADOOP-4029-2.patch, HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654011#action_12654011 ]
Konstantin Shvachko commented on HADOOP-4029:
---------------------------------------------
+1
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Attachments: HADOOP-4029-1.patch, HADOOP-4029-2.patch, HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-4029:
-----------------------------------
Status: Open (was: Patch Available)
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Attachments: HADOOP-4029-1.patch, HADOOP-4029-2.patch, HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4029) NameNode should report status and
performance for each replica of image and log
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651719#action_12651719 ]
Hadoop QA commented on HADOOP-4029:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12394796/HADOOP-4029.patch
against trunk revision 721415.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no tests are needed for this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
-1 findbugs. The patch appears to introduce 2 new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3670/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3670/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3670/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3670/console
This message is automatically generated.
> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Attachments: HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.