You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Cassandra Targett (JIRA)" <ji...@apache.org> on 2018/10/01 16:59:00 UTC
[jira] [Commented] (SOLR-12511) Support non integer values for
replica in autoscaling rules
[ https://issues.apache.org/jira/browse/SOLR-12511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16634319#comment-16634319 ]
Cassandra Targett commented on SOLR-12511:
------------------------------------------
[~noble.paul], Shouldn't this be resolved and marked as fixed in 7.5?
> Support non integer values for replica in autoscaling rules
> -----------------------------------------------------------
>
> Key: SOLR-12511
> URL: https://issues.apache.org/jira/browse/SOLR-12511
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: AutoScaling
> Reporter: Noble Paul
> Assignee: Noble Paul
> Priority: Major
>
> This means the user can configure a decimal value in replica
> example :
> {code:json}
> {"replica": 1.638, "node":"#ANY"}
> {code}
> This means a few things. The no:of of replicas in a node can be either 2 or 1. This also means that violations are calculated as follows
> * If the replica count is 1 or 2 there are no violations
> * If the replica count is 3, there is a violation and the delta is *{{3-1.638 = 1.362}}*
> * if the replica count is 0, there is a violation and the delta is *{{1.638 - 0 = 1.638}}*
> * This also means that the node with zero replicas has a *more serious* violation and the system would try to rectify that first before it address the node with 3 replicas
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org