You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Irena Shaigorodsky (JIRA)" <ji...@apache.org> on 2019/08/01 19:57:00 UTC
[jira] [Updated] (SOLR-13674) NodeAddedTrigger does not support
configuration of relica type hint
[ https://issues.apache.org/jira/browse/SOLR-13674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Irena Shaigorodsky updated SOLR-13674:
--------------------------------------
Affects Version/s: 7.6
> NodeAddedTrigger does not support configuration of relica type hint
> -------------------------------------------------------------------
>
> Key: SOLR-13674
> URL: https://issues.apache.org/jira/browse/SOLR-13674
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 7.6
> Reporter: Irena Shaigorodsky
> Priority: Major
>
> The current code org.apache.solr.cloud.autoscaling.ComputePlanAction#getNodeAddedSuggester only sets COLL_SHARD hint, as a result any added replica will be NRT one.
> Our current setup has TLOG nodes on physical hardware and PULL nodes on k8s that are recycled periodically. An attempt to add those will bring the nodes in the cluster as NRT one.
> The root cause is org.apache.solr.client.solrj.cloud.autoscaling.AddReplicaSuggester#tryEachNode that expects to find the hint REPLICATYPE and defaults to NRT one.
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org