[
https://issues.apache.org/jira/browse/SOLR-13674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16902837#comment-16902837
]
ASF subversion and git services commented on SOLR-13674:
--------------------------------------------------------
Commit de522052c8b113a90613055585c864aa7bcdb300 in lucene-solr's branch
refs/heads/branch_8x from Shalin Shekhar Mangar
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=de52205 ]
SOLR-13674: NodeAddedTrigger does not support configuration of replica type
hint.
A new replicaType property has been added to NodeAddTrigger so that new
replicas of the given type are added when the preferredOp is addreplica. The
default value of replicaType is `NRT`.
This closes #821.
(cherry picked from commit ed137dbe281cfb314af340673a7b646922a2e7d1)
> NodeAddedTrigger does not support configuration of replica 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
> Assignee: Shalin Shekhar Mangar
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
