-
Sub-task
-
Resolution: Won't Do
-
Medium
-
None
-
None
-
None
-
None
https://jiradc.int.net.nokia.com/browse/ONAP-509
Currently we handle each connected client with current dynamic (Consul-based) configuration. This has at least these issues:
- long running clients may produce messages for hours with the old configuration
- frequent configuration changes with frequent client connections will result in many copies of VesHvCollector and dependent classes on the heap