Solr container in docker deployment uses too small default value for jetty response header size

[Athemis]

What steps does it take to reproduce the issue?

• When does this issue occur?

Deploy Dataverse using docker and import a large metadata block.

• Which page(s) does it occurs on?

Landing page.

• What happens?

No datasets or subdataverses shown; Error message visible instead: "Header size 8663 > 8192"

Error shown in logs:

dataverse            |   Exception running search for [*] with filterQueries [] and paginationStart [0]: edu.harvard.iq.dataverse.search.SearchException: Internal Dataverse Search Engine Error org.apache.solr.client.solrj.SolrServerException org.apache.solr.client.solrj.SolrServerException: Header size 8663 > 8192 org.eclipse.jetty.http2.hpack.HpackException.SessionException org.eclipse.jetty.http2.hpack.HpackException$SessionException: Header size 8663 > 8192 |#]

• To whom does it occur (all users, curators, superusers)?

all

• What did you expect to happen?

Imported metadata block should not lead to errors.

Which version of Dataverse are you using?

6.8

Any related open or closed issues to this bug report?

#2311

The documentation explicitly mentions increasing response header size in the Installing Solr section, however the Solr container used in docker deployment still uses the default value of 8192.

Screenshots:

Are you thinking about creating a pull request for this issue?

• Yes