[
https://issues.apache.org/jira/browse/IGNITE-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16154526#comment-16154526
]
Valentin Kulichenko commented on IGNITE-2096:
---------------------------------------------
[~yzhdanov], that's correct, issue here is non intuitive exceptions. For
example, if I provide different number of backups for {{AtomicConfiguration}},
I get this:
{noformat}
class org.apache.ignite.IgniteCheckedException: Affinity key backups mismatch
(fix affinity key backups in cache configuration or set
-DIGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK=true system property)
[cacheName=ignite-atomics-sys-cache, localAffinityKeyBackups=2,
remoteAffinityKeyBackups=1, rmtNodeId=440e4806-1e43-4da4-9a11-814e56d89e89]
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.checkAttributeMismatch(GridCacheUtils.java:1084)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.checkCache(GridCacheProcessor.java:2986)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:768)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:978)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1814)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1605)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1042)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:569)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:516)
at org.apache.ignite.Ignition.start(Ignition.java:322)
at AtomicConfigTest.main(AtomicConfigTest.java:25)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
{noformat}
Exception refers to internal cache and doesn't explain what actually happened
and how it should be fixed.
> AtomicConfiguration and CollectionConfiguration should be properly checked
> for consistency
> ------------------------------------------------------------------------------------------
>
> Key: IGNITE-2096
> URL: https://issues.apache.org/jira/browse/IGNITE-2096
> Project: Ignite
> Issue Type: Bug
> Components: data structures
> Reporter: Valentin Kulichenko
> Labels: newbie, usability
>
> Currently {{AtomicConfiguration}} and {{CollectionConfiguration}} are mapped
> to system caches configuration and consistency is checked like for any other
> cache. This leads to unintuitive errors.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
