[
https://issues.apache.org/jira/browse/SOLR-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14945218#comment-14945218
]
Noble Paul commented on SOLR-8117:
----------------------------------
bq.This type of condition (<1) should be considered as invalid. I misunderstood
the rule configuration.
So far I have not put in any checks for "impossible" conditions
bq.By the way, the behavior should always be the same.
Yes, it should be. IIRC the state of the system is printed out if the rules
fail and it should be possible to debug it easily.
This should always pass , because for a given shard there can be a max of 1
replica in a host. You have four hosts. It requires only 14 nodes as per your
rule {{cores:<2}} and you have 16 nodes. So , it should always pass.
I guess it has something to do with the order the nodes are assigned. It'll be
great if we could write a testcase with the same data
> Rule-based placement issue with 'cores' tag
> --------------------------------------------
>
> Key: SOLR-8117
> URL: https://issues.apache.org/jira/browse/SOLR-8117
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 5.3, 5.3.1
> Reporter: Ludovic Boutros
> Assignee: Noble Paul
> Attachments: SOLR-8117.patch
>
>
> The rule-based placement fails on an empty node (core count = 0) with
> condition 'cores:<1'.
> It also fails if current core number is equal to the core number in the
> condition - 1.
> During the placement strategy process, the core counts for a node are
> incremented when all the rules match.
> At the end of the code, an additional verification of all the conditions is
> done with incremented core count and therefore it fails.
> I don't know why this additional verification is needed and removing it seems
> to fix the issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
