- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 32 for number (0.22 sec)
-
docs/config/README.md
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/throttle/README.md
MinIO server allows to throttle incoming requests: - limit the number of active requests allowed across the cluster - limit the wait duration for each request in the queue These values are enabled using server's configuration or environment variables. ## Examples
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Feb 12 00:51:25 GMT 2022 - 2.4K bytes - Viewed (0) -
docs/sts/web-identity.md
**NOTE**: When configuring multiple OpenID based authentication providers on a MinIO cluster, any number of Role Policy based providers may be configured, and at most one JWT Claim based provider may be configured. <details><summary>Example 1: Two role policy providers</summary> Sample environment variables: ```
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 19.2K bytes - Viewed (1) -
docs/erasure/README.md
MinIO divides the drives you provide into erasure-coding sets of *2 to 16* drives. Therefore, the number of drives you present must be a multiple of one of these numbers. Each object is written to a single erasure-coding set.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 4.1K bytes - Viewed (0) -
docs/metrics/prometheus/list.md
| `minio_s3_requests_inflight_total` | Total number of S3 requests currently in flight. | | `minio_s3_requests_rejected_auth_total` | Total number S3 requests rejected for auth failure. | | `minio_s3_requests_rejected_header_total` | Total number S3 requests rejected for invalid header. |
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/metrics/v3.md
| `minio_api_requests_rejected_auth_total` | `counter` | Total number of requests rejected for auth failure | `type,pool_index,server` | | `minio_api_requests_rejected_header_total` | `counter` | Total number of requests rejected for invalid header | `type,pool_index,server` | | `minio_api_requests_rejected_timestamp_total` | `counter` | Total number of requests rejected for invalid timestamp | `type,pool_index,server` |
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu May 02 17:37:57 GMT 2024 - 28.5K bytes - Viewed (0) -
docs/erasure/storage-class/README.md
- Greater than `REDUCED_REDUNDANCY` parity, if it is set. Parity blocks can not be higher than data blocks, so `STANDARD` storage class parity can not be higher than N/2. (N being total number of drives) The default value for the `STANDARD` storage class depends on the number of volumes in the erasure set: | Erasure Set Size | Default Parity (EC:N) | |------------------|-----------------------| | 5 or fewer | EC:2 |
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Aug 15 23:04:20 GMT 2023 - 5.8K bytes - Viewed (1) -
VULNERABILITY_REPORT.md
reported vulnerability and how it might be exploited. Alternatively, a well-established vulnerability identifier, e.g. CVE number, can be used instead. Based on the description mentioned above, a MinIO engineer or security team member investigates: - Whether the reported vulnerability exists. - The conditions that are required such that the vulnerability can be exploited.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Feb 12 00:51:25 GMT 2022 - 1.5K bytes - Viewed (0) -
docs/bucket/lifecycle/README.md
Enable object lifecycle configuration on buckets to setup automatic deletion of objects after a specified number of days or a specified date. ## 1. Prerequisites - Install MinIO - [MinIO Quickstart Guide](https://min.io/docs/minio/linux/index.html#quickstart-for-linux).
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Aug 26 07:33:25 GMT 2023 - 9K bytes - Viewed (1) -
docs/security/README.md
``` In case of a S3 multi-part operation each part is en/decrypted with the scheme shown in Figure 1. However, for each part an unique secret key is derived from the OEK and the part number using a PRF. So in case of multi-part not the OEK but the output of `PRF(OEK, part_id)` is used as secret key. #### Cryptographic Primitives
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Feb 12 00:51:25 GMT 2022 - 13.8K bytes - Viewed (0)