On 1/11/22 17:37, Dumitru Ceara wrote:
> When reconnecting, if there are condition changes already sent to the
> server but not yet acked, reset the db's 'last-id', esentially clearing
> the local cache after reconnect.
>
> This is needed because the client cannot easily differentiate between
> the following cases:
> a. either the server already processed the requested monitor
> condition change but the FSM was restarted before the
> client was notified. In this case the client should
> clear its local cache because it's out of sync with the
> monitor view on the server side.
> b. OR the server hasn't processed the requested monitor
> condition change yet.
>
> Conditions changing at the same time with a reconnection happening are
> rare so the performance impact of this patch should be minimal.
>
> Also, the tests are updated to cover the fact that we cannot control
> which of the two scenarios ("a" and "b" above) are hit during the test.
>
Fixes: ae25f8c8fff8 ("ovsdb-idl: Avoid inconsistent IDL state with
OVSDB_MONITOR_V3.")
> Reported-by: Maxime Coquelin <maxime.coque...@redhat.com>
> Signed-off-by: Dumitru Ceara <dce...@redhat.com>
> ---
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
