Pinging on this thread again to bring it to the top. Any idea why one request is stuck for hours in solr cloud.?
On Fri, Dec 9, 2022 at 3:35 PM Satya Nand <satya.n...@indiamart.com> wrote: > Hi Ere, > > We tried executing this request again and it didn't take any time. So it > is not repeatable. average response time of all the queries around this > period was only approx 100-200 ms. > > This was a group=true request where we get 14 groups and 5 results per > group. So no deep pagination. > > On Fri, Dec 9, 2022 at 2:04 PM Ere Maijala <ere.maij...@helsinki.fi> > wrote: > >> Hi, >> >> Are the same requests sometimes stalling and sometimes fast, or is it >> some particular queries that take hours? >> >> There are some things you should avoid with SolrCloud, and deep paging >> (i.e. a large number for the start or rows parameter) is a typical issue >> (see e.g. https://yonik.com/solr/paging-and-deep-paging/ for more >> information). >> >> Best, >> Ere >> >> Satya Nand kirjoitti 8.12.2022 klo 13.27: >> > Hi, >> > >> > Greetings for the day, >> > >> > We are facing a strange problem in Solr cloud where a few requests are >> > taking hours to complete. Some requests return with a 0 status code and >> > some with a 500 status code. The recent request took more than 5 hours >> to >> > complete with only a 9k results count. >> > >> > >> > These queries create problems in closing old searchers, Some times >> there >> > are 3-4 searchers where one is a new searcher and the others are just >> stuck >> > because a few queries are tracking hours. Finally, the application slows >> > down horribly, and the load increases. >> > >> > I have downloaded the stack trace of the affected node and tried to >> analyze >> > this stack trace online. but I couldn't get many insights from it. >> > . >> > >> > Stack Trace: >> > >> > >> https://fastthread.io/my-thread-report.jsp?p=c2hhcmVkLzIwMjIvMTIvOC9sb2dzLnR4dC0tMTAtNTUtMzA=& >> > >> > JVM Settings: We are using Parallel GC, can this be causing this much >> log >> > pause? >> > >> > -XX:+UseParallelGC >> > -XX:-OmitStackTraceInFastThrow >> > -Xms12g >> > -Xmx12g >> > -Xss256k >> > >> > What more we can check here to find the root cause and prevent this from >> > happening again? >> > Thanks in advance >> > >> >> -- >> Ere Maijala >> Kansalliskirjasto / The National Library of Finland >> >