[
https://issues.apache.org/jira/browse/HBASE-17436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16302133#comment-16302133
]
Appy edited comment on HBASE-17436 at 12/23/17 12:19 AM:
---------------------------------------------------------
open/offline/splitting are public concepts and reporting number for them is
much different then exposing our implementation details i.e. enum names/values
OPENING, SPLITTING, etc (which json api would do)
That said, am *for* idea of this patch, i think it can be useful to operators
(my only reason to support, it despite concerns raised above). i am just saying
that exposing internal stuff to public without notifying dev community is not a
right way.
The right way would be, sending out a note on dev@ stating this case (making
internal stuff public via json api) - explicitly listing pros (supposedly
useful to ops) and cons (points #3 and #4 above), and that it'll be done in x
days unless someone objects.
was (Author: appy):
open/offline/splitting are public concepts and reporting number for them is
much different then exposing our implementation details i.e. enum names/values
OPENING, SPLITTING, etc (which json api would do)
That said, am not against the idea of this patch, i think it can be useful to
operators (my only reason to support it despite concerns raised above). i am
just saying that exposing internal stuff to public without notifying dev
community is not a right way.
The right way would be, sending out a note on dev@ stating this case (making
internal stuff public via json api) - explicitly listing pros (supposedly
useful to ops) and cons (points #3 and #4 above), and that it'll be done in x
days unless someone objects.
> 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)
