[
https://issues.apache.org/jira/browse/IGNITE-28933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov updated IGNITE-28933:
------------------------------------
Ignite Flags: (was: Docs Required,Release Notes Required)
> Get rid of Tracing-related classes stored in PDS
> ------------------------------------------------
>
> Key: IGNITE-28933
> URL: https://issues.apache.org/jira/browse/IGNITE-28933
> Project: Ignite
> Issue Type: Task
> Reporter: Mikhail Petrov
> Priority: Major
>
> After the Tracing internal implementation was removed in IGNITE-28910, the
> following classes were marked for removal in the next Apache Ignite release:
> * org.apache.ignite.spi.tracing.TracingConfigurationCoordinates
> * org.apache.ignite.spi.tracing.TracingConfigurationParameters
> However, these classes cannot be removed without considering PDS backward
> compatibility. Instances of these classes were stored in the distributed
> MetaStorage under the `"tr.config"` key. Since distributed MetaStorage values
> may be persisted to the Persistent Data Store (PDS), removing these classes
> could cause deserialization failures when MetaStorage entries are restored
> from PDS during node join.
> See -
> org.apache.ignite.internal.processors.metastorage.persistence.DistributedMetaStorageImpl#validatePayload.
> We need to investigate a mechanism for safely skipping deserialization of
> these classes when restoring data from older PDS versions so that they can be
> removed without breaking backward compatibility.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
