OpenShift Container Platform 4.10 CLI 工具工具 64 2.5.1.129. oc set resources 使用 pod 模板更新对象上的资源请求/限制 用法示例 用法示例 2.5.1.130. oc set route-backends 更新路由的后端 用法示例 用法示例 # Set a readiness probe to try to open a TCP socket on 3306 oc set probe yaml # Print the backends on the route 'web' oc set route-backends web # Set two backend services on route 'web' with 2/3rds of traffic going to 'a' oc set route-backends web a=2 b=1 # Increase by 10%% relative to a oc set route-backends web --adjust b=+10%% # Set traffic percentage going to b to 10%% of the traffic going to a oc set route-backends web --adjust b=10%% # Set weight of0 码力 | 120 页 | 1.04 MB | 1 年前3
OpenShift Container Platform 4.13 CLI 工具(OC) 69 2.7.1.129. oc set resources 使用 pod 模板更新对象上的资源请求/限制 用法示例 用法示例 2.7.1.130. oc set route-backends 更新路由的后端 用法示例 用法示例 # Set an HTTP readiness probe for port 8080 and path /healthz over HTTP on yaml # Print the backends on the route 'web' oc set route-backends web # Set two backend services on route 'web' with 2/3rds of traffic going to 'a' oc set route-backends web a=2 b=1 # Increase by 10%% relative to a oc set route-backends web --adjust b=+10%% # Set traffic percentage going to b to 10%% of the traffic going to a oc set route-backends web --adjust b=10%% # Set weight of0 码力 | 128 页 | 1.11 MB | 1 年前3
OpenShift Container Platform 4.8 CLI 工具工具 64 2.5.1.130. oc set resources 使用 pod 模板更新对象上的资源请求/限制 用法示例 用法示例 2.5.1.131. oc set route-backends 更新路由的后端 用法示例 用法示例 # Set a readiness probe to try to open a TCP socket on 3306 oc set probe yaml # Print the backends on the route 'web' oc set route-backends web # Set two backend services on route 'web' with 2/3rds of traffic going to 'a' oc set route-backends web a=2 b=1 # Increase by 10%% relative to a oc set route-backends web --adjust b=+10%% # Set traffic percentage going to b to 10%% of the traffic going to a oc set route-backends web --adjust b=10%% # Set weight of0 码力 | 152 页 | 1.24 MB | 1 年前3
State management - CS 591 K1: Data Stream Processing and Analytics Spring 20202020 A pluggable component that determines how state is stored, accessed, and maintained. State backends are responsible for: • local state management • checkpointing state to remote and persistent distributed filesystem or a database system • Available state backends in Flink: • In-memory • File system • RocksDB State backends 7 Vasiliki Kalavri | Boston University 2020 MemoryStateBackend RocksDB 11 Vasiliki Kalavri | Boston University 2020 In conf/flink.conf.yaml: # Supported backends are 'jobmanager', 'filesystem', ‘rocksdb' # # state.backend: rocksdb # # Directory for checkpoints0 码力 | 24 页 | 914.13 KB | 1 年前3
OpenShift Container Platform 4.9 构建应用程序weight=1 的单一服务,因此所有请求都会进入该服务。添加其他服务作为 alternateBackend 并 调整 weight,即可激活 A/B 设置。这可通过 oc set route-backends 命令或编辑路由来完成。 如果将 oc set route-backend 设为 0,则服务不参与负载均衡,但继续为现有的持久连接服务。 注意 注意 对路由的更改只会改变流量进入各个服务的比例。您可能需要扩展部署来调整 OpenShift Container Platform 4.9 构 构建 建应 应用程序 用程序 120 1. 要管理由路由均衡负载的服务以及对应的权重,请使用 oc set route-backends 命令: 例如,以下命令将 ab-example-a 设为主服务 ( weight=198) 并将 ab-example-b 设为第一替代 服务 (weight=2): 这意味着 99% 的流量发送到服务 set route-backends ROUTENAME \ [--zero|--equal] [--adjust] SERVICE=WEIGHT[%] [...] [options] $ oc set route-backends ab-example ab-example-a=198 ab-example-b=2 $ oc set route-backends ab-example0 码力 | 184 页 | 3.36 MB | 1 年前3
OpenShift Container Platform 4.10 构建应用程序weight=1 的单一服务,因此所有请求都会进入该服务。添加其他服务作为 alternateBackend 并 调整 weight,即可激活 A/B 设置。这可通过 oc set route-backends 命令或编辑路由来完成。 注意 注意 使用 alternateBackends 时,也使用 roundrobin 负载均衡策略来确保请求按预 期分发到服务。通过使用路由注解,可以为路由设置 8. 点击 Create。 8.4.5.1.3. 使用 使用 CLI 管理 管理权 权重 重 流程 流程 1. 要管理由路由均衡负载的服务以及对应的权重,请使用 oc set route-backends 命令: 例如,以下命令将 ab-example-a 设为主服务 ( weight=198) 并将 ab-example-b 设为第一替代 服务 (weight=2): 这意味着 99% 的流量发送到服务 来处理请求负载。 2. 不带标志运行命令来验证当前配置: $ oc set route-backends ROUTENAME \ [--zero|--equal] [--adjust] SERVICE=WEIGHT[%] [...] [options] $ oc set route-backends ab-example ab-example-a=198 ab-example-b=2 OpenShift0 码力 | 198 页 | 3.62 MB | 1 年前3
Deploying and ScalingKubernetes with Rancher
level through a REST endpoint. Heapster natively supports Kubernetes and CoreOS, and a variety of backends can be used to store and visualize the data. Data for all containers on a host is fetched by cAdvisor and aggregated based on pods, services etc. The data is then stored into one of the configured backends, such as InfluxDB. ©Rancher Labs 2017. All rights Reserved. 46 DEPLOYING AND SCALING0 码力 | 66 页 | 6.10 MB | 1 年前3
Docker 从入门到实践 0.4stats uri / frontend balancer bind 0.0.0.0:80 mode http default_backend web_backends backend web_backends mode http option forwardfor balance roundrobin server weba weba:80 check py 文件中 DATABASES = ... 定义的节点内容。 DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': 'postgres', 'USER': 'postgres', 'HOST': 'db'0 码力 | 179 页 | 2.27 MB | 1 年前3
keras tutorialstructure - easy to achieve the result without any frills. It supports multiple platforms and backends. It is user friendly framework which runs on both CPU and GPU. Highly scalability of computation operations. By default, keras runs on top of TensorFlow backend. If you want, you can switch to other backends like Theano or CNTK. Defualt backend configuration is defined inside your root directory under0 码力 | 98 页 | 1.57 MB | 1 年前3
PyTorch Release Notesis using close to all available device memory due to an unexpected memory thrashing when `torch.backends.cudnn.benchmark = True` is used. The performance can be restored by disabling `cudnn.benchmark` autotuning could cause a long startup time or a hang. In these cases, disbale autotuning using `torch.backends.cudnn.benchmark = False`. ‣ GNMTv2 inference performance regression of up to 50% due to an MKL cases this might be manifested as NaNs in the output and we recommend to disable cuDNN via torch.backends.cudnn.enabled = False. ‣ Channels-last memory format is experimental in the 20.07 container. Potential0 码力 | 365 页 | 2.94 MB | 1 年前3
共 158 条
- 1
- 2
- 3
- 4
- 5
- 6
- 16













