[jira] [Commented] (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:comment-tabpanel=16744433#comment-16744433 ] Cassandra Targett commented on SOLR-12023: -- Did the commits here get straightened out? Is this in a release? Can it be resolved again? > 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, 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (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:comment-tabpanel=16677526#comment-16677526 ] ASF subversion and git services commented on SOLR-12023: Commit 6f6a880ec2126690bb363b2a591bed36c406caee in lucene-solr's branch refs/heads/master from [~noble.paul] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=6f6a880 ] SOLR-12023: correcting wrong git merge > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (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:comment-tabpanel=16674969#comment-16674969 ] ASF subversion and git services commented on SOLR-12023: Commit eb359ca0790af505debf33a57c3bfb18eecbab4e in lucene-solr's branch refs/heads/jira/http2 from [~noble.paul] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=eb359ca ] SOLR-12023: Autoscaling policy engine shuffles replicas needlessly > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (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:comment-tabpanel=16674345#comment-16674345 ] Noble Paul commented on SOLR-12023: --- Thanks [~shalinmangar] My push to master had failed . > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (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:comment-tabpanel=16674343#comment-16674343 ] ASF subversion and git services commented on SOLR-12023: Commit eb359ca0790af505debf33a57c3bfb18eecbab4e in lucene-solr's branch refs/heads/master from [~noble.paul] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=eb359ca ] SOLR-12023: Autoscaling policy engine shuffles replicas needlessly > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (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:comment-tabpanel=16668505#comment-16668505 ] Shalin Shekhar Mangar commented on SOLR-12023: -- [~noble.paul] - I see that the commit only fixes suggesting non-existent cores problem. What about the needlessly shuffling replicas -- is that already fixed? Also, where is the corresponding commit to master? > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (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:comment-tabpanel=16668501#comment-16668501 ] ASF subversion and git services commented on SOLR-12023: Commit 01c0172f40d43bfd2ea292069c385b1188ba5428 in lucene-solr's branch refs/heads/branch_7x from [~noble.paul] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=01c0172 ] SOLR-12023: Autoscaling policy engine shuffles replicas needlessly > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (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:comment-tabpanel=16667253#comment-16667253 ] Cassandra Targett commented on SOLR-12023: -- [~noble.paul], it should be reopened then? It's marked as Closed now. > 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 > > > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (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:comment-tabpanel=16667184#comment-16667184 ] Noble Paul commented on SOLR-12023: --- Apparently this is still a problem > 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 > > > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (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:comment-tabpanel=16373885#comment-16373885 ] Shalin Shekhar Mangar commented on SOLR-12023: -- Here is the full patch from SOLR-11066 with TriggerIntegrationTest.testScheduledTrigger that demonstrates the problem. > 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 >Priority: Major > Fix For: master (8.0), 7.3 > > Attachments: SOLR-11066-failing.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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org