- Sort Score
- Result 10 results
- Languages All
Results 81 - 90 of 187 for clusterid (0.04 sec)
-
cmd/perf-tests.go
clusterInfos, err := globalSiteReplicationSys.GetClusterInfo(ctx) if err != nil { return madmin.SiteNetPerfNodeResult{Error: err.Error()} } // Scale the number of connections from 32 -> 4 from small to large clusters. connectionsPerPeer := 3 + (29+len(clusterInfos.Sites)-1)/len(clusterInfos.Sites) errStr := "" var wg sync.WaitGroup for _, info := range clusterInfos.Sites { // skip self
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Fri Aug 29 02:39:48 UTC 2025 - 11.7K bytes - Viewed (0) -
src/main/resources/mail/es_status.dfmail
Registered: Thu Sep 04 12:52:25 UTC 2025 - Last Modified: Thu Oct 27 02:03:02 UTC 2016 - 291 bytes - Viewed (0) -
docs/metrics/prometheus/grafana/README.md
Cluster level Replication metrics can be viewed in the Grafana dashboard using [json file here](https://raw.githubusercontent.com/minio/minio/master/docs/metrics/prometheus/grafana/replication/minio-replication-cluster.json) 
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Thu Oct 31 17:38:53 UTC 2024 - 2.4K bytes - Viewed (0) -
docs/en/docs/deployment/docker.md
If you have a <abbr title="A group of machines that are configured to be connected and work together in some way.">cluster</abbr> of machines with **Kubernetes**, Docker Swarm Mode, Nomad, or another similar complex system to manage distributed containers on multiple machines, then you will probably want to **handle replication** at the **cluster level** instead of using a **process manager** (like Uvicorn with workers) in each container.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 29.5K bytes - Viewed (1) -
.gitignore
**/.hg **/.hg* # Vagrant .vagrant network_closure.sh # Local cluster env variables /cluster/env.sh # Compiled binaries in third_party /third_party/pkg # Also ignore etcd installed by hack/install-etcd.sh /third_party/etcd* /default.etcd # Also ignore protoc installed by hack/install-protoc.sh /third_party/protoc* # User cluster configs .kubeconfig .tags* # Version file for dockerized build
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Thu Feb 29 08:22:06 UTC 2024 - 2.1K bytes - Viewed (0) -
docs/es/docs/deployment/docker.md
Si tienes un <abbr title="Un grupo de máquinas que están configuradas para estar conectadas y trabajar juntas de alguna manera.">cluster</abbr> de máquinas con **Kubernetes**, Docker Swarm Mode, Nomad, u otro sistema complejo similar para gestionar contenedores distribuidos en varias máquinas, entonces probablemente querrás manejar la **replicación** a nivel de **cluster** en lugar de usar un **gestor de procesos** (como Uvicorn con workers) en cada contenedor.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Fri May 30 13:15:52 UTC 2025 - 31K bytes - Viewed (0) -
docs/sts/etcd.md
--advertise-client-urls http://0.0.0.0:2379 \ --listen-peer-urls http://0.0.0.0:2380 \ --initial-advertise-peer-urls http://0.0.0.0:2380 \ --initial-cluster s1=http://0.0.0.0:2380 \ --initial-cluster-token tkn \ --initial-cluster-state new ``` You may also setup etcd with TLS following this documentation [here](https://coreos.com/etcd/docs/latest/op-guide/security.html) ### 3. Setup MinIO with etcd
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 3.5K bytes - Viewed (0) -
src/main/java/org/codelibs/fess/app/web/admin/maintenance/AdminMaintenanceAction.java
*/ protected void writeFesenJson(final ZipOutputStream zos, final String id) { writeElastisearchJsonApi(zos, id, "cluster", "health"); writeElastisearchJsonApi(zos, id, "cluster", "state"); writeElastisearchJsonApi(zos, id, "cluster", "stats"); writeElastisearchJsonApi(zos, id, "cluster", "pending_tasks"); writeElastisearchJsonApi(zos, id, "nodes", "stats");
Registered: Thu Sep 04 12:52:25 UTC 2025 - Last Modified: Thu Aug 07 03:06:29 UTC 2025 - 18K bytes - Viewed (0) -
docs/pt/docs/deployment/docker.md
você tiver um <abbr title="Um grupo de máquinas que são configuradas para estarem conectadas e trabalharem juntas de alguma forma">cluster</abbr> de máquinas com **Kubernetes**, Docker Swarm Mode, Nomad ou outro sistema complexo semelhante para gerenciar contêineres distribuídos em várias máquinas, então provavelmente desejará **lidar com a replicação** no **nível do cluster** em vez de usar um **gerenciador de processos** (como o Gunicorn com workers) em cada contêiner. Um desses sistemas...
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sat Nov 09 16:39:20 UTC 2024 - 37.4K bytes - Viewed (0) -
docs/de/docs/deployment/docker.md
title="Eine Gruppe von Maschinen, die so konfiguriert sind, dass sie verbunden sind und auf irgendeine Weise zusammenarbeiten.">Cluster</abbr> von Maschinen mit **Kubernetes**, Docker Swarm Mode, Nomad verwenden, oder einem anderen, ähnlich komplexen System zur Verwaltung verteilter Container auf mehreren Maschinen, möchten Sie wahrscheinlich die **Replikation auf Cluster-Ebene abwickeln**, anstatt in jedem Container einen **Prozessmanager** (wie Gunicorn mit Workern) zu verwenden. Diese...
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sat Nov 09 16:39:20 UTC 2024 - 38.9K bytes - Viewed (0)