[
https://issues.apache.org/jira/browse/SOLR-14409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Bialecki updated SOLR-14409:
------------------------------------
Priority: Critical (was: Major)
> Existing violations allow bypassing policy rules when adding new replicas
> -------------------------------------------------------------------------
>
> Key: SOLR-14409
> URL: https://issues.apache.org/jira/browse/SOLR-14409
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: AutoScaling
> Affects Versions: master (9.0), 8.5, 8.6
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Critical
> Attachments: SOLR-14409.patch
>
>
> Steps to reproduce:
> * start with an empty cluster policy.
> * create a collection with as many replicas as there are nodes.
> * add one more replica to any node. Now this node has two replicas, all
> other nodes have one.
> * define the following cluster policy:
> {code:java}
> { 'set-cluster-policy': [ {'replica': '<2', 'shard': '#ANY', 'node': '#ANY',
> 'strict': true} ] } {code}
> This automatically creates a violation because of the existing layout.
> * try adding one more replica. This should fail because no node satisfies
> the rules (there must be at most 1 replica per node). However, the command
> succeeds and adds replica to the node that already has 2 replicas, which
> clearly violates the policy and makes matters even worse.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
