[ 
https://issues.apache.org/jira/browse/HBASE-17436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16299213#comment-16299213
 ] 

Appy commented on HBASE-17436:
------------------------------

bq. result = "Still initializing, please wait.";
If an url is json api, it should return json no matter what. Return { error: 
"..." }

Design stuff:
# Why just assigned regions? Should be renamed 'Assigned Region States' then.
# What's the reason for excluding regions in splitting, opening, merging, 
closing, etc states?
# RegionStates is IA.Private. Maybe we don't have admin fns for these because 
we don't want to expose these internal states? Idk. But if so, this jsp is 
sneaking into AM and exposing private stuff.
# Official programmatic way of getting info about cluster should be Admin. Json 
endpoints are useful, but just exposing one endpoint for region states and 
nothing for other 10s of basic functionalities (tables, table states, 
regionserver names, etc) is not a good approach. These needs better designing 
first. Specially not a button on top banner. If we still decide to add it after 
figuring out #3, then let's add it as separate section after 'Tables' on 
master, something like following. I hope we can, because i'd like to see it 
there.
{panel}
h4. Regions
Number of regions: XX
json endpoint: ........
Use state=Foo to filter down regions by state.
{panel}


> Add facility to provide more information for Other Regions seen on Master UI
> ----------------------------------------------------------------------------
>
>                 Key: HBASE-17436
>                 URL: https://issues.apache.org/jira/browse/HBASE-17436
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ted Yu
>            Assignee: Janos Gub
>              Labels: ui, usability
>             Fix For: 2.0.0
>
>         Attachments: 17436.v10.txt, 17436.v11.txt, 17436.v12.txt, 
> 17436.v9.txt, HBASE-17436-v2.patch, HBASE-17436-v5.patch, 
> HBASE-17436-v6.patch, HBASE-17436-v6.patch, HBASE-17436-v7.patch, 
> HBASE-17436-v8.patch, HBASE-17436.patch, HBASE-17779-v3.patch, 
> HBASE-17779-v4.patch, Screen Shot 2017-04-24 at 8.43.31 PM.png, Screen Shot 
> 2017-04-26 at 4.39.49 PM.png, Screen Shot 2017-11-08 at 10.29.49 AM.png, 
> Screen Shot 2017-11-08 at 10.30.09 AM.png, Screen Shot 2017-11-22 at 4.17.35 
> PM.png, initial.patch, regionstates.png, table-selected.png, tableregions.png
>
>
> [~rpednekar] and I were looking at a case where the count displayed under 
> Other Regions was high (~1200).
> Since the table page just maintains a count instead of List of region names, 
> it is very difficult for user to determine which regions belong to this 
> category.
> We should provide facility to provide more details for this category (LOG, 
> JMX, etc).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to