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
starts CrateDB
Option Description
------ -----------
-C <KeyValuePair> Configure a setting
-V, --version Prints CrateDB version information and exits
-h, --help show help
-s, --silent show minimal output
-v, --verbose show verbose output
ERROR: setting [node.attr.zone] must not be empty
Setting as a workaround:
spec.cluster.settings:
node.attr.zone: "test"
The text was updated successfully, but these errors were encountered:
yannic-hamann-abb
changed the title
No Azure Zone: Crate Cannot start
No Azure Zone: Crate Cannot Start
Oct 4, 2024
Could you please share environment variable settings you pass to crate-operator?
I assume envvar:: CLOUD_PROVIDER is set to azure, in which case the crate-operator assumes that the nodepools/nodes a spread over several availability zones and consults the infrastructure metaservice during startup of the POD for this information. Furthermore cluster routing allocation awareness is setup in the cratedbs, which makes limited sense if there are no AZs on the infrastructure side.
I hope that makes sense, otherwise let me know.
From documentation:
Under the hood, the operator will pass a zone attribute to all CrateDB
nodes. This attribute can also be defined explicitly or override the one set
by the operator. To do this on a cluster level, set .spec.cluster.settings:
Just wanted to spin up some test crate cluster in Azure.
The host system is in no zone:
curl -s 'http://169.254.169.254/metadata/instance/compute/zone?api-version=2020-06-01&format=text' -H 'Metadata: true'
Returns an empty string.
Cluster start fails with:
Setting as a workaround:
The text was updated successfully, but these errors were encountered: