Error codes
This page contains the list of error codes emitted by Restate components.
META0003
Cannot reach the service endpoint to execute discovery. Make sure:
- The provided
URI
/ARN
is correct - The deployment is up and running
- Restate can reach the deployment through the configured
URI
/ARN
- If additional authentication is required, make sure it's configured through
additional_headers
META0004
Cannot register the provided deployment, because it conflicts with the uri of an already registered deployment.
In Restate deployments have a unique uri/arn and are immutable, thus it's not possible to discover the same deployment twice. Make sure, when updating a deployment, to assign it a new uri/arn.
You can force the override using the "force": true
field in the discover request, but beware that this can lead in-flight invocations to an unrecoverable error state.
See the versioning documentation for more information.
META0005
Cannot propagate deployment/service metadata to Restate services. If you see this error when starting Restate, this might indicate a corrupted Meta storage.
We recommend wiping the Meta storage and recreating it by registering deployments in the same order they were registered before.
META0006
Cannot register the newly discovered service revision in the provided deployment, because it conflicts with an already existing service revision.
When implementing a new service revision, make sure that:
- The service type is the same as the previous revision.
- The new revision contains at least all the handlers of the previous revision.
See the versioning documentation for more information.
META0009
The provided subscription is invalid. Subscriptions should have:
- A
source
field in the format ofkafka://<CLUSTER_NAME>/<TOPIC_NAME>
. When registering, the Kafka cluster should be configured in the Restate configuration. - A
sink
field in the format ofservice://<service_NAME>/<HANDLER_NAME>
. When registering, service and handler should be available already in the registry, meaning they have been previously registered. - Additional constraints may apply depending on the sink service type.
Please look at the Kafka documentation (for TypeScript and Java) for more details on subscriptions and event handlers.
META0010
Trying to open meta storage directory, configured via meta.storage_path
, which contains incompatible data. This indicates that your data was written with a different Restate version than you are running right now.
Suggestions:
- Up/Downgrade your Restate server to the requested version.
- Migrate your data to the requested version by running the migration scripts.
- Wipe your meta storage directory to start afresh via
rm -rf <BASE_DIR>/<NODE_NAME>/local-metadata-store
. - Configure a different meta storage directory via
meta.storage_path
.
META0011
Non-empty meta storage directory, configured via meta.storage_path
, is missing the version file. This indicates data corruption or that the data has been written with an incompatible Restate version < 0.8.
Suggestions:
- Wipe your meta storage directory to start afresh via
rm -rf <BASE_DIR>/<NODE_NAME>/local-metadata-store
. - Configure a different meta storage directory via
meta.storage_path
. - Downgrade your Restate server to <= 0.7.
META0012
Trying to register a service endpoint whose supported service protocol versions is incompatible with the server. This indicates that you have to upgrade your server to make it work together with the deployed SDK.
Suggestions:
- Check the compatibility matrix between SDK and server versions
- Try upgrading to a server version which is compatible with your SDK
- Try using an SDK version which is compatible with your server
META0013
Received a bad service discovery response from the specified service endpoint. This indicates that you are trying to register a service endpoint with an incompatible server.
Suggestions:
- Check the compatibility matrix between SDK and server versions
- Either deploy a server version which is compatible with your SDK
- Or use an SDK version which is compatible with your server