This message was deleted.

That seems to be related to this exception code: https://github.com/vesoft-inc/nebula/blob/793c914be1700adf12aac7b2fd40bc83b66e08fd/src/clients/meta/MetaClient.cpp#L893 Which gets thrown in a number of situations where the number of replicas in your cluster do not seem to be equal to the number of zones: https://github.com/search?q=repo%3Avesoft-inc%2Fnebula%20E_ZONE_NOT_ENOUG&type=code Do you have storage nodes down while attempting to make schema changes, maybe?

Hi @Zack, this refers to available storage hosts is not enough. Most possible cases are. • One storage hosts, but creating space with 3-replica factor • First time started cluster, storage host was not acitvated, to activate storage hosts, just do

ADD HOSTS

refer to: https://docs.nebula-graph.io/3.6.0/4.deployment-and-installation/manage-storage-host/

SHOW HOSTS;

ADD HOSTS "hostname_or_ip0":9779, "hostname_or_ip1":9779, "hostname_or_ip2":9779;

Thanks @wey ! Definitely sounds like the latter. One recommendation, it would be helpful to have more details with this error and others that includes actionable advice. Btw, great presentation today at the workshop!

Wow Thanks Zack! I’m thinking of how to mitigate this strange error 🫡