- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 12 for siteb (0.16 sec)
-
Makefile
@echo "Running tests for replicating three sites" test-site-replication-ldap: install-race ## verify automatic site replication @echo "Running tests for automatic site replication of IAM (with LDAP)" @(env bash $(PWD)/docs/site-replication/run-multi-site-ldap.sh) test-site-replication-oidc: install-race ## verify automatic site replication
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Apr 25 21:55:41 GMT 2024 - 10.3K bytes - Viewed (1) -
docs/config/README.md
MINIO_SITE_NAME (string) name for the site e.g. "cal-rack0" MINIO_SITE_REGION (string) name of the location of the server e.g. "us-west-1" MINIO_SITE_COMMENT (sentence) optionally add a comment to this setting ``` Example: ```sh export MINIO_SITE_REGION="us-west-0" export MINIO_SITE_NAME="sfo-rack-1" minio server /data ``` ### Storage Class
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Sep 11 21:48:54 GMT 2023 - 17.7K bytes - Viewed (0) -
docs/site-replication/README.md
# Automatic Site Replication This feature allows multiple independent MinIO sites (or clusters) that are using the same external IDentity Provider (IDP) to be configured as replicas. In this situation the set of replica sites are referred to as peer sites or just sites. When site-replication is enabled on a set of sites, the following changes are replicated to all other sites: - Creation and deletion of buckets and objects
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Feb 26 21:30:28 GMT 2024 - 3.4K bytes - Viewed (0) -
.gitignore
**/*.swp cover.out *~ minio !*/ site/ **/*.test **/*.sublime-workspace /.idea/ /Minio.iml **/access.log vendor/ .DS_Store *.syso coverage.txt .vscode/ *.tar.bz2 parts/ prime/ stage/ .sia_temp/ config.json node_modules/ mc.* s3-check-md5* xl-meta* healing-* inspect*.zip 200M* hash-set minio.RELEASE* mc nancy inspects/* .bin/ *.gz
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Dec 29 23:52:41 GMT 2023 - 707 bytes - Viewed (0) -
docs/metrics/prometheus/list.md
| `minio_cluster_health_erasure_set_status` | Get current health status of the erasure set | ## Cluster Replication Metrics Metrics marked as ``Site Replication Only`` only populate on deployments with [Site Replication](https://min.io/docs/minio/linux/operations/install-deploy-manage/multi-site-replication.html) configurations.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Apr 25 22:01:31 GMT 2024 - 43.4K bytes - Viewed (2) -
docs/batch-jobs/README.md
# MinIO Batch Job MinIO Batch jobs is an MinIO object management feature that lets you manage objects at scale. Jobs currently supported by MinIO - Replicate objects between buckets on multiple sites Upcoming Jobs - Copy objects from NAS to MinIO - Copy objects from HDFS to MinIO ## Replication Job To perform replication via batch jobs, you create a job. The job consists of a job description YAML that describes
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Oct 06 06:00:43 GMT 2022 - 4.8K bytes - Viewed (0) -
.github/workflows/multipart/nginx-site2.conf
sendfile on; keepalive_timeout 65; # include /etc/nginx/conf.d/*.conf; upstream minio { server site2-minio1:9000; server site2-minio2:9000; server site2-minio3:9000; server site2-minio4:9000; } server { listen 9002; listen [::]:9002; server_name localhost;
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Sep 30 10:13:56 GMT 2023 - 1.7K bytes - Viewed (0) -
.github/workflows/multipart/nginx-site1.conf
sendfile on; keepalive_timeout 65; # include /etc/nginx/conf.d/*.conf; upstream minio { server site1-minio1:9000; server site1-minio2:9000; server site1-minio3:9000; server site1-minio4:9000; } server { listen 9001; listen [::]:9001; server_name localhost;
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Sep 30 10:13:56 GMT 2023 - 1.7K bytes - Viewed (0) -
docs/bucket/replication/DESIGN.md
For active-active replication, automatic failover occurs on `GET/HEAD` operations if object or object version requested qualifies for replication and is missing on one site, but present on the other. This allows the applications to take full advantage of two-way replication even before the two sites get fully synced.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 14.7K bytes - Viewed (0) -
docs/bigdata/README.md
![hdfs-configs](https://github.com/minio/minio/blob/master/docs/bigdata/images/image2.png?raw=true "hdfs advanced configs") Navigate to **Custom core-site** to configure MinIO parameters for `_s3a_` connector ![s3a-config](https://github.com/minio/minio/blob/master/docs/bigdata/images/image5.png?raw=true "custom core-site") ``` sudo pip install yq alias kv-pairify='yq ".configuration[]" | jq ".[]" | jq -r ".name + \"=\" + .value"' ```
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 14.7K bytes - Viewed (0)