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

Apicurio throwing io.apicurio.registry.storage.ArtifactNotFoundException while uploading a new artifact #1926

Closed
nehasewda opened this issue Oct 11, 2021 · 11 comments
Assignees
Labels
type/bug Something isn't working

Comments

@nehasewda
Copy link

While trying upload a new artifact via Apicurio registry UI, getting io.apicurio.registry.storage.ArtifactNotFoundException.
Kindly help.

@carlesarnal
Copy link
Member

carlesarnal commented Oct 13, 2021

@nehasewda do you mind please adding some context here? More specifically:

  • Apicurio Registry version
  • Some steps with the operation you're trying to perform
  • Example data in case you think it might be a problem with data format or something like that (e.g. artifactId is being sent as header)

Thanks

@EricWittmann
Copy link
Member

@nehasewda ping

@nehasewda
Copy link
Author

Sorry for the delay.

  1. Apicurio image used - apicurio/apicurio-registry-kafkasql:latest-snapshot
  2. Trying to upload an artifact with an ID "out-stream" with a valid json schema.
  3. Got the following error "io.apicurio.registry.storage.ArtifactNotFoundException artifact with ID out-stream not found".

Strangely, I was able to upload the same mentioned artifact after few retries.

@EricWittmann EricWittmann added the type/bug Something isn't working label Oct 25, 2021
@EricWittmann
Copy link
Member

I don't suppose you still have any server logs? :) I'm not actually sure that will help, but it's always worth a look.

@carlesarnal when you have some bandwidth to look at this, could you analyze the Create Artifact flow when using KafkaSQL as the storage and see if you can determine how ArtifactNotFoundException could occur? That's obviously an unusual exception to get when creating an artifact.

@nehasewda were you using the UI for this?

@nehasewda
Copy link
Author

Hi @EricWittmann ,

Actually, this issue is intermittent. Therefore, not able to fetch the server logs at this moment(successfully updating new artifact as of now).

And yes, I was using the UI to upload new artifacts.

@EricWittmann
Copy link
Member

OK thanks @nehasewda - intermittent is the worst kind! We'll keep trying to analyze it, but if you experience it again and can get the server logs and any stack traces that appear in the browser, that would be super helpful. In addition, if it's possible to get a dump of the kafka topic, that would be even better. Something like this:

kafkacat -b localhost:9092 -t kafkasql-journal -Z -O -D \\n--message-delimiter--\\n -e -K \\n----\\n -J > kafkacat-output-2.log

If you have proprietary schemas in there I understand. But if not, that full export of all the messages in the topic would be amazing.

@nehasewda
Copy link
Author

Sure @EricWittmann . I will keep a track and pass the information as soon as I encounter this again.
Thanks for the help.

@EricWittmann
Copy link
Member

@nehasewda I think we may figured out the root cause of this issue:

#1993

@EricWittmann
Copy link
Member

We should have a blog post about this issue we can point you to soon.

@nehasewda
Copy link
Author

@EricWittmann sure. Thanks!

@EricWittmann
Copy link
Member

We are confident that this has been fixed in #2030

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants