: I currently have Solr 4.3 set up with about 400 cores set to load upon
: start up. When starting Solr with an empty index for each core, Solr is
: able to load all of the cores and start up normally as expected.
: However, after running a dataimport on all cores and restarting Solr, it
: hangs at "org.apache.solr.core.CoreContainer; registering core: ..."
: without any type of error message in the log. The process still exists
: at this point, but doesn't make any progress even if left for a period
: of time. Prior to the restart, Solr continues to function normally, and
: is searchable.
When solr gets into this state, can you generate a thread dump, wait 20-30
seconds, generate another thread dump, and then send both to the list so
we can see what's going on at this point?
The easiest way to generate a threaddump is with jstack on the same
machine...
jstack <pid> >> threaddumps.log
: hang at the same spot. It does appear to be related to files to an
: extent, since removing the index/"data" directory of half of the cores
: does allow Solr to start up normally.
wild shot in the dark -- is it possible you have really large transaction
logs that are being replayed on startup, because you never did a hard
commit after indexing?
can you also include in your next email a listing of all the files in all
the data dirs of the affected solr instance, including file sizes?
something along the lines of this command output from your solr home
dir...
du -ab */data
?
-Hoss
