Offer the sharding setting when creating a Fabric cluster

Aperta
#2,084 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
58/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
typescript

Direzione di ricerca

Start by reading Studio's create-cluster flow and configRestrictions.ts, then check how it submits cluster settings and displays errors from central-manager. Add an optional sharding section with the stated limits, compatibility checks, and read-only-after-creation behavior; keep replication restrictions unchanged. Done when the supported sharding settings validate before submission and central-manager scale-in errors appear unchanged.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Problem

Central-manager accepts sharding: { shards, minOwners } on POST /Cluster (HarperFast/central-manager#527), for Harper 5.4 schema-defined sharding. Studio's create-cluster flow has no way to set it, so a sharded Fabric cluster can only be created through the API. Studio's configRestrictions.ts blocks editing replication except databases, which should stay as it is: shard settings are managed by Fabric, not by node config edits.

Proposed

An optional sharding section in the create-cluster flow:

  • Shards: 2 to 256.
  • Owners per shard (minOwners): default 2; 1 allowed, with a warning that losing that one owner loses the shard's records for good.
  • Validate before submit as central-manager does: Harper 5.4.0-beta.3 or later, a hosted (not self-hosted) cluster with region plans, and at least shards * minOwners instances across the chosen plans. Central-manager answers 400 with the reason otherwise.
  • After creation the setting is read-only. It cannot be changed or turned on later (HarperFast/central-manager#1158 covers enabling on an existing cluster, HarperFast/central-manager#1159 changing the shard count).

On scale-in, central-manager refuses a change that would leave a shard with fewer than minOwners running owners and names the shard. Studio should show that message as is.

Not in scope

Showing shard ownership on the cluster page is #2081 and is not part of this issue.

🤖 Generated by Anthropic Claude Code (Claude Opus); posted via @kriszyp.

Lingua principale
TypeScript
Stelle
5
Fork
4
Merge medio
2g 13h
PR unite (30g)
60

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di HarperFast/studio

Tutte le issue di HarperFast/studio

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.