Thanks, Shawn. I am a bit wary of creating a total core just for this
health check purpose.
Isn't it a bit expensive to create a core, considering the caches and so
many things it registers? Or, is it fine in which case I might just proceed
with that solution.
On Sat, Nov 19, 2022 at 6:00 AM Shawn
We are good. one of our engineers upgraded java without stopping solr.
After restarting the solr on the leader node (with new JRE) the
replication worked.
On Sat, Nov 19, 2022 at 7:40 AM Hari Nakka wrote:
> I see this error in the leader node.
>
> 2022-11-19 04:23:21.600 ERROR (qtp110053477-21
I see this error in the leader node.
2022-11-19 04:23:21.600 ERROR (qtp110053477-2178276) [c:c_facilities_a
s:shard1 r:core_node18 x:c_facilities_a_shard1_replica_n17]
o.a.s.s.HttpSolrCall java.lang.RuntimeException:
java.lang.NoClassDefFoundError: Co
uld not initialize class java.util.zip.Adler3
We have solr8.9 cluster running on 5 nodes. We were in the middle of
patching and rebooting the nodes. Couple of collections failed to recover
after the restart.
Below is the exception in the logs
=
2022-11-19 04:02:21.680 ERROR
(recoveryExecutor-11-thread-1-processing-x:c_facilities_a_s
We have solr8.9 cluster running on 5 nodes. We were in the middle of
patching and rebooting the nodes. Couple of collections failed to recover
after the restart.
Below is the exception in the logs
lica_n23/data/index.20221119040221652
lockFactory=org.apache.lucene.store.NativeFSLockFactory@7342a
On 11/17/22 22:05, gnandre wrote:
Unfortunately, I am still on legacy mode and not cloud mode.
So, I can't take advantage of this feature :(
In the meantime, I have implemented the Solr plugin and it is working as
expected but the only issue is that it needs to be called in the
context of
some
