Loading of issue changelog is required to be able to reopen closed issues to their relevant previous status and resolution.
However, the current implementation seem to be causing Out of Memory errors due to a design which loads all the change log of all the closed issue of a component at once (see INFRA-2444 and INFRA-2454 for OOM stacktrace samples).
Several possibles axis of improvement (which could be combined):
- stream changelog data from DB instead of loading them all in memory (see ..)
- do not load the changelog of all closed issues (maybe only a subset we could identify is required)
- do not load all the change log of each issue: we only care about some types of changelog entries and the latest ones of those