[ 
https://issues.apache.org/jira/browse/IGNITE-8162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440688#comment-16440688
 ] 

ASF GitHub Bot commented on IGNITE-8162:
----------------------------------------

GitHub user dgarus opened a pull request:

    https://github.com/apache/ignite/pull/3841

    IGNITE-8162 Handle ClassNotFoundException during deserialization of 
persisted cache configuration

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/dgarus/ignite ignite-8162

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/3841.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3841
    
----
commit fd28f4bef77f4e8d4d94290de598f156f60e1e50
Author: denis.garus <d.garus@...>
Date:   2018-04-17T09:41:30Z

    IGNITE-8162 Show meaningful message with instruction how to overcome 
ClassNotFoundException during deserialization of persisted cache configuration

commit 9b84851a9cbbd89ec1d9e901e83a95afdc67f9e4
Author: denis.garus <d.garus@...>
Date:   2018-04-17T09:52:28Z

    Merge branch 'master' of https://github.com/apache/ignite into ignite-8162

----


> 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
>            Assignee: Denis Garus
>            Priority: Major
>              Labels: newbie
>             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)

Reply via email to