The load test was fairly heavy (ie lots of users) and designed to mimic a fully operational system with lots of users doing normal things.
There were two things I gleaned from the logs: PERFORMANCE WARNING: Overlapping onDeckSearchers=2 appeared for several of my more active cores and The non-leaders were throwing errors saying that the leader as not responding while trying to forward updates. (sorry can't find that specific error now) My best guess is that it has something to do with the commits. a. frequent user generated writes using /update?commitWithin=500&waitFlush=false&waitSearcher=false b. softCommit set to 3000 c. autoCommit set to 300,000 and openSearcher false d. I'm also doing frequent periodic DIH updates. I guess this is commit=true by default. Should I omit commitWithin and set DIH to commit=false and just let soft and autocommit do their jobs? Cheers, Jim -- View this message in context: http://lucene.472066.n3.nabble.com/Some-nodes-have-all-the-load-tp4046349p4046476.html Sent from the Solr - User mailing list archive at Nabble.com.
