You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2018/11/06 17:46:00 UTC

[jira] [Reopened] (SOLR-12023) Autoscaling policy engine shuffles replicas needlessly and can also suggest nonexistent replicas to be moved

     [ https://issues.apache.org/jira/browse/SOLR-12023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hoss Man reopened SOLR-12023:
-----------------------------

Noble: what the heck happened with your push to master?  did you just force push an old commit????

eb359ca0790af505debf33a57c3bfb18eecbab4e broke a tone of stuff in CHANGES.txt -- including removing the entire 8.0 section, and deleting/moving a bunch of stuff going back as far as 7.3!?!

https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;a=blobdiff;f=solr/CHANGES.txt;h=be31fe7f4793fd27f1213779bc0880281fa9c1df;hp=90cce5b27f9b770ceb85a9c4a10b4979041a8b05;hb=eb359ca;hpb=f669a1fb0e1ff974df93229c41cd397956cb1e9a

> Autoscaling policy engine shuffles replicas needlessly and can also suggest nonexistent replicas to be moved
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-12023
>                 URL: https://issues.apache.org/jira/browse/SOLR-12023
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: AutoScaling, SolrCloud
>            Reporter: Shalin Shekhar Mangar
>            Assignee: Noble Paul
>            Priority: Major
>             Fix For: 7.6, master (8.0)
>
>         Attachments: SOLR-11066-failing.patch, SOLR-12023.patch
>
>
> A test that I wrote in SOLR-11066 found the following problem:
> Cluster: 2 nodes
> Collection: 1 shard, 3 replicas, maxShardsPerNode=5
> No autoscaling policy or preference applied
> When the trigger runs, the computed plan needlessly shuffles all three replicas and then proceeds to return suggestions with only numbers as core names. These cores do not exist. I found that these numbers are generated internally by the framework as placeholders for moved cores for further calculations. They should never ever be suggested to the users.



--
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