[
https://issues.apache.org/jira/browse/IGNITE-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956539#comment-15956539
]
Semen Boikov commented on IGNITE-4667:
--------------------------------------
Hi Dmitry,
Reviewed your changes, have some comments:
- please add more tests so that all cache modes are tested:
transactional/atomic + near cache enabled/disabled
- I think you need catch/handle cache init exception on more higher level -
inside CacheAffinitySharedManager.onCacheChangeRequest (prepareCacheStart can
finish without errors, but after this initAffinity can fail)
- also I think it is better to finish cache statr futures in single place, now
this is done in GridCacheProcessor.onExchangeDone, let's just change it to
finish future with error if 'err' != null
Thanks!
> Throw exception on starting client cache when indexed types cannot be loaded
> ----------------------------------------------------------------------------
>
> Key: IGNITE-4667
> URL: https://issues.apache.org/jira/browse/IGNITE-4667
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.8
> Reporter: Dmitry Karachentsev
> Assignee: Dmitry Karachentsev
> Fix For: 2.0
>
>
> Assume following situation:
> 1. Server node configured cache indexed types with classes that client node
> doesn't have.
> 2. Start server.
> 3. Start client. Client successfully connected.
> 4. Try to get cache on client node.
> 5. Was thrown exception in GridQueryProcessor and request for cache on client
> node hangs forever.
> If on some reason cache couldn't be initialized, exception must be thrown on
> Ignite.cache() operation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
