https://linen.dev logo
Join Slack
Powered by
This message was deleted.
# troubleshooting
s
This message was deleted.
p
This is the error on the server:
Copy code
2022-11-18T14:48:38,836 ERROR [qtp857732012-81] org.apache.druid.indexing.overlord.sampler.SamplerExceptionMapper - Failed to sample data: Failed to get Avro schema: 79
org.apache.druid.indexing.overlord.sampler.SamplerException: Failed to sample data: Failed to get Avro schema: 79
	at org.apache.druid.indexing.overlord.sampler.InputSourceSampler.sample(InputSourceSampler.java:246) ~[druid-indexing-service-24.0.0.jar:24.0.0]
	at org.apache.druid.indexing.seekablestream.SeekableStreamSamplerSpec.sample(SeekableStreamSamplerSpec.java:117) ~[druid-indexing-service-24.0.0.jar:24.0.0]
	at <http://org.apache.druid.indexing.overlord.sampler.SamplerResource.post|org.apache.druid.indexing.overlord.sampler.SamplerResource.post>(SamplerResource.java:43) ~[druid-indexing-service-24.0.0.jar:24.0.0]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_275]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_275]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_275]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_275]
	at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) ~[jersey-server-1.19.4.jar:1.19.4]
	at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185) ~[jersey-server-1.19.4.jar:1.19.4]
	at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) ~[jersey-server-1.19.4.jar:1.19.4]
	at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) ~[jersey-server-1.19.4.jar:1.19.4]
	at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) ~[jersey-server-1.19.4.jar:1.19.4]
	at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) ~[jersey-server-1.19.4.jar:1.19.4]
	at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) ~[jersey-server-1.19.4.jar:1.19.4]
	at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) ~[jersey-server-1.19.4.jar:1.19.4]
	at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) ~[jersey-server-1.19.4.jar:1.19.4]
	at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) ~[jersey-server-1.19.4.jar:1.19.4]
	at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) ~[jersey-server-1.19.4.jar:1.19.4]
	at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) ~[jersey-servlet-1.19.4.jar:1.19.4]
g
It means there is some problem contacting your schema registry, like an IO error of some sort
Unfortunately the actual IO exception is not attached to the parse error you get! This patch fixes it so you would get the original error: https://github.com/apache/druid/pull/13403
I would suggest double checking your 
avroBytesDecoder
config and verifying that your registry actually does have a valid schema for id 
79
in it
If that doesn't lead you to a solution, then that original error would be very useful, so you could consider applying the patch and building a version of Druid with that
Alternatively you can try running the Confluent schema registry client yourself, with the same config, and see what error you get when trying to retrieve schema id 
79
. It is likely that you would get the same error from the schema registry client as Druid is encountering.
a
You can try to get the schema using SchemaRegistry REST API, like:
Copy code
curl -k -X GET <https://schemaregistry.organization.com:8081/schemas/ids/79>
and you can add the basic auth. too to curl if the SchemaRegistry requires authentication.
Open in Slack
PreviousNext
Powered by