Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No Azure Zone: Crate Cannot Start #660

Open
yannic-hamann-abb opened this issue Oct 4, 2024 · 1 comment
Open

No Azure Zone: Crate Cannot Start #660

yannic-hamann-abb opened this issue Oct 4, 2024 · 1 comment

Comments

@yannic-hamann-abb
Copy link

yannic-hamann-abb commented Oct 4, 2024

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:

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"
@yannic-hamann-abb yannic-hamann-abb changed the title No Azure Zone: Crate Cannot start No Azure Zone: Crate Cannot Start Oct 4, 2024
@WalBeh
Copy link
Contributor

WalBeh commented Oct 16, 2024

Hi @yannic-hamann-abb, first of all apologies for the late response!

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:

  kind: CrateDB
  spec:
    cluster:
      settings:
        node.attr.zone: "some-value"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants