Header size too large when using large number of metadatablocks
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
What steps does it take to reproduce the issue?
-
When does this issue occur?
Deploying Dataverse with Docker and adding many metadata blocks (including many fields), currently it happened with for us with 45 metadata blocks (including the default ones : citation, journal...). -
Which page(s) does it occurs on?
All pages, although I can login and logout but can't see the dataverse, datasets... -
What happens?
I get an error displaying that there's an issue with the search engine, supposing that there header of the request is too large,
the exact error is:
Could not hpack encode GET{u=http://solr:8983/solr/collection1/select?q=*&sort=dateSort+desc&fl=*%2Cscore&qt=%2Fselect&facet=true&facet.query=*&fa..... -
To whom does it occur (all users, curators, superusers)?
To all users -
What did you expect to happen?
Which version of Dataverse are you using?
- Dataverse version 6.6
- Solr version 9.8.0
Any related open or closed issues to this bug report?
- #12047
- #8911
Screenshots:
Related discussion:
#troubleshooting > Number of Metadatablocks limit @ 💬
Thank you in advance and best regards.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure in a Docker deployment with many metadata blocks and inspect the search-engine request error involving Solr. The report names no source files or tests; done means deployments with many metadata blocks no longer produce oversized-header errors and all users can access Dataverse and dataset pages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- backend, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100