You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Steshin (Jira)" <ji...@apache.org> on 2025/10/14 15:01:00 UTC

[jira] [Updated] (IGNITE-26708) Revise TcpDiscoveryMetricsUpdateMessage

     [ https://issues.apache.org/jira/browse/IGNITE-26708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Steshin updated IGNITE-26708:
--------------------------------------
    Epic Link: IGNITE-25883

> Revise TcpDiscoveryMetricsUpdateMessage
> ---------------------------------------
>
>                 Key: IGNITE-26708
>                 URL: https://issues.apache.org/jira/browse/IGNITE-26708
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladimir Steshin
>            Priority: Major
>              Labels: IEP-132, discovery, ise
>
> We have _TcpDiscoveryMetricsUpdateMessage_ and related {_}EVT_NODE_METRICS_UPDATED{_}. And also similar _ClusterMetricsUpdateMessage_ in {_}Communication{_}. Both of them send the metrics. If discovery is not of _TPC_ type (ZooKeeper for instance), then the metrics are sent through {_}Communication{_}:
> {code:java}
> ClusterProcessor:
> sndMetrics = !(ctx.config().getDiscoverySpi() instanceof TcpDiscoverySpi);
> if (sndMetrics) {
>     metricsProvider = ctx.discovery().createMetricsProvider();
>     long updateFreq = ctx.config().getMetricsUpdateFrequency();
>     ctx.timeout().addTimeoutObject(new MetricsUpdateTimeoutObject(updateFreq));
> } {code}
>  
> Why not sending the metrics via _Communication_ only? Pros: fewer discovery messages; no duplication of functionality, messages  and serialization; more lightweight discovery.
> No need of delivery guarantee here.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)