[
https://issues.apache.org/jira/browse/IGNITE-20014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov updated IGNITE-20014:
--------------------------------------
Description:
h2. Motivation
Maintenance of complex software systems can be challenging, requiring efficient
monitoring, troubleshooting, and decision-making processes. However, without a
comprehensive understanding of the system's internal state, identifying issues
and making informed decisions becomes difficult. System Views, also known as
virtual tables, is a powerful tool that is meant to expose the system's state
and provide real-time insights into its various components. Therefore,
introducing System Views into Apache Ignite 3 can significantly improve the
system's maintainability.
h2. Requirements
# Any component of the AI3 should be able to register system views
# Updating the view should be as easy as restarting the cluster with updated
view definition
# Once registered, the view should be available on every node. This implies,
even if the view was registered on node N1 only, and is having data provider
for this view on N1 only, it still should be possible to query all the data
from this view from node N2. In other words, a user is going to interact with
the cluster, not a particular node, and view must be queryable regardless it
was registered on every node or not
was:
h2. Motivation
Maintenance of complex software systems can be challenging, requiring efficient
monitoring, troubleshooting, and decision-making processes. However, without a
comprehensive understanding of the system's internal state, identifying issues
and making informed decisions becomes difficult. System Views, also known as
virtual tables, is a powerful tool that is meant to expose the system's state
and provide real-time insights into its various components. Therefore,
introducing System Views into Apache Ignite 3 can significantly improve the
system's maintainability.
h2. Requirements
# Any component of the AI3 should be able to register system views
# Updating the view should be as easy as restarting the cluster with updated
view definition
# Once registered, the view should be available on every node. This implies,
even if the view was registered on node N1 only, and is having data provider
for this view on N1 only, it still should be possible to query all the data
from this view from node N2. In other words, a user is going to interact with
the cluster, not a particular node, and view must be queryable regardless it
was registered on every node or not
> System Views in AI3
> -------------------
>
> Key: IGNITE-20014
> URL: https://issues.apache.org/jira/browse/IGNITE-20014
> Project: Ignite
> Issue Type: Epic
> Reporter: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
>
> h2. Motivation
> Maintenance of complex software systems can be challenging, requiring
> efficient monitoring, troubleshooting, and decision-making processes.
> However, without a comprehensive understanding of the system's internal
> state, identifying issues and making informed decisions becomes difficult.
> System Views, also known as virtual tables, is a powerful tool that is meant
> to expose the system's state and provide real-time insights into its various
> components. Therefore, introducing System Views into Apache Ignite 3 can
> significantly improve the system's maintainability.
> h2. Requirements
> # Any component of the AI3 should be able to register system views
> # Updating the view should be as easy as restarting the cluster with updated
> view definition
> # Once registered, the view should be available on every node. This implies,
> even if the view was registered on node N1 only, and is having data provider
> for this view on N1 only, it still should be possible to query all the data
> from this view from node N2. In other words, a user is going to interact with
> the cluster, not a particular node, and view must be queryable regardless it
> was registered on every node or not
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
