Closed maltesander closed 1 month ago
Moving back to in progress, as we want to create one upstream Druid issues for the nimbus-jose-jwt problem
Created an upstream issue: https://github.com/apache/druid/issues/16920
Thanks. This means we can move to Druid 30 in 24.11?
I'd say yes :)
We planned on having Druid
30.0.0
in the24.7
release, which we now bailed on and marked30.0.0
as experimental.The reason were problems with integration tests and demos, especially regarding data ingestion.
Definiton of Done
Ideally the problem is identified and fixed. However, one possible outcome of this issue could be that we are not able to identifiy and fix the problem within 2-3 days. In that case we at least want to create an upsteam issue at Druid with a instructions to reproduce the issue.
Problem description
In the HDFS deep storage integration test e.g. the ingestion task fails with a null pointer exception.
@xeniape reported another null pointer exception during the nifi-kafka-druid-earthquake demo test:
and failing logs
whereas a working tasks persists:
@xeniape also found out that unit tests fail when building 30.0.0 from source
Tests from source with our mvn profile / command:
and failure for our patched builds:
The ingestion tasks seem very flaky, although more on the failing side. Ingesting a simple CSV file sometimes work and sometimes doesnt.
The problem is around the segments and persting data and should be further researched to support Druid 30.0.0
I tried remote debugging but did not spent too much time on it. Just add the line
to the jvm config and connect to localhost on port 5005 to debug the process.
@labrenbe found an unrelated error in OIDC callbacks:
Related issues (very old): https://github.com/apache/druid/issues/7662 https://github.com/apache/druid/issues/8835