lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shalin Shekhar Mangar (JIRA)" <>
Subject [jira] [Commented] (SOLR-9858) Collect aggregated metrics from nodes and shard leaders in overseer
Date Mon, 06 Mar 2017 14:50:32 GMT


Shalin Shekhar Mangar commented on SOLR-9858:

I tried the patch again Andrzej but I found another bug. Instead of core name, now the core
node name is used for the core-specific registry e.g. I see {{solr.core.gettingstarted.shard1.core_node1}}
in the output of /admin/metrics.

I have a few more requests:
# In this patch, the leader metrics are exposed at e.g. {{solr.core.gettingstarted.shard2.leader}}
and {{solr.core.gettingstarted.shard2.leader}} -- there is no reason to have "core" in this
name. Can we rename it to e.g. {{solr.collection.gettingstarted.shard1.leader}}?
# The aggregated cluster level metrics are exposed at {{solr.overseer}}. Can we rename it
to {{solr.cluster}} to make its purpose explicit? Another reason to do this is that in future
when we have overseer specific metrics such as the ones from the Overseer Status collection
API, they will have to be shoehorned into the same registry and for users it will be difficult
to distinguish between what is aggregated from the cluster and what is overseer specific.
# Can we disable the aggregation by default? Users should be able to enable/disable this aggregation
via the CLUSTERPROP API for the cluster level metrics and using modify collection API for
the leader level metrics. If you want, we can have just one switch for both and separate them
out later.

> Collect aggregated metrics from nodes and shard leaders in overseer
> -------------------------------------------------------------------
>                 Key: SOLR-9858
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: metrics
>    Affects Versions: master (7.0)
>            Reporter: Andrzej Bialecki 
>            Assignee: Andrzej Bialecki 
>            Priority: Minor
>         Attachments: SOLR-9858.patch, SOLR-9858.patch
> Overseer can collect metrics from Solr nodes and shard leaders in order to have a notion
of the indexing / query / replication / system load on each node, shard and its replicas.
This information then can be used for cluster (auto)scaling.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message