I’ve seen this signal in different places than Solr that use http2. From what I’ve read, it’s something that the client should expect and handle appropriately (eg. retry again later)
Let me know if someone knows better, as I’m just another victim:) — > On May 13, 2025, at 18:04, dario.v...@coop.ch.invalid wrote: > > Dear Solr People > > On our system we have an indexer-service that indexes documents based on > incoming events. Sometimes a lot of these events happen at the same time (or > at least very close in time to each other). If that happens our indexer > receives GOAWAY signals from solr. > We're using the HttpJdkSolrClient with HTTP/2. Solr Version is 9.5.0 > > When exactly do these GOAWAY signals show up. In other words, how many > requests need to be made to solr in a certain amount of timespan that solr > starts emitting this signal. And how exactly should it be handled or fixed. > > Should we switch to HTTP/1.1? This version of HTTP does not specify this > signal, but this is probably not a solution? > Using another client? > > Can there be done anything else about it? Will the documents that were in the > request that caused the GOAWAY signal still get added to the index or do we > need to resend this request? And If yes, how long should we wait to resend it? > > With kind regards, > > Dario
