Search Options

Display Count
Sort
Preferred Language
Advanced Search

Results 1 - 3 of 3 for replication_workers (0.07 seconds)

  1. internal/config/api/api.go

    )
    
    // Deprecated key and ENVs
    const (
    	apiReadyDeadline            = "ready_deadline"
    	apiRequestsDeadline         = "requests_deadline"
    	apiReplicationWorkers       = "replication_workers"
    	apiReplicationFailedWorkers = "replication_failed_workers"
    )
    
    // DefaultKVS - default storage class config
    var (
    	DefaultKVS = config.KVS{
    		config.KV{
    			Key:   apiRequestsMax,
    			Value: "0",
    		},
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Fri Aug 29 02:39:48 GMT 2025
    - 11.5K bytes
    - Click Count (1)
  2. docs/bucket/replication/DESIGN.md

    contribute to replication speed. The number of workers used for replication defaults to 100. Based on network bandwidth and system load, the number of workers used in replication can be configured using `mc admin config set alias api` to set the `replication_workers`. The prometheus metrics exposed by MinIO can be used to plan resource allocation and bandwidth management to optimize replication speed.
    
    If synchronous replication is configured above, replication is attempted right away prior to returning...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Tue Aug 12 18:20:36 GMT 2025
    - 14.7K bytes
    - Click Count (0)
  3. internal/config/config.go

    // previously known names
    var renamedSubsys = map[string]string{
    	CrawlerSubSys: ScannerSubSys,
    	// Add future sub-system renames
    }
    
    const ( // deprecated keys
    	apiReplicationWorkers       = "replication_workers"
    	apiReplicationFailedWorkers = "replication_failed_workers"
    )
    
    // map of subsystem to deleted keys
    var deletedSubSysKeys = map[string][]string{
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Sun Sep 28 20:59:21 GMT 2025
    - 37.7K bytes
    - Click Count (0)
Back to Top