Wild shot here: two Solr instances started on the same data directory? Best regards, Radu -- Sematext Cloud - Full Stack Observability - https://sematext.com Solr and Elasticsearch Consulting, Training and Production Support
> On 1 Dec 2020, at 06:25, sambasivarao giddaluri > <sambasiva.giddal...@gmail.com> wrote: > > when checked in to opt/solr/volumes/data/cores/ both > k04o95kz_shard2_replica_n10 and k04o95kz_shard3_replica_n16 replicate are not > present no idea how they got deleted. > > On Mon, Nov 30, 2020 at 4:13 PM sambasivarao giddaluri > <sambasiva.giddal...@gmail.com> wrote: > Hi All, > We are getting below exception from Solr where 3 zk with 3 solr nodes and 3 > replicas. It was working fine and we got this exception unexpectedly. > > • k04o95kz_shard2_replica_n10: > org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: > Index dir > '/opt/solr/volumes/data/cores/k04o95kz_shard2_replica_n10/data/index.20201126040543992' > of core 'k04o95kz_shard2_replica_n10' is already locked. The most likely > cause is another Solr server (or another solr core in this server) also > configured to use this directory; other possible causes may be specific to > lockType: native > • k04o95kz_shard3_replica_n16: > org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: > Index dir > '/opt/solr/volumes/data/cores/k04o95kz_shard3_replica_n16/data/index.20201126040544142' > of core 'k04o95kz_shard3_replica_n16' is already locked. The most likely > cause is another Solr server (or another solr core in this server) also > configured to use this directory; other possible causes may be specific to > lockType: native > > > > > > > Any advice > > Thanks > sam
