[jira] [Comment Edited] (HBASE-21521) Expose master startup status via JMX and web UI
[ https://issues.apache.org/jira/browse/HBASE-21521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412168#comment-17412168 ] Rushabh Shah edited comment on HBASE-21521 at 9/8/21, 8:17 PM: --- Raised a PR: [https://github.com/apache/hbase/pull/3667] Screenshots attached. Added a sleep for 30 seconds for master to become active, so that I can see that progress page is showing correct information. was (Author: shahrs87): Raised a PR: [https://github.com/apache/hbase/pull/3667] Screenshots attached. > Expose master startup status via JMX and web UI > --- > > Key: HBASE-21521 > URL: https://issues.apache.org/jira/browse/HBASE-21521 > Project: HBase > Issue Type: Improvement > Components: master, UI >Reporter: Andrew Kyle Purtell >Assignee: Rushabh Shah >Priority: Major > Attachments: hbase-21521-1.png, hbase-21521-2.png, hbase-21521-3.png, > hbase-21521-4.png > > > Add an internal API to the master for tracking startup progress. Expose this > information via JMX. > Modify the master to bring the web UI up sooner. Will require tweaks to > various views to prevent attempts to retrieve state before the master fully > up (or else expect NPEs). Currently, before the master has fully initialized > an attempt to use the web UI will return a 500 error code and display an > error page. > Finally, update the web UI to display startup progress, like HDFS-4249. > Filing this for branch-1. Need to check what if anything is available or > improved in branch-2 and master. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (HBASE-21521) Expose master startup status via JMX and web UI
[ https://issues.apache.org/jira/browse/HBASE-21521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938944#comment-16938944 ] Rushabh Shah edited comment on HBASE-21521 at 9/26/19 8:17 PM: --- I went through hmaster initialization tasks and found the following tasks which may take time. [~apurtell] [~stack] [~reidchan] [~pankaj2461] Please let me know if I am missing any tasks. Thank you ! * Initialize Memstore chunk creator. (only if tables on master) * Create Procedure Executor * Assignment Manager * Start RegionServer Tracker * Initialize Zk System Trackers ** Load procedures (done as a part of zookeeper initialization) * Waiting for RegionServers to be online * Wait for meta to be online. * Wait for Assignment Manager to process offline regions. * Wait for namespace to be online. * Initialize Cluster Schema Service. was (Author: shahrs87): I went through hmaster initialization tasks and found the following tasks which may take time. [~apurtell] [~stack] [~reidchan] [~pankaj2461] Please let me know if I am missing any tasks. Thank you ! * Startup tasks * Initialize Memstore chunk creator. (only if tables on master) * Create Procedure Executor * Assignment Manager * Start RegionServer Tracker * Initialize Zk System Trackers ** Load procedures (done as a part of zookeeper initialization) * Waiting for RegionServers to be online * Wait for meta to be online. * Wait for Assignment Manager to process offline regions. * Wait for namespace to be online. * Initialize Cluster Schema Service. > Expose master startup status via JMX and web UI > --- > > Key: HBASE-21521 > URL: https://issues.apache.org/jira/browse/HBASE-21521 > Project: HBase > Issue Type: Improvement > Components: master, UI >Reporter: Andrew Kyle Purtell >Assignee: Rushabh Shah >Priority: Major > > Add an internal API to the master for tracking startup progress. Expose this > information via JMX. > Modify the master to bring the web UI up sooner. Will require tweaks to > various views to prevent attempts to retrieve state before the master fully > up (or else expect NPEs). Currently, before the master has fully initialized > an attempt to use the web UI will return a 500 error code and display an > error page. > Finally, update the web UI to display startup progress, like HDFS-4249. > Filing this for branch-1. Need to check what if anything is available or > improved in branch-2 and master. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (HBASE-21521) Expose master startup status via JMX and web UI
[ https://issues.apache.org/jira/browse/HBASE-21521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916199#comment-16916199 ] Andrew Purtell edited comment on HBASE-21521 at 8/26/19 11:00 PM: -- What stack said. However, the inspiration for this idea comes in part from what HDFS does for their namenode: HDFS-4249 . Judging by the screenshot on that JIRA a lot of front end knowledge was not required. Looks like a table and some basic formatting. rendered once. To update you refetch at the browser. Namenode startup can be orders of magnitude longer than HBase master startup for all but the really abnormal cases (like hundreds of queued ServerCrashProcedures) so the pressure to do a detailed phase by phase status report update is less, but would still be nice. was (Author: apurtell): What stack said. However, the inspiration for this idea comes in part from what HDFS does for their namenode: HDFS-4249 Namenode startup can be orders of magnitude longer than HBase master startup for all but the really abnormal cases (like hundreds of queued ServerCrashProcedures) so the pressure to do a detailed phase by phase status report update is less, but would still be nice. > Expose master startup status via JMX and web UI > --- > > Key: HBASE-21521 > URL: https://issues.apache.org/jira/browse/HBASE-21521 > Project: HBase > Issue Type: Improvement > Components: master, UI >Reporter: Andrew Purtell >Priority: Major > > Add an internal API to the master for tracking startup progress. Expose this > information via JMX. > Modify the master to bring the web UI up sooner. Will require tweaks to > various views to prevent attempts to retrieve state before the master fully > up (or else expect NPEs). Currently, before the master has fully initialized > an attempt to use the web UI will return a 500 error code and display an > error page. > Finally, update the web UI to display startup progress, like HDFS-4249. > Filing this for branch-1. Need to check what if anything is available or > improved in branch-2 and master. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (HBASE-21521) Expose master startup status via JMX and web UI
[ https://issues.apache.org/jira/browse/HBASE-21521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916044#comment-16916044 ] Rushabh S Shah edited comment on HBASE-21521 at 8/26/19 6:36 PM: - Is this feature/improvement still required ? I would like to contribute to this jira if no one else is working on it. My front end skills are not that sharp but if no one else volunteers I will try to refine them. Initially I can expose all the jmx metrics and then work on adding them to web ui. [~apurtell] Please suggest. was (Author: shahrs87): Is this feature/improvement still required ? I would like to contribute to this jira if no one else is working on it. My front end skills are not that sharp but if no one else volunteers I will try to refine them. Initially I can expose all the jmx metrics and then work on adding them to web ui. Please suggest. > Expose master startup status via JMX and web UI > --- > > Key: HBASE-21521 > URL: https://issues.apache.org/jira/browse/HBASE-21521 > Project: HBase > Issue Type: Improvement > Components: master, UI >Reporter: Andrew Purtell >Priority: Major > > Add an internal API to the master for tracking startup progress. Expose this > information via JMX. > Modify the master to bring the web UI up sooner. Will require tweaks to > various views to prevent attempts to retrieve state before the master fully > up (or else expect NPEs). Currently, before the master has fully initialized > an attempt to use the web UI will return a 500 error code and display an > error page. > Finally, update the web UI to display startup progress, like HDFS-4249. > Filing this for branch-1. Need to check what if anything is available or > improved in branch-2 and master. -- This message was sent by Atlassian Jira (v8.3.2#803003)
