Description of problem:
Currently each field under an object gets written individually to etcd which makes REST call for each of them. Same is the case while reading an object from etcd.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
The write and read to / from etcd should marshal and un-marshal object data.
How should we measure impact of the change described here? This change doesn't
have functional or directly visible impact on end user, so we can't verify that
this change has expected benefits without specifying how to measure it.
This ideally involves verification across two versions, one without this fix and one with this fix. In new version we should be able to see lesser no of REST calls for writing the object data.
It is sufficient to measure number of REST calls by logging new TCP connections
opened with target port which etcd is listening on via custom firewall rule?
I'm asking as it's likely that the tcp connection could be reused for multiple
queries, correct? If the firewall level logging is not sufficient, we would need
to use tcpdump and count the calls directly there ...
How big improvement do we expect to see? Could I measure this in other way as
well (eg. utilization of particular resource goes down by some percent)?
Fixing wrong docs contact.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.