<div dir="ltr"><div>Re-using the state would mean there's always 1 or 0 running instance of that server at a given time, but what happens if it's scaled up to 2 instances or more? Is it a possible scenario? If yes, it seems complicated to use dc+version+tenant as the feed id.<br></div><div><br></div><div>I filed an issue in JIRA about introducing some kind of TTL : <a href="https://issues.jboss.org/browse/HWKINVENT-205">https://issues.jboss.org/browse/HWKINVENT-205</a></div><div>Maybe those expired feeds fall in the scope of this issue.</div><div><br></div><div><br></div><div class="gmail_extra"><div class="gmail_quote">On Tue, Jan 24, 2017 at 10:21 AM, Heiko W.Rupp <span dir="ltr"><<a href="mailto:hrupp@redhat.com" target="_blank">hrupp@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hey,<br>
<br>
when WildFly connects to Inventory for the 1st time, we sync<br>
the EAP information into inventory, which also includes the information<br>
about which metrics are available.<br>
<br>
Now when WildFly is deployed into Kubernetes or OpenShift, we<br>
will see that WildFly is started, syncs and then dies at some point<br>
in time, where k8s will not re-use the existing one, but start<br>
a new one, which will have a different FeedId.<br>
<br>
This will leave a WildFly in Inventory, that is later detected as<br>
down in Metrics/Alerting, but the one in Inventory will stay<br>
forever. Consequences are<br>
- Inventory will get "full" with no-longer needed information<br>
- Clients will retrieve data about non-"usable" servers<br>
<br>
We need to figure out how to deal with this situation like e.g.:<br>
- have inventory listen on k8s events and remove the server<br>
when k8s removes it (not when it is going down; stopped pods<br>
can stay around for some time)<br>
- Have a different way of creating the feed id / server id so that<br>
the state is "re-used". Something like feedId/server name could<br>
be the name of the deployment config + version + k8s tenant.<br>
<br>
Thoughts?<br>
<br>
______________________________<wbr>_________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/hawkular-dev</a><br>
</blockquote></div><br></div></div>