Chris, Thanks for the suggestions. I checked and our max_stanza_size is set to 2 million or 2000000. Can you confirm that your change was to 20 million or 20000000 as your email specified?
As a part of the upgrade all our records were reingested so we should be good on that front. Beth On Wed, Dec 19, 2018 at 4:01 PM Chris Burton <[email protected]> wrote: > I ran across an issue like this just recently. > The ejabberd settings around line 125 with max_stanza_size was too small. > Equinox helped me out and we quadrupled it to 20000000. > This does require a restart of ejabberd, opensrf and apache though. > > Ejabberd is the XMPP server that communicates searches with opensrf > processes. > > > Another possibility is that your database requires a reingest to reindex > all the records in the system. > > Others may have more suggestions as we just started using Evergreen last > year > > On Wed, 19 Dec 2018 at 16:43, Beth Longwell <[email protected]> wrote: > >> Evergreen libraries, >> >> We recently upgraded to 3.1.7 from 2.11. Before the upgrade we were >> experiencing slowness and failed searches even for known items in the >> catalog. We thought with the upgrade that this would go away but it has >> not. So far, most of the slowness seems to be on keyword searches but we >> are having the libraries track when the problem occurs and the search >> details so we will have more information. >> >> Have any of you experienced something similar? Any ideas on what we can >> do? >> >> There are 74 libraries in our consortium, many of them small. We have two >> application servers and have not seen any indications of load problems. >> >> Thanks in advance for any help, >> >> Beth Ross >> Systems Manager >> Sage Library System >> >> >>
