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

Issue with creating Schema Registry object: "Register operation timed out; error code: 50002" #3135

Open
abdelrahman-a-ibrahim opened this issue May 29, 2024 · 2 comments

Comments

@abdelrahman-a-ibrahim
Copy link

Description

I am encountering an issue while deploying the Schema Registry image with imageTag 7.0.1 on Kubernetes. When attempting to create a new Schema Registry (SR) object, the operation fails with the following error message:

failed to create schema, 500, {"error_code":50002,"message":"Register operation timed out; error code: 50002"}

Steps to Reproduce

  1. Deploy the Schema Registry image with imageTag 7.0.1 on Kubernetes.
  2. Attempt to send a post request to create a new SR object.

Expected Behavior

The Schema Registry should successfully create the new SR object without errors.

Actual Behavior

The creation of the new SR object fails with a 500 error code and the message "Register operation timed out; error code: 50002".

Environment

  • Schema Registry image: confluentinc/cp-schema-registry:7.0.1
  • Kubernetes version: v1.28.9-eks-036c24b
  • Kubernetes environment: EKS Cluster
@drozd0
Copy link

drozd0 commented Aug 1, 2024

I suppose it may be an issue to connect to your Kafka cluster. Also, it may be related to #3192

@bhargav2427
Copy link

@abdelrahman-a-ibrahim are you running multiple replicas of schema registry? If yes the you need to change the advertised host for instance. In k8s, you can do like this

- name: SCHEMA_REGISTRY_HOST_NAME
   valueFrom:
      fieldRef:
        fieldPath: status.podIP

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

3 participants