Unfortunately as developers we have no access to the actual solr nodes, and
certainly no privileges to delete stuff, even in the development
environment.
On Fri, Oct 6, 2017 at 1:34 PM, Erick Erickson
wrote:
> for future reference, a less harsh way to fix it would be to
> > stop the Solr instanc
for future reference, a less harsh way to fix it would be to
> stop the Solr instance where the replica resides
> rm -rf SOLR_HOME/collection1_replia1_shard1
where "collection1_replica1_shard1" is the directory of the replica in
question, you should see a "core.properties" file in that directory..
The replica was deleted using the deleteReplica collections API call. The
call timed out, but eventually completed. However something still held a
write lock, and it was still held a day later, but the replica was removed
as far as we could tell in the solr admin console.
Since it was a developmen
Hi,
How did you delete replica? Did you see any errors in logs after deleting? How
did/does it look from ZK perspective after deleting that replica?
Thanks,
Emir
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training - http://sematext.com/
