Right now we store nomad and consul information about instances in a hash map inside the InstanceService. This is a potential memory leak.
I don't think it's a severe risk as with the current code base we actually always overwrite the info coming from Nomad / Consul. So as long as nobody changes the code we should be fine.
Solution
Use the play cache API with an appropriate TTL (e.g. double the nomad refresh time).
Problem
Right now we store nomad and consul information about instances in a hash map inside the
InstanceService
. This is a potential memory leak.I don't think it's a severe risk as with the current code base we actually always overwrite the info coming from Nomad / Consul. So as long as nobody changes the code we should be fine.
Solution
Use the play cache API with an appropriate TTL (e.g. double the nomad refresh time).