Indexer origin intrinsic metadata uses excessive resources (cpu, memory)
In production, this indexer has been deployed in azure (no data besides exploding in mid-air [0]) and on the dynamic infra [1]. It systematically uses an excessive amount of resources [1]. It's currently deactivated.
Note that on the staging dynamic infra, it's been ok since its deployment [2].
The major distinctions being the staging:
- volumetry which is not of the same dimension
- backend is the cassandra storage instance (vs the postgresql production [3]).
[0] recurrent icinga alerts about resource consumption excess (we no longer have those since the migration to dynamic infra)
[1] https://grafana.softwareheritage.org/goto/J0ho71hIz?orgId=1
[2] https://grafana.softwareheritage.org/goto/vE1t0JhSz?orgId=1
Might be related to [3] #4269