[
https://issues.apache.org/jira/browse/IGNITE-14405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin resolved IGNITE-14405.
------------------------------------------
Resolution: Fixed
> Local persistent key-value storage (Vault)
> ------------------------------------------
>
> Key: IGNITE-14405
> URL: https://issues.apache.org/jira/browse/IGNITE-14405
> Project: Ignite
> Issue Type: New Feature
> Reporter: Vyacheslav Koptilin
> Priority: Major
> Labels: ignite-3
>
> In order to maintain a local state of Ignite node, it is required to
> implement persistent key-value storage named Vault.
> The data stored in the vault is semantically divided into the following
> categories:
> - User-level local configuration properties (such as memory limits, network
> timeouts, etc). User-level configuration properties can be written both at
> runtime (not all properties will be applied at runtime, however, - some of
> them will require a full node restart) and when a node is shut down (in order
> to be able to change properties that prevent node startup for some reason)
> - System-level private properties (such as computed local statistics,
> node-local common paths, etc). System-level private properties are computed
> locally based on the information available at node locally (not based on
> metastorage watched values)
> - System-level distributed metastorage projected properties (such as paths
> to partition files, etc). System-level projected properties are associated
> with one or more metastorage properties and are computed based on the local
> node state and the metastorage properties values. System-level projected
> properties values are semantically bound to a particular revision of the
> dependee properties and must be recalculated when dependees are changed (see
> reliable watch processing).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
