|
From: Michael W. <wes...@ja...> - 2025-12-12 23:51:37
|
Hi Alberto, It sounds like it may be reindexing. If you abruptly stopped the container without everything shutting down gracefully, reindexing everything will automatically start when you bring it back up. Do you have multiple GB of XML documents and many indexes? If so, reindexing could take quite a while. To gracefully stop eXist, log into the container's shell and run the bin/shutdown.sh script before shutting down the container. I don't use containers, but it seems to me that there is shut down script that can trigger that in Docker's setting file. Hope this helps. Take care. 2025年12月13日(土) 6:00 Alberto Simões <am...@zb...>: > On Friday, December 12th, 2025 at 10:22, Alberto Simões <am...@zb...> > wrote: > > > On Friday, December 12th, 2025 at 09:55, Juri Leino > ju...@ex... wrote: > > > > > That sounds alarming. Especially, when monex does not show any > activity. > > > I have seen instances running on all available CPU cores with a lot of > > > active brokers. > > > > > > What you should see, however, is monex reporting the same CPU usage. > > > Is that the case? > > > > > > Under "System Information" > > > > > > -> System CPU Load: > > > > > > -> Process CPU Load: > > > > > > From monex, everything looks calm. > > System CPU Load: 0.646755 > > Process CPU Load: 0.575614 > > > > Only at the top I have the " Running Queries 1 " but nothing more shows. > > > > As a sidenote, I am running inside a docker image, in case that helps > debugging. > > If I stop the container and restart, load looks normal for a little > time... and gets up again... > > Btw, is there a way to gracelly stop jetty when running inside docker? > > Thanks > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > -- Michael Westbay Writer/System Administrator http://www.japanesebaseball.com/ |