You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Nikita Amelchev (Jira)" <ji...@apache.org> on 2025/11/28 12:41:00 UTC
[jira] [Updated] (IGNITE-26248) Better tooling for cluster topology monitoring
[ https://issues.apache.org/jira/browse/IGNITE-26248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nikita Amelchev updated IGNITE-26248:
-------------------------------------
Labels: IEP-140 ise (was: ise)
> Better tooling for cluster topology monitoring
> ----------------------------------------------
>
> Key: IGNITE-26248
> URL: https://issues.apache.org/jira/browse/IGNITE-26248
> Project: Ignite
> Issue Type: Task
> Reporter: Sergey Chugunov
> Assignee: Nikita Amelchev
> Priority: Major
> Labels: IEP-140, ise
>
> h3. *Motivation*
> MultiDC support requires considerable changes in TcpDiscovery protocol, so we need a tooling to better understand what topology looks like from a point of view of each node.
> Moreover, in MultiDC environment chances of split-brain events are higher and a reliable tool to quickly inspect current topology state is necessary.
> h3. Description
> Summarize tools already available including output to logs or control.sh commands. Come up with ideas how to enhance existing tools or add new ones.
> Requirements:
> # There should be tools working locally on each node (e.g. better logging) as well as cluster-wide (like control.sh command or metrics).
> # Tools should provide information about topology in an easy-to-understand form. E.g. lists or UUIDs of nodes is not an acceptable form as it is hard to read UUIDs by naked eye.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)