If the coordinator fails or is shut down during a writer-initiated global transaction, a “Coordinator node not responding” error occurs. Depending on the current state of the global transaction, one of the following will happen:
If this error occurs during the initiation of the transaction, only the current command is rolled back and the transaction can continue.
If a global transaction is already initiated, and this error occurs before committing the global transaction, that transaction cannot be committed and must be rolled back.
If this error occurs during the commit of a global transaction, the user's connection is terminated.
If a global transaction initiated from a writer node modifies both global and local persistent objects (for example, an SA base table and an IQ base table), and the coordinator fails during commit, global object changes may be committed while local object changes are lost. This is consistent with the same scenario updating both local and proxy tables in the same transaction, where “best effort” is used to commit both local and global components of a transaction.