Closed (won't fix)
Project:
Apache Solr Search
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
6 Jun 2008 at 15:10 UTC
Updated:
2 Dec 2021 at 16:22 UTC
Jump to comment: Most recent
Comments
Comment #1
janusman commentedI think the recommended process is, do all of your steps but adding these between 4 and 5:
4.a) Shut down Solr
4.b) completely erase the example/solr/data directory in your apachesolr. (in Unix: cd example/solr; rm -rf data)
4.c) Restart Solr
Comment #2
robertdouglass commentedCan't reproduce. janusman's extra steps are correct if you want to totally erase any trace of old content.
One thing that might be happening is that if you have core's search enabled, all of those nodes have to be reindexed as well, so you might have to run cron several times (usually with the typical delay while node module indexes) before ApacheSolr gets its turn.
Comment #3
satishraj commentedThanks for the suggestion it worked for me as when i restarted my web server,
Thanks Once again from rajj:)
Comment #4
ragapriya commentedHi team

We are trying to re-index. But it is not processing after certain percentage.
Even tried restarting the web server & increasing the memory limit but still no luck. Console error -Screenshot attached for your reference
Can you please help in a way to re-index?