You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitry Karachentsev (JIRA)" <ji...@apache.org> on 2018/07/16 12:47:00 UTC
[jira] [Created] (IGNITE-9011) RendezvousAffinity.excludeNeighbors
should be removed and be a default behavior
Dmitry Karachentsev created IGNITE-9011:
-------------------------------------------
Summary: RendezvousAffinity.excludeNeighbors should be removed and be a default behavior
Key: IGNITE-9011
URL: https://issues.apache.org/jira/browse/IGNITE-9011
Project: Ignite
Issue Type: Improvement
Components: cache
Affects Versions: 2.6
Reporter: Dmitry Karachentsev
Fix For: 3.0
According to this [discussion | http://apache-ignite-developers.2346864.n4.nabble.com/Neighbors-exclusion-td32550.html], cache backup distribution should be more straightforward.
Right now we have not obvious logic on how backups will be stored across nodes. For example:
1. If set nodeFilter, it will filter backup nodes and if there are not enough nodes there will be less backups...
2. If set property excludeNeighbors, it will ignore manually set backupFilter.
3. By default excludeNeighbors is false.
There seems no need to keep excludeNeighbors property at all and it should be removed. Instead, node always must do the best to distribute backups to different machines.
If user set backupFilter, it must be used, otherwise distribute backups to other machines if it's possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)