You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit acbe09f
Browse filesBrowse the repository at this point in the historyBrowse files
fix: Allow scaling a FeatureStore whose online store is disabled
The CEL rule that guards horizontal scaling required
services.onlineStore.persistence.store unconditionally. That made it
impossible to set spec.replicas > 1 or services.scaling.autoscaling on a
FeatureStore that sets services.onlineStore.disabled, such as a
registry-only or offline-only FeatureStore, even though no online store
pod or persistence is deployed for it. The scaling docs already say the
DB-backed requirement applies to enabled services only.
Let the online store rule also pass when the online store is explicitly
disabled. An omitted onlineStore block is still rejected, because the
operator deploys the online store with file-based defaults in that case.
The offline store and registry rules are unchanged, so a disabled online
store still needs a DB-backed, object-store or remote registry to scale.
Regenerate the CRD and dist/install.yaml, add envtest cases for static
replicas and autoscaling with a disabled online store, and document the
behaviour in the scaling guide.
Fixesfeast-dev#6865
Signed-off-by: NopeCharon <[email protected]>
Copy file name to clipboardExpand all lines: docs/how-to-guides/scaling-feast.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -118,6 +118,7 @@ The operator enforces the following rules:
118
118
- `spec.replicas > 1`and `services.scaling.autoscaling` are **mutually exclusive** -- you cannot set both.
119
119
- Scaling with `replicas > 1` or any `autoscaling` config is **rejected** if any enabled service uses file-based persistence.
120
120
- S3 (`s3://`) and GCS (`gs://`) backed registry file persistence is allowed with scaling, since these object stores support concurrent readers.
121
+
- The online store is deployed with file-based defaults when `services.onlineStore` is omitted, so it counts as an enabled service. Set `services.onlineStore.disabled: true` to scale a FeatureStore that runs only the registry, offline store, or UI.
0 commit comments