[
https://issues.apache.org/jira/browse/IGNITE-6716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16615108#comment-16615108
]
matt hoffman commented on IGNITE-6716:
--------------------------------------
Documenting the properties that must be the same is helpful, I guess, but
that's not the root if this issue. In this case, all nodes have identical
configuration – the Ignite configuration is done in code, and all nodes have
identical code deployed. No property involving anything like # of replicas or #
of backups can be different between nodes.
> Document "Affinity key backups mismatch" resolution steps
> ---------------------------------------------------------
>
> Key: IGNITE-6716
> URL: https://issues.apache.org/jira/browse/IGNITE-6716
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
> Reporter: Nicholas DiPiazza
> Assignee: Artem Budnikov
> Priority: Major
> Fix For: 2.8
>
>
> Please see the issue below:
> https://stackoverflow.com/questions/46894435/how-do-i-fix-affinity-key-backups-in-cache-configuration
> results in this error:
> {code}
> 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)
> {code}
> Can someone help me get the steps in order to fix this issue? we should add
> it to the documentation somewhere.
> # What causes this error?
> # How to fix this error?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
