How the systems handle transaction failure and recovery?
系统如何处理事务失败与恢复？
Having some degree of transaction failure does not equate to a competitive disadvantage.
某种程度上的交易出错，并不等于是一种竞争劣势。
The UI tier will need to notify the user of transaction failure, and solicit input on how to handle the situation.
UI层则需要告诉用户事务失败了，并请求用户指示如何处理情况。
It's important to note that the implementation of aggressive timers doesn't correct or prevent the transaction failure.
务必注意，主动计时器的实现并不能纠正或防止事务失败。
In combination with the corresponding recovery protocols, recovery algorithm guaranteed the atomicity of global transaction failure.
恢复算法结合相关恢复协议，确保了全局事务故障的原子性。
For example, in the case of compensating transaction failure you could send notification to the system administrator, or use messaging technology to retry these transactions at a later time.
例如，在补偿事务失败的情况下，您可以向系统管理员发送通知，或者用消息技术稍后重试这些事务。
There are two kinds of transaction failure to consider: the first is when all of the services are transaction-capable, and the second is when one or more non-transaction-capable services are involved.
要考虑两种事务失败：第一种是所有服务都能够参与事务时，而第二种是包括一个或多个不能参与事务的服务。
This is an architected set of flows used to ensure all resource managers in a transaction can be reliably coordinated, irrespective of any failure.
这是流的体系结构集，用于确保无论发生什么故障，事务中的所有资源管理器都能够可靠地协作。
The next section presents some test cases to help you answer these questions as they relate to the transaction manager, in the event of a resource manager failure at different points in time.
当资源管理器在不同时间点出现故障时，下面小节展示的一些测试案例可以帮助您解决这些问题，因为它们都与事务管理器相关。
A failure of a member does not affect the transaction workload of other members.
一个成员出故障不会影响其他成员的事务工作负载。
Ensuring transaction integrity when distributing business processes across the network and when failure and reliability concerns are significant, for example, in banking applications.
在跨网络分布业务流程以及故障和可靠性顾虑非常重要(例如，在银行应用程序中)时确保事务完整性。
For typical transactional workloads, the time from the member failure until the time the pages are recovered and available to another transaction is typically 20 seconds or less.
对于通常的事务性工作负载，从成员出故障到页面被恢复并可供另一个事务使用，通常只需20秒甚至更少的时间。
Then if a system or media failure occurs, you can use the transaction log and a third-party backup utility to recover your database.
如果系统或媒体发生失败，您可以使用事务日志和第三方备份实用工具恢复数据库。
This is an architected set of flows that transaction managers use to ensure all resource managers in a transaction can be reliably coordinated, irrespective of any failure.
该部分是流程的体系结构集，事务管理器使用它来确保不管任何故障都能可靠地协调事务中所有的资源管理器。
Such a communication failure during commit of the one-phase commit resource introduces the risk of a mixed outcome to the transaction.
在单阶段提交资源提交过程中，这样的通信故障引入了混合事务结果的危险。
The log operation succeeds only on transaction commit, but a failure of the log operation doesn't cause the transaction to abort.
只有当事务提交的时候日志操作才会成功，但日志操作的失败并不会导致事务被中止。
The failure of a log operation does not cause the transaction to fail, and the log operation can succeed even if the transaction itself is aborted.
一个日志操作的失败不会导致整个事务的失败，并且即使在事务被中止的情况下日志操作仍旧可以成功。
Make sure that the transaction manager overall remains available, even after the process detects the failure, Only the process executing the transaction should be affected.
确保事务管理器总体上保持可用，即使进程检测到了故障，也只有执行事务的那个进程受到影响。
Prior to the two-phase commit process, all work performed during the transaction is said to be in-flight, and failure during this period will lead to a rollback of work.
在两阶段提交进程之前，事务过程中执行的所有工作都被认为是“在处理中”，并且在此期间如果失败将会导致工作回滚。
The failure of a single system will cause no interruption of transaction processing on its partners.
一个系统上出现故障不会导致其他系统上的事务被中断。
Thus, a communication failure during commit of the one-phase commit resource introduces the risk of a mixed outcome to the transaction (the heuristic hazard).
因此，在提交单阶段提交资源时通信失败会带来混合的事务结果风险（启发式危险）。
Thus, if there is any failure while the transaction is in-flight (that is, before commit processing is initiated), then all updates will be rolled back.
这样，如果在事务处于处理状态时（即，在启动提交进程之前）发生任何故障，那么所有更新将回滚。
The transaction manager also coordinates recovery activities of the resource managers when necessary, such as after a component failure.
在必要时(如组件失败后)，事务管理器还协调资源管理器的恢复活动。
In order to implement recovery from failure scenarios, the transaction manager and the resource manager must be able to recover from a failure at any point in the transactional flow.
为了执行从故障场景中恢复，事务管理器和资源管理器必须能够在事务流程的任何点从故障中恢复。
However, it must be taken into account what the database can handle without a transaction timeout or a transaction log full failure.
但是，必须考虑到在不出现事务超时或事务日志写满的情况下数据库能够处理的操作量。
Their failure doesn't directly impact the completion of a transaction, and security requirements are minimal.
它们的失败并不会直接影响事务的完成，安全需求最小。
If the transaction load was heavy at the time the partial site failure occurred, it can take several minutes to restart the instances and the databases affected.
如果在发生部分站点故障时事务负载很重，要花几分钟才能重新启动受影响的实例和数据库。
Be aware that no normal transaction operation is affected if such a log message should fail, but the log message itself is affected by the transaction's failure.
因为如果日志操作失败，并没有正常的事务操作受到影响，但如果事务失败，日志消息却会受到影响。
The resource manager fails between prepare and commit processing, and the transaction manager detects the failure.
在准备和提交进程期间，资源管理器出现故障，事务管理器检测到错误。
We recommend transaction logging for high availability and failure recovery.
为了获得高可用性和进行故障恢复，我们推荐使用事务日志。
应用推荐