RE: Updates to index not available immediately as index scales, even with autoSoftCommit at 1 second

Thanks for the explanation. This makes a lot of sense to me... I'm wondering if there's a way to get the best of both worlds. Can throwing more hardware at the index give real time updates + a large LRU cache? Would we be CPU bound at this point? -- View this message in context:

Updates to index not available immediately as index scales, even with autoSoftCommit at 1 second

I've been trying to debug through this but I'm stumped. I have a Solr index with ~40 million documents indexed currently sitting idle. I update an existing document through the web interface (collection1 - Documents - /update) and the web request returns successfully. At this point, I expect

Re: Updates to index not available immediately as index scales, even with autoSoftCommit at 1 second

I'm not seeing any messages in the log with respect to cache warming at the time, but I will investigate that possibility. Thank you. In case it is helpful, I pasted the entire solrconfig.xml at http://pastebin.com/C0iQ7E9a -- View this message in context:

Re: Updates to index not available immediately as index scales, even with autoSoftCommit at 1 second

Immediately after triggering the update, this is what is in the logs: /2014-08-12 12:58:48,774 | [71] | 153414367 [qtp2038499066-4772] INFO org.apache.solr.update.processor.LogUpdateProcessor – [collection1] webapp=/solr path=/update params={wt=json} {add=[52627624 (1476251068652322816)]} 0 34

Error from SPLITSHARD that seems to be unrecoverable

I'm using Solr 4.6 with SolrCloud. I tried using the SPLITSHARD command and it threw a series of exceptions, which have put my SolrCloud in a weird state. Here is an image of my SolrCloud setup after a few tries at SPLITSHARD, all of which fail. http://imgur.com/CFXJKfb Here is the log

Errors on index in SolrCloud: ConcurrentUpdateSolrServer$Runner.run()

I have a SolrCloud index with ~5 million documents, which I'm committing to with SolrNet, 1000 documents at a time. I'm able to query just fine, but indexing new documents is causing Solr to throw the following exception every time: ERROR - 2013-12-18 20:27:05.750;

How to programatically unload a shard from a single server to horizontally scale on SolrCloud

I'm writing a script so that when my SolrCloud setup is slowing down, I can add a new physical machine and run a script to split the shard with the most data and send half of the shard to the new machine. Here's the general thinking I'm following: - Pick the machine with the most data currently

Re: How to programatically unload a shard from a single server to horizontally scale on SolrCloud

Thanks Michael. I didn't realize the cores and collections APIs were interchangeable like that. I'd assumed that the cores API was meant for vanilla Solr, while Collections was specific to SolrCloud. I appreciate you clarifying that. Thanks. -- View this message in context: