You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Rakov (JIRA)" <ji...@apache.org> on 2018/04/06 11:05:00 UTC
[jira] [Updated] (IGNITE-8162) Handle ClassNotFoundException during
deserialization of persisted cache configuration
[ https://issues.apache.org/jira/browse/IGNITE-8162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Rakov updated IGNITE-8162:
-------------------------------
Description:
Ticket is created according to dev list discussion: http://apache-ignite-developers.2346864.n4.nabble.com/Fwd-Data-Loss-while-upgrading-custom-jar-from-old-jar-in-server-and-client-nodes-td28808.html
Cache configuration is serialized by JDK marshaller and persisted in cache_data.dat file. It may contain instances of classes that disappeared from runtime classpath (e.g. if implementation of CacheStore has been renamed). In such case, node will fail on start.
We should handle this and show meaningful message with instruction how to overcome this issue - delete cache_data.dat and restart cache.
was:
Ticket is created according to dev list discussion: http://apache-ignite-developers.2346864.n4.nabble.com/Fwd-Data-Loss-while-upgrading-custom-jar-from-old-jar-in-server-and-client-nodes-td28808.html
Cache configuration is serialized by JDK marshaller and persisted in cache_data.dat file. It may contain instances of classes that disappeared from runtime classpath (e.g. in case implementation of CacheStore has been renamed). In such case, node will fail on start.
We should handle this and show meaningful message with instruction how to overcome this issue - delete cache_data.dat and restart cache.
> Handle ClassNotFoundException during deserialization of persisted cache configuration
> --------------------------------------------------------------------------------------
>
> Key: IGNITE-8162
> URL: https://issues.apache.org/jira/browse/IGNITE-8162
> Project: Ignite
> Issue Type: Improvement
> Components: general
> Affects Versions: 2.4
> Reporter: Ivan Rakov
> Priority: Major
> Fix For: 2.6
>
>
> Ticket is created according to dev list discussion: http://apache-ignite-developers.2346864.n4.nabble.com/Fwd-Data-Loss-while-upgrading-custom-jar-from-old-jar-in-server-and-client-nodes-td28808.html
> Cache configuration is serialized by JDK marshaller and persisted in cache_data.dat file. It may contain instances of classes that disappeared from runtime classpath (e.g. if implementation of CacheStore has been renamed). In such case, node will fail on start.
> We should handle this and show meaningful message with instruction how to overcome this issue - delete cache_data.dat and restart cache.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)