[
https://issues.apache.org/jira/browse/IGNITE-16366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Chudov updated IGNITE-16366:
----------------------------------
Description:
Cluster-wide events, such as, for example, configuration changes or Metastorage
updates, trigger notifications that are propagated to the nodes and therefore,
to components. Every event can trigger several notifications. Every
notification has a causality token. Notifications triggered by the same event
have the same causality token.
{{Tokens should be added to org.apache.ignite.internal.manager.EventParameters}}
was:
Cluster-wide events, such as, for example, configuration changes or Metastorage
updates, trigger notifications that are propagated to the nodes and therefore,
to components. Every event can trigger several notifications. Every
notification has a causality token. Notifications triggered by the same event
have the same causality token.
Tokens should be added to org.apache.ignite.internal.manager.EventParameters
> Add causality tokens for notifications
> --------------------------------------
>
> Key: IGNITE-16366
> URL: https://issues.apache.org/jira/browse/IGNITE-16366
> Project: Ignite
> Issue Type: Improvement
> Reporter: Denis Chudov
> Priority: Major
> Labels: ignite-3
>
> Cluster-wide events, such as, for example, configuration changes or
> Metastorage updates, trigger notifications that are propagated to the nodes
> and therefore, to components. Every event can trigger several notifications.
> Every notification has a causality token. Notifications triggered by the same
> event have the same causality token.
> {{Tokens should be added to
> org.apache.ignite.internal.manager.EventParameters}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
