Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 5 of 5 for wasn (0.14 sec)

  1. internal/grid/README.md

        conn := manager.Connection(host)
    	
        payload := []byte("request")
        response, err := conn.SingleRequest(ctx, grid.HandlerDiskInfo, payload)
    ```
    
    If the error type is `*RemoteErr`, then the error was returned by the remote server. Otherwise it is a local error.
    
    Context timeouts are propagated, and a default timeout of 1 minute is added if none is specified.
    
    There is no cancellation propagation for single payload requests.
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Thu Jan 18 07:03:17 GMT 2024
    - 9.4K bytes
    - Viewed (0)
  2. docs/integrations/veeam/README.md

    - Under Home > Jobs > Backup in Navigation Pane, click on Backup Job button in the ribbon and choose Virtual Machine. Follow the on screen wizard.
    
    - On the Storage screen, choose the Scale-out Backup Repository that was configured previously.
    
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Thu Sep 29 04:28:45 GMT 2022
    - 5.4K bytes
    - Viewed (0)
  3. docs/bucket/notifications/README.md

          }
        ]
      }
    }
    ```
    
    This output shows that a document has been created for the event in Elasticsearch.
    
    Here we see that the document ID is the bucket and object name. In case `access` format was used, the document ID would be automatically generated by Elasticsearch.
    
    ## Publish MinIO events via Redis
    
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Thu Jan 18 07:03:17 GMT 2024
    - 84K bytes
    - Viewed (2)
  4. docs/bigdata/README.md

    It was found that the directory staging committer was the fastest among the three, S3A connector should be configured with the following parameters for optimal results:
    
    ```
    cat ${HADOOP_CONF_DIR}/core-site.xml | kv-pairify | grep "s3a"
    
    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)
  5. docs/bucket/replication/README.md

    the `X-Amz-Replication-Status` changes from `PENDING` to `COMPLETED` or `FAILED` after replication attempt either succeeded or failed respectively. On the destination side, a `X-Amz-Replication-Status` status of `REPLICA` indicates that the object was replicated successfully. Any replication failures are automatically re-attempted during a periodic disk scanner cycle.
    
    To perform bi-directional replication, repeat the above process on the target site - this time setting the source bucket...
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Tue Jan 24 23:46:33 GMT 2023
    - 18.2K bytes
    - Viewed (0)
Back to top