[
https://issues.apache.org/jira/browse/SOLR-17210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl resolved SOLR-17210.
--------------------------------
Resolution: Information Provided
Hi, thanks for providing this information. This sounds more like a support
request rather than a bug report, and thus opening a discussion thread on the
[us...@solr.apache.org|mailto:us...@solr.apache.org] mailing list (see
[https://solr.apache.org/community.html#mailing-lists-chat)] is the best way
forward for you to get help and for us to understand your use case. When you
reach out to the list, please provide more context on your install. We already
know that you use v9.1.1 in Kubernetes on Amazon, and use TRA collection.
Things to include in the mail: Do you use the Solr Operator, or a 3rd party
Solr Helm cart, or have you rolled your own deploy? The PODs that are
restarted weekly, do they remain down or do they come up again on same host
names? If using Solr-Operator it will take care of stable service names for
each node.
I will close this Jira now, but if the mailing list discussion uncovers a
likely bug or the need for a new feature, we may re-open this or create one or
more new JIRAs to handle.
> Index Fetch Failed Issue in Solr
> ---------------------------------
>
> Key: SOLR-17210
> URL: https://issues.apache.org/jira/browse/SOLR-17210
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: replication (java), replication (scripts)
> Affects Versions: 9.1.1
> Reporter: NAGARAJAN S
> Priority: Major
>
> Hi Team
> I deployed 10 Solr and 3 zookeeper nodes in AKS. Each solr of capacity 6 CPU
> and 32 GB JVM and disk of 4 TB per solr and 40 TB shared. Our disk is only 5
> to 10% utilized.
> We are following TRA collection on daily basis each daily collection do have
> 5 shards. We are taking backup using Solr Backup APIs.Our solr is storing 150
> Million data per day.
>
> each Shards with two replicas. For a collection, shards are following the
> default Simple Placement Factory. Replicas are placed in sorted list of nodes.
> However, solr pods are getting restarted on weekly basis on AKS. which causes
> some of the shards on the restarted pods are not coming up it is in
> Down/recovery failed/recovery. We had to manually delete and create replica
> in order to fix it which incurred data loss.
> There are four issues
>
> # If replica is down, solr does not automatically add replicas in other
> available nodes.. autoaddreplicas is deprecated from Solr 9. We are not sure
> what to use for automatically add replicas.
> # Our frequently occuring errors related to replication in solr logs are
> below
> o.a.s.c.RecoveryStrategy Error while trying to recover =>
> org.apache.solr.common.SolrException: Replication for recovery failed.
> 3. our frequently occuring errors related to index in solr logs are below
> o.a.s.h.ReplicationHandler Index fetch failed =>
> org.apache.solr.common.SolrException: Index fetch failed :
> 4. Shutdown log line
> o.a.s.s.HttpSolrCall Unable to write response, client closed connection or we
> are shutting down => org.eclipse.jetty.io.EofException: Closed
>
> Please provide your suggestions to fix the issue
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
