No, I just add the documents, call commit() and wait for the response.

Now I made a workaround where I put each commit() in a separate thread,
which I wait for (Thread#join(long)) and recommit the documents if
the Thread didn't end within a given amount of time.
This way I am able to commit all documents - during uploading 15.000.000
documents 5 or 6 retries were necessary - but probably the
Threads all go on for eternity, which isn't that good I reckon,
even though they don't seem to do anything at all.

Not a very satisfactory solution. :(


zayhen wrote:
> 
> Are you using any postCommit postOptimize eventListener?
> 
> I got some problems using them, that I run on scenario where the
> commit/optimize thread never ended.
> 
> 2008/8/26 Machisuji <[EMAIL PROTECTED]>
> 
>>
>> Hey.
>>
>> I've been working with SolR for a few days now and as long as I haven't
>> worked with
>> too much data everything was alright.
>>
>> However, now that I wanted to index really all data, I've got problems
>> with
>> SolrJ
>> not returning from a call to CommonHttpSolrServers's commit().
>> I try to upload data from online shops, to be more precise name,
>> category,
>> price and description of tens of millions of items.
>> After a few million items the call of commit() doesn't return anymore and
>> simply does nothing.
>> At least the cpu usage on the computer running the solr server falls to
>> 0%.
>>
>> I always add 10,000 items at a time by calling
>> SolrServer#add(Collection<SolrInputDocument>) followed by
>> SolrServer.commit().
>> Has someone an idea what could be the problem here?
>> --
>> View this message in context:
>> http://www.nabble.com/SolrJ---SolrServer-commit%28%29-doesn%27t-return-tp19161293p19161293.html
>> Sent from the Solr - User mailing list archive at Nabble.com.
>>
>>
> 
> 
> -- 
> Alexander Ramos Jardim
> 
> 
> -----
> RPG da Ilha 
> 

-- 
View this message in context: 
http://www.nabble.com/SolrJ---SolrServer-commit%28%29-doesn%27t-return-tp19161293p19165657.html
Sent from the Solr - User mailing list archive at Nabble.com.

Reply via email to