从上次写操作到出现服务器故障之间对会话的任何更改都可能丢失。
Any changes in the session between the last write and a server failure can be lost.
例如，一家金融公司不可能因为意外而短暂的服务器故障就舍弃一个重要的服务提供者。
For example, a financial firm is not likely to abandon an important service provider for an unexpected, short duration server outage.
数据库在回滚事务时，可能会从服务器2剥夺共享资源，而后者与故障没有任何关系。
So as the database is rolling back the transactions, Shared resources could be shifted away from server 2, which had nothing to do with the failure.
由于有几个克隆的服务器可以用来处理请求，故障不太可能破坏系统的吞吐量和可靠性。
With several clones available to handle requests, it is more likely that failures will not damage throughput and reliability.
计算这些情况的可能性非常容易；问题在于存在很多不同的方式，比如10台服务器中的5台可能出故障。
It is quite easy to calculate the probabilities of those; the problem is that there are a lot of different ways that, say 5 out of 10 servers can be down.
如若发送方服务器出故障，发送方就可能丢失消息的副本，因而不能进行重发。
If the sender_s server goes down the sender may lose its copy of the message and, therefore, will not be able to resend it.
尽管这样做可能会在短期内产生经济效益，但服务器故障处理起来非常费时，而且还可能会因为多个品牌造成额外问题。
Although doing so may have appeared economical in the short run, a server failure is time-consuming enough without the added headache of multiple hardware brands.
此解决方案的另一个优势是能够处理应用服务器的级联故障，而这在内存到内存配置中只有使用多个副本才有可能实现。
Another advantage is that this solution can handle cascading failures of application servers, which is only possible with more than one replica in a memory to memory configuration.
他们需要分隔实例以及同时运行两台服务器的理由就是为了降低多个并发应用程序发生故障的可能性。
The reason they wanted to separate the instances and have both servers running was to decrease the possibility of multiple concurrent application failures.
模式定义变更、服务器和网络故障，以及密码过期等事件随时可能发生。
Schema definitions change, servers and networks go down, passwords expire, and so on.
当一个数据库服务器的速度降低时，为进行测试和排除故障而增加的工作负载很可能使问题变得更严重。
When a database server slows down, the added workload from people logging in to test and troubleshoot can easily make matters worse.
基本上，在一个比如有10台服务器的集群中，您可能有一个有限数量的感兴趣的组合：亦即没有服务器出故障、一台服务器出故障、两台服务器出故障？
Basically, in a cluster of, say, 10 servers, you can have a limited number of combinations you are interested in: i.e. no servers down, one server down, two servers down?
在以下情况下可能重新设置此设置：故障转移、首选服务器更改、缓存文件不可访问、复制间隔错误，或者在其他任何需要与新的服务器邮件文件进行同步时。
This setting can be reset by failover, preferred server change, unreachable cache file, replication interval setback, or any other time you need to synch with a new server mail file.
服务器故障的发生可能有两种原因所致：软件故障或硬件故障。
Two types of potential server failure exist: software failure and hardware failure.
如果服务器发生故障，客户端将从服务器得不到确认信息，将有可能发生两种情形。
If the server fails, the client gets no acknowledgement message from the server. There are two possible scenarios.
log中记录的所有请求表明故障出现在odr中，而proxy . log文件中记录的失败请求可能表明问题出在应用程序服务器上。
File indicate the failure occurred in the ODR, where failed requests logged in the proxy.log file may indicate the problem is with the application server.
服务器里的GC会引起响应时间和大规模GC事件出现变化，可能会致使(一级缓存l1的)缓存客户端故障转移到备份的Terracotta服务器上去。
GC in the server caused variation in response times and in the event a large GC occurred, could cause Cache clients (L1's) to failover to a backup Terracotta server.
您要连结的网络服务器或网络可能发生故障。请稍后再试。
The remote host or network may be down. Please try the request again.
您要连结的网络服务器或网络可能发生故障。请稍后再试。
Connection timed out the remote host or network may be down. Please try the request again.
您要连结的网络服务器或网络可能发生故障。请稍后再试。
Connection timed out the remote host or network may be down. Please try the request again.
应用推荐