- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 95 for balancing (0.16 sec)
-
pilot/pkg/networking/core/loadbalancer/loadbalancer.go
return } // Support Locality weighted load balancing // (https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/load_balancing/locality_weight#locality-weighted-load-balancing) // by providing weights in LocalityLbEndpoints via load_balancing_weight. // By setting weights across different localities, it can allow // Envoy to do weighted load balancing across different zones and geographical locations.
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Tue Apr 23 05:38:57 UTC 2024 - 11.8K bytes - Viewed (0) -
samples/multicluster/README.md
```bash kubectl apply -f samples/multicluster/expose-istiod.yaml -n istio-system ``` ## Multi-network Configuration In order to enable cross-cluster load balancing between clusters that are in different networks, we need to expose the services through the east-west gateway in each cluster: ```bash kubectl apply -f samples/multicluster/expose-services.yaml -n istio-system
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Thu Apr 22 16:29:16 UTC 2021 - 1.4K bytes - Viewed (0) -
releasenotes/notes/new_lb_algorithm_default.yaml
apiVersion: release-notes/v2 kind: feature area: traffic-management releaseNotes: - | **Updated** Istio's default load balancing algorithm from `ROUND_ROBIN` to `LEAST_REQUEST`. The `ROUND_ROBIN` algorithm can lead to overburdened endpoints, especially when weights are used. The `LEAST_REQUEST` algorithm, distributes more evenly across and is far less likely to overburden endpoints. A number of experiments (by both the Istio and
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Wed Feb 09 20:55:01 UTC 2022 - 856 bytes - Viewed (0) -
.github/workflows/mint/minio-erasure.yaml
healthcheck: test: ["CMD", "mc", "ready", "local"] interval: 5s timeout: 5s retries: 5 # starts 4 docker containers running minio server instances. # using nginx reverse proxy, load balancing, you can access # it through port 9000. services: minio1: <<: *minio-common hostname: minio1 volumes: - edata1-1:/edata1 - edata1-2:/edata2 - edata1-3:/edata3
Registered: Sun Jun 16 00:44:34 UTC 2024 - Last Modified: Fri Nov 03 21:18:18 UTC 2023 - 1.2K bytes - Viewed (0) -
.github/workflows/mint/minio-pools.yaml
healthcheck: test: ["CMD", "mc", "ready", "local"] interval: 5s timeout: 5s retries: 5 # starts 4 docker containers running minio server instances. # using nginx reverse proxy, load balancing, you can access # it through port 9000. services: minio1: <<: *minio-common hostname: minio1 volumes: - pdata1-1:/pdata1 - pdata1-2:/pdata2 minio2: <<: *minio-common
Registered: Sun Jun 16 00:44:34 UTC 2024 - Last Modified: Fri Nov 03 21:18:18 UTC 2023 - 2.3K bytes - Viewed (0) -
.github/workflows/mint/minio-compress-encrypt.yaml
healthcheck: test: ["CMD", "mc", "ready", "local"] interval: 5s timeout: 5s retries: 5 # starts 4 docker containers running minio server instances. # using nginx reverse proxy, load balancing, you can access # it through port 9000. services: minio1: <<: *minio-common hostname: minio1 volumes: - cdata1-1:/cdata1 - cdata1-2:/cdata2 minio2: <<: *minio-common
Registered: Sun Jun 16 00:44:34 UTC 2024 - Last Modified: Fri Nov 03 21:18:18 UTC 2023 - 1.7K bytes - Viewed (0) -
.github/workflows/mint/minio-resiliency.yaml
healthcheck: test: ["CMD", "mc", "ready", "local"] interval: 5s timeout: 5s retries: 5 # starts 4 docker containers running minio server instances. # using nginx reverse proxy, load balancing, you can access # it through port 9000. services: minio1: <<: *minio-common hostname: minio1 volumes: - rdata1-1:/rdata1 - rdata1-2:/rdata2 minio2: <<: *minio-common
Registered: Sun Jun 16 00:44:34 UTC 2024 - Last Modified: Wed May 22 23:07:14 UTC 2024 - 1.7K bytes - Viewed (0) -
.github/workflows/multipart/docker-compose-site1.yaml
command: server http://site1-minio{1...4}/data{1...2} environment: - MINIO_PROMETHEUS_AUTH_TYPE=public - CI=true # starts 4 docker containers running minio server instances. # using nginx reverse proxy, load balancing, you can access # it through port 9000. services: site1-minio1: <<: *minio-common hostname: site1-minio1 volumes: - site1-data1-1:/data1 - site1-data1-2:/data2 site1-minio2:
Registered: Sun Jun 16 00:44:34 UTC 2024 - Last Modified: Sat Sep 30 10:13:56 UTC 2023 - 1.5K bytes - Viewed (0) -
docs/orchestration/docker-compose/docker-compose.yaml
healthcheck: test: ["CMD", "mc", "ready", "local"] interval: 5s timeout: 5s retries: 5 # starts 4 docker containers running minio server instances. # using nginx reverse proxy, load balancing, you can access # it through port 9000. services: minio1: <<: *minio-common hostname: minio1 volumes: - data1-1:/data1 - data1-2:/data2 minio2: <<: *minio-common
Registered: Sun Jun 16 00:44:34 UTC 2024 - Last Modified: Fri Jun 14 05:40:03 UTC 2024 - 1.5K bytes - Viewed (0) -
staging/src/k8s.io/apiserver/pkg/server/filters/goaway.go
// according to the given chance for HTTP2 requests. After client receive GOAWAY, // the in-flight long-running requests will not be influenced, and the new requests // will use a new TCP connection to re-balancing to another server behind the load balance. func WithProbabilisticGoaway(inner http.Handler, chance float64) http.Handler { return &goaway{ handler: inner, decider: &probabilisticGoawayDecider{ chance: chance,
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Sun Jun 28 20:27:28 UTC 2020 - 2.4K bytes - Viewed (0)