Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for One (0.14 sec)

  1. docs/bucket/replication/DESIGN.md

    All replication failures are picked up by the scanner which runs at a one minute frequency, each time scanning upto a sixteenth of the namespace. Object versions marked `PENDING` or `FAILED` are re-queued for replication.
    
    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)
  2. docs/bucket/lifecycle/DESIGN.md

    ## Implementation
    
    ILM tiering takes place when a object placed in the bucket meets lifecycle transition rules and becomes eligible for tiering. MinIO scanner (which runs at one minute intervals, each time scanning one sixteenth of the namespace), picks up the object for tiering. The data is moved to the remote tier in entirety, leaving only the object metadata on MinIO.
    
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Thu Sep 29 04:28:45 GMT 2022
    - 4.3K bytes
    - Viewed (0)
  3. docs/distributed/DESIGN.md

      minio server [FLAGS] DIR{1...64}
      minio server [FLAGS] DIR{1...64} DIR{65...128}
    
    DIR:
      DIR points to a directory on a filesystem. When you want to combine
      multiple drives into a single large system, pass one directory per
      filesystem separated by space. You may also use a '...' convention
      to abbreviate the directory arguments. Remote directories in a
      distributed setup are encoded as HTTP(s) URIs.
    ```
    
    ## Common usage
    
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Tue Aug 15 23:04:20 GMT 2023
    - 8K bytes
    - Viewed (0)
Back to top