enable error

This commit is contained in:
timchenxiaoyu 2017-02-24 14:09:27 +08:00
parent b3453d0bd2
commit 50bc2ee9ba
3 changed files with 3 additions and 3 deletions

View File

@ -43,7 +43,7 @@ Resuming the workload will [uncordon](http://kubernetes.io/docs/user-guide/kubec
## Known Limitations ## Known Limitations
Kubernetes workers currently only support 'phaux' HA scenarios. Even when configured with an HA cluster string, they will only ever contact the first unit in the cluster map. To enalbe a proper HA story, kubernetes-worker units are encouraged to proxy through a [kubeapi-load-balancer](https://jujucharms.com/kubeapi-load-balancer) Kubernetes workers currently only support 'phaux' HA scenarios. Even when configured with an HA cluster string, they will only ever contact the first unit in the cluster map. To enable a proper HA story, kubernetes-worker units are encouraged to proxy through a [kubeapi-load-balancer](https://jujucharms.com/kubeapi-load-balancer)
application. This enables a HA deployment without the need to application. This enables a HA deployment without the need to
re-render configuration and disrupt the worker services. re-render configuration and disrupt the worker services.

View File

@ -656,7 +656,7 @@ slowlog-max-len 128
# By default latency monitoring is disabled since it is mostly not needed # By default latency monitoring is disabled since it is mostly not needed
# if you don't have latency issues, and collecting data has a performance # if you don't have latency issues, and collecting data has a performance
# impact, that while very small, can be measured under big load. Latency # impact, that while very small, can be measured under big load. Latency
# monitoring can easily be enalbed at runtime using the command # monitoring can easily be enabled at runtime using the command
# "CONFIG SET latency-monitor-threshold <milliseconds>" if needed. # "CONFIG SET latency-monitor-threshold <milliseconds>" if needed.
latency-monitor-threshold 0 latency-monitor-threshold 0

View File

@ -656,7 +656,7 @@ slowlog-max-len 128
# By default latency monitoring is disabled since it is mostly not needed # By default latency monitoring is disabled since it is mostly not needed
# if you don't have latency issues, and collecting data has a performance # if you don't have latency issues, and collecting data has a performance
# impact, that while very small, can be measured under big load. Latency # impact, that while very small, can be measured under big load. Latency
# monitoring can easily be enalbed at runtime using the command # monitoring can easily be enabled at runtime using the command
# "CONFIG SET latency-monitor-threshold <milliseconds>" if needed. # "CONFIG SET latency-monitor-threshold <milliseconds>" if needed.
latency-monitor-threshold 0 latency-monitor-threshold 0