Glad to hear that! Thanks for closing this out.
Best,
Erick
On Sun, Nov 9, 2014 at 4:55 PM, Bruno Osiek wrote:
> Erick,
>
> Once again thank you very much for your attention.
>
> Now my pseudo-distributed SolrCloud is configured with no inconsistency. An
> additional problem was starting Jboss w
Erick,
Once again thank you very much for your attention.
Now my pseudo-distributed SolrCloud is configured with no inconsistency. An
additional problem was starting Jboss with "solr.data.dir" set to a path
not expected by Solr (actually it was not even underneath solr.home
directory).
This thre
OK, we're _definitely_ in the speculative realm here, so don't think
I know more than I do ;)...
The next thing I'd try is to go back to "native" as the lock type on the
theory that the lock type wasn't your problem, it was the too-frequent
commits.
bq: This file "_1.nvm" once existed. Was delete
Hi Erick,
Thank you very much for your reply.
I disabled client commit while setting commits at solconfig.xml as follows:
${solr.autoCommit.maxTime:30}
false
${solr.autoSoftCommit.maxTime:6}
The picture changed for the better. No more index c
First. for tweets committing every 500 docs is much too frequent.
Especially from the client and super-especially if you have multiple
clients running. I'd recommend you just configure solrconfig this way
as a place to start and do NOT commit from any clients.
1> a hard commit (openSearcher=false)
Hi,
I am a newbie SolrCloud enthusiast. My goal is to implement an
infrastructure to enable text analysis (clustering, classification,
information extraction, sentiment analysis, etc).
My development environment consists of one machine, quad-core processor,
16GB RAM and 1TB HD.
Have started impl
