- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 32 for Night (3.45 sec)
-
cmd/object-api-common.go
package cmd import ( "sync" "github.com/dustin/go-humanize" ) const ( // Block size used for all internal operations version 1. // TLDR.. // Not used anymore xl.meta captures the right blockSize // so blockSizeV2 should be used for all future purposes. // this value is kept here to calculate the max API // requests based on RAM size for existing content. blockSizeV1 = 10 * humanize.MiByte
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Nov 21 01:09:35 GMT 2023 - 2.1K bytes - Viewed (0) -
docs/throttle/README.md
These values are enabled using server's configuration or environment variables. ## Examples ### Configuring connection limit
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) -
cmd/mrf.go
func (m *mrfState) healRoutine(z *erasureServerPools) { for { select { case <-GlobalContext.Done(): return case u, ok := <-m.opCh: if !ok { return } // We might land at .metacache, .trash, .multipart // no need to heal them skip, only when bucket // is '.minio.sys' if u.bucket == minioMetaBucket { // No MRF needed for temporary objects
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Apr 23 17:15:52 GMT 2024 - 3.2K bytes - Viewed (0) -
docs/hotfixes.md
```
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Feb 14 21:36:02 GMT 2024 - 5K bytes - Viewed (0) -
cmd/signature-v2_test.go
// Test case with wrong accessID. { authString: fmt.Sprintf("%s %s:%s", signV2Algorithm, "InvalidAccessID", "signature"), expectedError: ErrInvalidAccessKeyID, }, // Test case - 6. // Case with right accessID and format. { authString: fmt.Sprintf("%s %s:%s", signV2Algorithm, accessID, "signature"), expectedError: ErrNone, }, } for i, testCase := range testCases {
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Oct 14 10:08:40 GMT 2022 - 8K bytes - Viewed (0) -
docs/kms/README.md
The main difference between various MinIO-KMS deployments is the KMS implementation. The following table helps you select the right option for your use case: | KMS | Purpose |
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 7.1K bytes - Viewed (0) -
internal/s3select/sql/utils.go
e.And[0].Condition[0].Not != nil || e.And[0].Condition[0].Operand.ConditionRHS != nil { return "", false } operand := e.And[0].Condition[0].Operand.Operand if operand.Right != nil || operand.Left.Right != nil || operand.Left.Left.Negated != nil || operand.Left.Left.Primary.JPathExpr == nil { return "", false } // Check if path expression ends in a key
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Nov 10 16:12:50 GMT 2021 - 3.6K bytes - Viewed (0) -
docs/erasure/storage-class/README.md
redundancy or better drive space utilization. To get an idea of how various combinations of data and parity drives affect the storage usage, let’s take an example of a 100 MiB file stored on 16 drive MinIO deployment. If you use eight data and eight parity drives, the file space usage will be approximately twice, i.e. 100 MiB file will take 200 MiB space. But, if you use ten data and six parity drives, same 100 MiB file takes around 160 MiB. If you use 14 data and
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) -
cmd/bitrot.go
if err != nil { // Read's failed for object with right size, file is corrupt. return err } // Subtract hash length.. left -= int64(n) if left < shardSize { shardSize = left } read, err := io.CopyBuffer(h, io.LimitReader(r, shardSize), *bufp) if err != nil { // Read's failed for object with right size, at different offsets. return errFileCorrupt }
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Jan 30 20:43:25 GMT 2024 - 7.6K bytes - Viewed (0) -
code_of_conduct.md
behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior, in compliance with the licensing terms applying to the Project developments. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Jan 20 18:38:58 GMT 2020 - 3.5K bytes - Viewed (0)