- Sort Score
- Result 10 results
- Languages All
Results 221 - 230 of 403 for cluster (0.47 sec)
-
cmd/notification.go
// of profiling data of all nodes zipWriter := zip.NewWriter(writer) defer zipWriter.Close() // Start by embedding cluster info. if b := getClusterMetaInfo(ctx); len(b) > 0 { internalLogIf(ctx, embedFileInZip(zipWriter, "cluster.info", b, 0o600)) } // Profiles can be quite big, so we limit to max 16 concurrent downloads. ng := WithNPeersThrottled(len(sys.peerClients), 16)
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sun Sep 28 20:59:21 UTC 2025 - 46K bytes - Viewed (0) -
cmd/endpoint.go
type EndpointServerPools []PoolEndpoints // ESCount returns the total number of erasure sets in this cluster func (l EndpointServerPools) ESCount() (count int) { for _, p := range l { count += p.SetCount } return count } // GetNodes returns a sorted list of nodes in this cluster func (l EndpointServerPools) GetNodes() (nodes []Node) { nodesMap := make(map[string]Node) for _, pool := range l {
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sun Sep 28 20:59:21 UTC 2025 - 34.5K bytes - Viewed (0) -
docs/sts/client-grants.md
## Sample `POST` Request ```
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 7.2K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.26.md
with a service account may only reference secrets specified in the service account's secrets field. Kubernetes clusters are only affected if the ServiceAccount admission plugin and the `kubernetes.io/enforce-mountable-secrets` annotation are used together with ephemeral containers. **Note**: This only impacts the cluster if the ServiceAccount admission plugin is used (most cluster should have this on by default as recommended in https://kubernetes.io/docs/reference/access-authn-authz/ad...
Registered: Fri Dec 26 09:05:12 UTC 2025 - Last Modified: Thu Mar 14 16:24:51 UTC 2024 - 425.7K bytes - Viewed (0) -
cmd/bucket-replication-metrics.go
LastFailedCount uint64 `json:"failedCount_last5min"` // Count of unreplicated entries that were dropped after MRF retry limit reached since cluster start. TotalDroppedCount uint64 `json:"droppedCount_since_uptime"` // Bytes of unreplicated entries that were dropped after MRF retry limit reached since cluster start. TotalDroppedBytes uint64 `json:"droppedBytes_since_uptime"` } // SMA struct for calculating simple moving average
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Thu Aug 15 12:04:40 UTC 2024 - 14.2K bytes - Viewed (0) -
cmd/data-usage-utils.go
ObjectsTotalSize uint64 `json:"objectsTotalSize"` ReplicationInfo map[string]BucketTargetUsageInfo `json:"objectsReplicationInfo"` // Total number of buckets in this cluster BucketsCount uint64 `json:"bucketsCount"` // Buckets usage info provides following information across all buckets // - total size of the bucket // - total objects in a bucket // - object size histogram per bucket
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sun Mar 10 09:15:15 UTC 2024 - 6.4K bytes - Viewed (0) -
docs/bucket/notifications/README.md
stanConnection, _ = stan.Connect("test-cluster", "test-client", stan.NatsURL("nats://yourusername:yoursecret@0.0.0.0:4222"), stan.SetConnectionLostHandler(func(c stan.Conn, _ error) { go func() { for { // Reconnect if the connection is lost. if stanConnection == nil || stanConnection.NatsConn() == nil || !stanConnection.NatsConn().IsConnected() {
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 84.2K bytes - Viewed (0) -
docs/kms/README.md
``` In a given setup, there are `n` MinIO instances talking to `m` KES servers but only `1` central KMS. The most simple setup consists of `1` MinIO server or cluster talking to `1` KMS via `1` KES server. 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:
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 7.2K 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:
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 18.9K bytes - Viewed (0) -
src/main/java/org/codelibs/fess/helper/SystemHelper.java
public void addUpdateConfigListener(final String name, final Supplier<String> listener) { updateConfigListenerMap.put(name, listener); } /** * Checks if the cluster state has changed. * * @param status The current cluster status. * @return true if the state has changed, false otherwise. */ public boolean isChangedClusterState(final int status) {
Registered: Sat Dec 20 09:19:18 UTC 2025 - Last Modified: Sat Dec 20 08:30:43 UTC 2025 - 36.6K bytes - Viewed (0)