Did you check the number of documents that end up on each shard in these two scenarios.
My guess would be that - perhaps - low entropy key puts most of the documents into one shard and high-entropy key causes a lot more routing traffic with delay coming from the network communication and/or confirmation. Maybe even combined with the very low commit values. I am not a SolrCloud specialist. But that's one place I can see the entropy of the key becoming a factor. Regards, Alex. ---- http://www.solr-start.com/ - Resources for Solr users, new and experienced On 30 March 2017 at 11:57, moscovig <mosco...@gmail.com> wrote: > Hi > > Yes it is solrCloud, we saw the same behavior with 1,2 and 4 shards. each > shard has 3 replicas. > > Each bulk contains 300 docs. We get approximately 800 docs inserted in a > second. > > ~6000 docs are being sent in an iteration by all loading threads. > we have 20 threads, each sending bulks of 300 docs. > > The loaders are waiting for the response, > which gets back after ~10 seconds for a loader. > > Thanks! > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/slow-indexing-when-keys-are-verious-tp4327681p4327714.html > Sent from the Solr - User mailing list archive at Nabble.com.
