Re: Configuration of parallel indexing threads

Thanks a lot! -- View this message in context: http://lucene.472066.n3.nabble.com/Configuration-of-parallel-indexing-threads-tp4338466p4339792.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: cursorMark value causes Request-URI Too Long excpetion

Thanks, that was my assumption as well that all parameters should are supported by both GET and POST. However, when using JSON API I keep getting 400 error code: /Request/: {"query":"*","cursorMark":"*","sort":"id asc"} /Response/: {"responseHeader":{"status":400,"QTime":0,"params":{"fl":"id","js

Re: cursorMark value causes Request-URI Too Long excpetion

Thanks a lot. I didn't think of switching to application/x-www-form-urlencoded content type. It solved my issue :) -- View this message in context: http://lucene.472066.n3.nabble.com/cursorMark-value-causes-Request-URI-Too-Long-excpetion-tp4335472p4335691.html Sent from the Solr - User mailing

Configuration of parallel indexing threads

During performance testing a question was raised whether Solr indexing performance could be improved by adding more concurrent index writer threads. I discovered traces of such functionality here , but not sure how to use it in Solr 6.2. Hopefully

Re: Configuration of parallel indexing threads

Thanks for the replies. Just to confirm that I got it right: 1. Since there is no setting to control index writers, is it fair to assume that Solr always indexes at maximum possible speed? 2. The way to control write speed is to control number of clients that are simultaneously posting data, right?