Shawn, Only my web application access this solr. at a first look at http server logs I didnt find something different. Sometimes I have a very big crawler access to my servers, this was my first bet.
No scheduled crons running at this time too. I think that I will reconfigure my boxes with two solr nodes each instead of four and increase heap to 16GB. This box only run Solr and has 64Gb. Each Solr will use 16Gb and the box will still have 32Gb for the OS. What do you think? This is a production server, so I will plan to migrate. Regards, Koji Em ter, 13 de ago de 2019 às 12:58, Shawn Heisey <apa...@elyograg.org> escreveu: > On 8/13/2019 9:28 AM, Kojo wrote: > > Here are the last two gc logs: > > > > > https://send.firefox.com/download/6cc902670aa6f7dd/#Ee568G9vUtyK5zr-nAJoMQ > > Thank you for that. > > Analyzing the 20MB gc log actually looks like a pretty healthy system. > That log covers 58 hours of runtime, and everything looks very good to me. > > https://www.dropbox.com/s/yu1pyve1bu9maun/gc-analysis-kojo.png?dl=0 > > But the small log shows a different story. That log only covers a > little more than four minutes. > > https://www.dropbox.com/s/vkxfoihh12brbnr/gc-analysis-kojo2.png?dl=0 > > What happened at approximately 10:55:15 PM on the day that the smaller > log was produced? Whatever happened caused Solr's heap usage to > skyrocket and require more than 6GB. > > Thanks, > Shawn >
