Use this function to explicitly commit a remote transaction running in "update" or "query" transaction mode. You typically will not use this function for transactions running in "auto" transaction mode because the server commits such transactions automatically, at the end of every statement.

When you call xdmp:transaction-commit, the transaction is marked for commit. The commit occurs asyncronously at a point in time after the end of the current executing statement, typically after the next cluster heartbeat. The transaction ends at that point, and you can verify it with xdmp:host-status.

If the named host or transaction does not exist, an error is raised.