[jira] [Commented] (SOLR-13674) NodeAddedTrigger does not support configuration of replica type hint
[ 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
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16900414#comment-16900414 ] Irena Shaigorodsky commented on SOLR-13674: --- [~shalinmangar], I fixed the test case. > 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 >Assignee: Shalin Shekhar Mangar >Priority: Major > Time Spent: 10m > 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
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16899345#comment-16899345 ] Irena Shaigorodsky commented on SOLR-13674: --- https://github.com/apache/lucene-solr/pull/821 > 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 > Time Spent: 10m > 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
[jira] [Created] (SOLR-13674) NodeAddedTrigger does not support configuration of relica type hint
Irena Shaigorodsky created SOLR-13674: - Summary: 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) Reporter: Irena Shaigorodsky 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
[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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-13591) AlreadyClosedException in SolrJ
[
https://issues.apache.org/jira/browse/SOLR-13591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890369#comment-16890369
]
Irena Shaigorodsky commented on SOLR-13591:
---
Experienced a similar issue:
{code:java}
org.apache.solr.client.solrj.SolrServerException:
org.apache.solr.common.AlreadyClosedException
at
org.apache.solr.client.solrj.impl.CloudSolrClient.requestWithRetryOnStaleState(CloudSolrClient.java:1002)
{code}
The issue happens with SolrJ 7.6, 7.7.2, 8.8.1, and httpclient library over
than 4.5.3. Downgrading to 4.5.5 resolves the problem. The error looks like
HTTP client issue.
> AlreadyClosedException in SolrJ
> ---
>
> Key: SOLR-13591
> URL: https://issues.apache.org/jira/browse/SOLR-13591
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
>Affects Versions: 8.1.1
>Reporter: Markus Jelsma
>Priority: Major
> Fix For: master (9.0), 8.2
>
>
> Since upgrading from 7.7 to 8.1, we regulary get the following exception in
> SolrJ. The message is null, the stack trace is:
> {code}
> org.apache.solr.common.AlreadyClosedException
> at
> org.apache.solr.client.solrj.impl.ZkClientClusterStateProvider.getZkStateReader(ZkClientClusterStateProvider.java:165)
> at
> org.apache.solr.client.solrj.impl.ZkClientClusterStateProvider.connect(ZkClientClusterStateProvider.java:160)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.connect(BaseCloudSolrClient.java:329)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.requestWithRetryOnStaleState(BaseCloudSolrClient.java:779)
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.request(BaseCloudSolrClient.java:769)
> at
> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:207)
> at org.apache.solr.client.solrj.SolrClient.query(SolrClient.java:987)
> at org.apache.solr.client.solrj.SolrClient.query(SolrClient.java:1002)
> {code}
> The clients are always 8.1.1, the servers are either 7.5 or 8.1.1. There are
> no indications in the server logs, although they are set to log level WARN.
> We run Zookeeper 3.4.13.
--
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
