[ovs-dev] [PATCH] ovsdb-server.7: Describe message ordering between "update" and "transact".

Ben Pfaff blp at ovn.org
Mon Apr 22 21:00:24 UTC 2019


This comes up sometime and it's best to document it.

Signed-off-by: Ben Pfaff <blp at ovn.org>
---
 Documentation/ref/ovsdb-server.7.rst | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/Documentation/ref/ovsdb-server.7.rst b/Documentation/ref/ovsdb-server.7.rst
index 4bbe2325ac1f..9be4f2c0cc07 100644
--- a/Documentation/ref/ovsdb-server.7.rst
+++ b/Documentation/ref/ovsdb-server.7.rst
@@ -1,5 +1,5 @@
 ..
-      Copyright (c) 2017 Nicira, Inc.
+      Copyright (c) 2017, 2019 Nicira, Inc.
 
       Licensed under the Apache License, Version 2.0 (the "License"); you may
       not use this file except in compliance with the License. You may obtain
@@ -146,6 +146,13 @@ notifications (see below) to the request, it must be unique among all active
 monitors.  ``ovsdb-server`` rejects attempt to create two monitors with the
 same identifier.
 
+When a given client sends a ``transact`` request that changes a table that the
+same client is monitoring, ``ovsdb-server`` always sends the ``update`` (or
+``update2`` or ``update3``) for these changes before it sends the reply to the
+``transact`` request.  Thus, when a client replies a ``transact`` reply, it can
+know immediately what changes (if any) the transaction made.  (If the other
+ordering were used, then the client might have to wait indefinitely.)
+
 4.1.7 Monitor Cancellation
 --------------------------
 
-- 
2.20.1



More information about the dev mailing list