ashimbose,
It is possible that this is happening because Solr reaches a point where
it is doing so many simultaneous merges that ongoing indexing is stopped
until a huge merge finishes. This causes the JDBC driver to time out
and disconnect, and there is no viable generic way to recover from that
problem.
I used to run into this with large MySQL imports. If this is what's
happening, the following change/addition in the mergeScheduler section
of indexConfig in solrconfig.xml will fix it:
<mergeScheduler class="org.apache.lucene.index.ConcurrentMergeScheduler">
<int name="maxThreadCount">1</int>
<int name="maxMergeCount">6</int>
</mergeScheduler>
If that doesn't fix it, then I would look for a problem with either your
JDBC driver or your DB server.
Thanks,
Shawn
On 1/17/2013 7:19 AM, Otis Gospodnetic wrote:
Hi,
It looks like this is the cause:
JBC0016E: Remote call failed
(return code=-2,220). SDK9019E: internal error SDK9019X:
Interestingly, Google gives just 1 hit for the above as query - your post.
But it seems you should look up what the above codes mean first...
Otis
--
Solr & ElasticSearch Support
http://sematext.com/
On Thu, Jan 17, 2013 at 2:43 AM, ashimbose <ashimb...@gmail.com> wrote:
I am trying to index large data (not rich document) about 5GB, but Its not
getting index. In case of small data it's perfectly indexing.For Large data
import XML response..
