[
https://issues.apache.org/jira/browse/SOLR-15300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17339645#comment-17339645
]
Jan Høydahl commented on SOLR-15300:
------------------------------------
Can you perhaps create a JIRA for exposing this health status in AdminUI
"nodes" screen? And another JIRA to expose it in Prometheus Exporter? Not sure
if the {{bin/solr status}} response should also have it? But currently it only
displays number of nodes and number of collections, so per-collection info is
probably not fit for that one. Would it make sense to have a cluster-level
health as well, that would give people one place to look if things are GREEN,
and if things are YELLOW you can dig further into which collection is having
issues...
> Shard "state" flag is confusing and of limited value to outside consumers
> -------------------------------------------------------------------------
>
> Key: SOLR-15300
> URL: https://issues.apache.org/jira/browse/SOLR-15300
> Project: Solr
> Issue Type: Improvement
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Solr API (and consequently the metric reporters, which are often used for
> Solr monitoring) report the shard as being in ACTIVE state even when in
> reality its functionality is severely compromised (eg. no replicas, all
> replicas down, or no leader).
> This reported state is technically correct because it is used only for
> tracking of the SPLITSHARD operations, as defined in {{Slice.State}}.
> However, this may be misleading and more often unhelpful than not - for
> constant monitoring a flag that actually reports impaired functionality of a
> shard would be more useful than a flag that reports a relatively uncommon
> SPLITSHARD operation.
> We could either redefine the meaning of the existing flag (and change its
> state according to some of the criteria I listed above), or add another flag
> to represent the "health" status of a shard. The value of this flag would
> then provide an easy way to monitor and to alert external systems of
> dangerous function impairment, without monitoring the state of all replicas
> of a collection.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
