[ 
https://issues.apache.org/jira/browse/SOLR-13674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16902864#comment-16902864
 ] 

Irena Shaigorodsky commented on SOLR-13674:
-------------------------------------------

[~shalinmangar], will it be possible to merge the change in branch_7x as well? 
This is the version that is currently in use for me.

> 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) 
>          Components: AutoScaling
>    Affects Versions: 7.6
>            Reporter: Irena Shaigorodsky
>            Assignee: Shalin Shekhar Mangar
>            Priority: Major
>             Fix For: master (9.0), 8.3
>
>          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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to