- Sort Score
- Result 10 results
- Languages All
Results 1 - 8 of 8 for participating (0.17 sec)
-
cmd/admin-handlers-pools.go
if id, err = pools.initRebalanceMeta(ctx, buckets); err != nil { writeErrorResponseJSON(ctx, w, toAPIError(ctx, err), r.URL) return } // Rebalance routine is run on the first node of any pool participating in rebalance. pools.StartRebalance() b, err := json.Marshal(struct { ID string `json:"id"` }{ID: id}) if err != nil { writeErrorResponseJSON(ctx, w, toAPIError(ctx, err), r.URL) return
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sun Sep 28 20:59:21 UTC 2025 - 11.1K bytes - Viewed (0) -
cmd/erasure-server-pool-rebalance_gen.go
} case "bs": z.Bytes, err = dc.ReadUint64() if err != nil { err = msgp.WrapError(err, "Bytes") return } case "par": z.Participating, err = dc.ReadBool() if err != nil { err = msgp.WrapError(err, "Participating") return } case "inf": err = z.Info.DecodeMsg(dc) if err != nil { err = msgp.WrapError(err, "Info") return } default:
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sun Sep 28 20:59:21 UTC 2025 - 26.8K bytes - Viewed (0) -
cmd/erasure-server-pool-rebalance.go
NumVersions uint64 `json:"numVersions" msg:"nv"` // Number of versions rebalanced Bytes uint64 `json:"bytes" msg:"bs"` // Number of bytes rebalanced Participating bool `json:"participating" msg:"par"` Info rebalanceInfo `json:"info" msg:"inf"` } func (rs *rebalanceStats) update(bucket string, fi FileInfo) { if fi.IsLatest { rs.NumObjects++ }
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sun Sep 28 20:59:21 UTC 2025 - 28.7K bytes - Viewed (0) -
docs/logging/README.md
- Pool number the object operation was performed on. - Set number the object operation was performed on. - The list of drives participating in this operation belong to the set. ```json { "version": "1", "deploymentid": "90e81272-45d9-4fe8-9c45-c9a7322bf4b5", "time": "2024-05-09T07:38:10.449688982Z", "event": "", "trigger": "incoming",Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 10.5K bytes - Viewed (0) -
docs/bucket/replication/DESIGN.md
replication, the replication status is reflected as `PENDING`. If 3 or more targets are participating in active-active replication, the replication configuration for replica metadata sync, delete marker replication and delete replication should match to avoid inconsistent picture between the clusters. It is not recommended to turn on asymmetric replication - for e.g. if three sites A,B,C are participating in replication, it would be better to avoid replication setups like A -> [B, C], B -> A. In...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 14.7K bytes - Viewed (0) -
cmd/object-api-interface.go
// mainly set for certain WRITE operations. SkipDecommissioned bool // SkipRebalancing should be set to 'true' if the call should skip pools // participating in a rebalance operation. Typically set for 'write' operations. SkipRebalancing bool SrcPoolIdx int // set by PutObject/CompleteMultipart operations due to rebalance; used to prevent rebalance src, dst pools to be the same
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sun Sep 28 20:59:21 UTC 2025 - 17.5K bytes - Viewed (0) -
cmd/notification.go
} } if pools, ok := objAPI.(*erasureServerPools); ok { pools.StopRebalance() } } // LoadRebalanceMeta notifies all peers to load rebalance.bin from object layer. // Note: Only peers participating in rebalance operation, namely the first node // in each pool will load rebalance.bin. func (sys *NotificationSys) LoadRebalanceMeta(ctx context.Context, startRebalance bool) { ng := WithNPeers(len(sys.peerClients))Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sun Sep 28 20:59:21 UTC 2025 - 46K bytes - Viewed (0) -
impl/maven-core/src/site/apt/offline-mode.apt
behaviors behind a consistent user interface is much, much more difficult if the system can't tell whether it has access to the network required by these operations. Offline mode really means anticipating a lack of network connectivity, and as a result turning off certain services provided by m2 and providing a coherent way of predicting and reporting when network-related failures will take place.
Registered: Sun Dec 28 03:35:09 UTC 2025 - Last Modified: Sat Apr 05 11:52:05 UTC 2025 - 10.6K bytes - Viewed (0)