-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
ALL
-
🟦 Shard Catalog
-
None
-
None
-
None
-
None
-
None
-
None
Summary
Running create with a storageTier option on an Atlas cluster that does not support cold collections (a non-Infinite cluster) fails cleanly, but the error message names an internal feature flag instead of telling the user that cold storage is not available on their cluster:
MongoServerError[InvalidOptions]: 'storageTier' option may not be used without featureFlagCreateSupportsStorageTierOptions enabled.
Steps to reproduce
On a non-Infinite Atlas cluster (no cold collection support), in mongosh:
use coldrepro
db.createCollection("cold_coll", { storageTier: { collection: "cold" } })
Actual result
MongoServerError[InvalidOptions]: 'storageTier' option may not be used without featureFlagCreateSupportsStorageTierOptions enabled.
No collection is created (the command fails cleanly and nothing is left behind), but the error surfaces the internal feature flag name featureFlagCreateSupportsStorageTierOptions.
Expected result
A user-facing message saying cold collections are not supported on this cluster. This message already exists on other unsupported deployments: the same command on a cc-disabled Atlas cluster returns
MongoServerError[InvalidOptions]: Cold collections are not available in this deployment.
The non-Infinite gating path should return the same readable message instead of the feature-flag error.
Notes
- No data loss or bad state: the create is refused and no collection exists.
- Related: SERVER-135783 (cold collection create behavior on ASC clusters), SERVER-135777 (cold create bypassing the feature flag).