bitflicker64 commented on PR #3132: URL: https://github.com/apache/hugegraph/pull/3132#issuecomment-5170912569
0ebd2dc0 addresses the deployment-side feedback from testing: - Fresh installs now seed PD with `partition.default-shard-count` derived from the Store count (3 with three or more Stores, otherwise 1, matching PD's odd-only constraint), so a default install gets store-level HA instead of one shard replica per partition. Verified on a fresh 1 PD + 3 Store cluster: 12/12 partitions with 3 shards on 3 distinct stores. The seed applies at first bootstrap only; PD metadata is authoritative afterwards, and the initial partition count change (36 to 12 on defaults) is documented. - `pd.antiAffinity` and `store.antiAffinity` default to `preferred` so single-node and small clusters schedule out of the box; `values-cluster.yaml` keeps `required`, and NOTES warns when PD quorum members may co-locate. - Per-component `nodeSelector`, `tolerations`, `affinity`, and `topologySpreadConstraints` were already supported; the README now has a Scheduling section making that visible. - The Disaster Recovery section documents the manual `/v1/task/patrolPartitions`, `/v1/task/balanceLeaders`, and `/v1/task/balancePartitions` triggers, and explains why `pd.patrol-interval` and `store.max-down-time` are not exposed: current builds bind but never read them. Periodic leader balancing and recovery metrics are filed as #3135 and #3136, and the CreateGraph propagation window as #3137. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
