You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "vitthal (Suhas) Gogate (JIRA)" <ji...@apache.org> on 2012/05/13 05:19:23 UTC

[jira] [Created] (AMBARI-238) When namenode process is down info shown is not correct for both HDFS and MR

vitthal (Suhas) Gogate created AMBARI-238:
---------------------------------------------

             Summary: When namenode process is down info shown is not correct for both HDFS and MR
                 Key: AMBARI-238
                 URL: https://issues.apache.org/jira/browse/AMBARI-238
             Project: Ambari
          Issue Type: Bug
    Affects Versions: ambari-186
            Reporter: vitthal (Suhas) Gogate
            Assignee: vitthal (Suhas) Gogate


As we make jmx over http call to get information for HDFS/HBASE/MAPREDUCE, if their master daemons are down, we should show the down status correctly instead of showing broken UI or garbage information. It would take some time to have alert triggered for these master processes, so mean time dashboard front page if shows broken/garbage data, then user would not know the reason. 

--
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] (AMBARI-238) When namenode process is down info shown is not correct for both HDFS and MR

Posted by "vitthal (Suhas) Gogate (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMBARI-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

vitthal (Suhas) Gogate updated AMBARI-238:
------------------------------------------

    Attachment: AMBARI-238.patch
    
> When namenode process is down info shown is not correct for both HDFS and MR
> ----------------------------------------------------------------------------
>
>                 Key: AMBARI-238
>                 URL: https://issues.apache.org/jira/browse/AMBARI-238
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: ambari-186
>            Reporter: vitthal (Suhas) Gogate
>            Assignee: vitthal (Suhas) Gogate
>             Fix For: ambari-186
>
>         Attachments: AMBARI-238.patch
>
>
> As we make jmx over http call to get information for HDFS/HBASE/MAPREDUCE, if their master daemons are down, we should show the down status correctly instead of showing broken UI or garbage information. It would take some time to have alert triggered for these master processes, so mean time dashboard front page if shows broken/garbage data, then user would not know the reason. 

--
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] (AMBARI-238) When namenode process is down info shown is not correct for both HDFS and MR

Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMBARI-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli updated AMBARI-238:
-------------------------------------------

    Affects Version/s:     (was: ambari-186)
                       0.9.0
    
> When namenode process is down info shown is not correct for both HDFS and MR
> ----------------------------------------------------------------------------
>
>                 Key: AMBARI-238
>                 URL: https://issues.apache.org/jira/browse/AMBARI-238
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 0.9.0
>            Reporter: vitthal (Suhas) Gogate
>            Assignee: vitthal (Suhas) Gogate
>             Fix For: 0.9.0
>
>         Attachments: AMBARI-238.patch
>
>
> As we make jmx over http call to get information for HDFS/HBASE/MAPREDUCE, if their master daemons are down, we should show the down status correctly instead of showing broken UI or garbage information. It would take some time to have alert triggered for these master processes, so mean time dashboard front page if shows broken/garbage data, then user would not know the reason. 

--
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] (AMBARI-238) When namenode process is down info shown is not correct for both HDFS and MR

Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMBARI-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli updated AMBARI-238:
-------------------------------------------

    Fix Version/s:     (was: ambari-186)
                   0.9.0
    
> When namenode process is down info shown is not correct for both HDFS and MR
> ----------------------------------------------------------------------------
>
>                 Key: AMBARI-238
>                 URL: https://issues.apache.org/jira/browse/AMBARI-238
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: ambari-186
>            Reporter: vitthal (Suhas) Gogate
>            Assignee: vitthal (Suhas) Gogate
>             Fix For: 0.9.0
>
>         Attachments: AMBARI-238.patch
>
>
> As we make jmx over http call to get information for HDFS/HBASE/MAPREDUCE, if their master daemons are down, we should show the down status correctly instead of showing broken UI or garbage information. It would take some time to have alert triggered for these master processes, so mean time dashboard front page if shows broken/garbage data, then user would not know the reason. 

--
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