Right, as Michael says you've allocated a massive amount of memory. I suspect you're just hitting a full-pause garbage collection and it's taking a loooong time. Do you know whether you actually need all that memory or was it allocated on the theory that "more is better"?
We often recommend that you _start_ with about 1/2 the memory to the JVM and the rest to the OS. In your case, I'd back that off even more unless you have evidence that this much memory is required. Best Erick On Thu, Jul 12, 2012 at 8:54 AM, Michael Della Bitta <michael.della.bi...@appinions.com> wrote: > Hi, Jason, > > That's a huge heap. Which Directory implementation are you using? It > might make more sense to drastically reduce that heap and let the OS > buffer the index at a lower level. > > Michael Della Bitta > > ------------------------------------------------ > Appinions, Inc. -- Where Influence Isn’t a Game. > http://www.appinions.com > > > On Wed, Jul 11, 2012 at 10:05 PM, Jason <hialo...@gmail.com> wrote: >> Hi Erick >> Our physical memory is 128g and jvm option is -Xms110g -Xmx110g >> -XX:PermSize=512m -XX:MaxPermSize=512m >> This is very huge memory allocation. >> But we are servicing patent search and that is accepted very complex queries >> used memory. >> >> >> -- >> View this message in context: >> http://lucene.472066.n3.nabble.com/shard-connection-timeout-tp3994301p3994556.html >> Sent from the Solr - User mailing list archive at Nabble.com.
