[
https://issues.apache.org/jira/browse/SOLR-13674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16902874#comment-16902874
]
Shalin Shekhar Mangar commented on SOLR-13674:
----------------------------------------------
The 7x branch has been made protected to reject any commits. See
https://issues.apache.org/jira/browse/INFRA-18192. This is due to back-compat
issues that make it almost impossible to release a new minor version from the
7x branch.
This change can be back-ported to branch_7_7 (and to branch_8_2) in case a new
bug fix release (7.7.3 or 8.2.1) is required but none of them are in plans
today.
Would it be okay if you cherry-picked the commit to 7x on your private repos
instead?
> 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: [email protected]
For additional commands, e-mail: [email protected]
