[
https://issues.apache.org/jira/browse/HBASE-21785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860064#comment-17860064
]
Umesh Kumar Kumawat commented on HBASE-21785:
---------------------------------------------
{quote}So the problem here is that if we have lots of regions to assign when a
region server is crashed, some of the regions will leave in OPEN state for a
long time, and then AssignmentManager will output strange message?
Is there a way to know that the procedure has not been executed yet? Maybe for
these RITs we could include the message that the procedure has not been
executed yet. I think it worth to warn if a procedure has not been scheduled
for a very long time?
{quote}
Am I right that this patch still doesn't solve this? I think it is fine in the
case of a server crash as even if the region is OPEN it is not available but in
draining should it report it in transition?
I did see such an issue where procedures were submitted but it took much time
to pick it up for execution. I thought HBASE-28158 could be a solution for
that.
cc [~apurtell] [~zhangduo]
> master reports open regions as RITs and also messes up rit age metric
> ---------------------------------------------------------------------
>
> Key: HBASE-21785
> URL: https://issues.apache.org/jira/browse/HBASE-21785
> Project: HBase
> Issue Type: Bug
> Affects Versions: 3.0.0-alpha-1, 2.2.0
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.2.0
>
> Attachments: HBASE-21785.01.patch, HBASE-21785.patch
>
>
> {noformat}
> Region State RIT time (ms) Retries
> dba183f0dadfcc9dc8ae0a6dd59c84e6 ....dba183f0dadfcc9dc8ae0a6dd59c84e6.
> state=OPEN, ts=Wed Dec 31 16:00:00 PST 1969 (1548453918s ago),
> server=server,17020,1548452922054 1548453918735 0
> {noformat}
> RIT age metric also gets set to a bogus value.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
