[
https://issues.apache.org/jira/browse/HBASE-22408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shelukhin updated HBASE-22408:
-------------------------------------
Description:
This serves 2 purposes for monitoring:
1) Catching when regions are on dead servers due to long WAL splitting or other
delays in SCP. At that time, the regions are not listed as RITs; we'd like to
be able to have alerts in such cases.
2) Catching various bugs in assignment and procWAL corruption, etc. that leave
region "OPEN" on a server that no longer exists, again to alert the
administrator via a metric.
Later, it might be possible to add more logic to distinguish 1 and 2, and to
mitigate 2 automatically and also set some metric to alert the administrator to
investigate later.
was:
This serves 2 purposes for monitoring:
1) Catching when regions are on dead servers due to long WAL splitting or other
delays in SCP. At that time, the regions are not listed as RITs; we'd like to
be able to have alerts in such cases.
2) Catching various bugs in assignment and procWAL corruption, etc. that leave
region "OPEN" on a server that no longer exists, again to alert the
administrator via a metric.
Later, it might be possible to add more logic to distinguish 1 and 2, and add
logic to mitigate 2 automatically and also set some metric to alert the
administrator to investigate later.
> add a metric for regions OPEN on non-live servers
> -------------------------------------------------
>
> Key: HBASE-22408
> URL: https://issues.apache.org/jira/browse/HBASE-22408
> Project: HBase
> Issue Type: Bug
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Priority: Major
>
> This serves 2 purposes for monitoring:
> 1) Catching when regions are on dead servers due to long WAL splitting or
> other delays in SCP. At that time, the regions are not listed as RITs; we'd
> like to be able to have alerts in such cases.
> 2) Catching various bugs in assignment and procWAL corruption, etc. that
> leave region "OPEN" on a server that no longer exists, again to alert the
> administrator via a metric.
> Later, it might be possible to add more logic to distinguish 1 and 2, and to
> mitigate 2 automatically and also set some metric to alert the administrator
> to investigate later.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
