Fix a few typos
This commit is contained in:
parent
f1c17b27fc
commit
5ace1911d1
|
@ -1677,13 +1677,13 @@ public:
|
|||
self->unhealthyServers--;
|
||||
}
|
||||
if (!unhealthy && status->isUnhealthy()) {
|
||||
TraceEvent(SevWarn, "StorangeServerUnhealthy", self->distributorId)
|
||||
TraceEvent(SevWarn, "StorageServerUnhealthy", self->distributorId)
|
||||
.detail("ServerID", interf.id())
|
||||
.detail("ServerIpAddress", interf.address());
|
||||
self->unhealthyServers++;
|
||||
}
|
||||
} else if (status->isUnhealthy()) {
|
||||
TraceEvent(SevWarn, "StorangeServerUnhealthy", self->distributorId)
|
||||
TraceEvent(SevWarn, "StorageServerUnhealthy", self->distributorId)
|
||||
.detail("ServerID", interf.id())
|
||||
.detail("ServerIpAddress", interf.address());
|
||||
self->unhealthyServers++;
|
||||
|
|
|
@ -39,7 +39,7 @@
|
|||
// This workload tests a gray failure scenario: a satellite TLog is have network issue
|
||||
// for sending packets to the remote data center's log routers. This will cause these
|
||||
// log routers to fail to progress, and causing data center lag, i.e., lag between the
|
||||
// primary and remote DC's tlags. With changes to log routers, they can detect that the
|
||||
// primary and remote DC's tlogs. With changes to log routers, they can detect that the
|
||||
// peek is taking a long time (> LOG_ROUTER_PEEK_SWITCH_DC_TIME) and swith to use
|
||||
// another DC to get data, thus recoverying from the data center lag.
|
||||
struct DcLagWorkload : TestWorkload {
|
||||
|
|
Loading…
Reference in New Issue