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

Test failing -- TestElasticSearchSuite/TestSparkDependenciesES #1113

Closed
jpkrohling opened this issue Jul 3, 2020 · 4 comments · Fixed by jaegertracing/jaeger#2327
Closed
Labels
bug Something isn't working

Comments

@jpkrohling
Copy link
Contributor

The test TestElasticSearchSuite/TestSparkDependenciesES as part of es-otel is currently failing, affecting #1111, #1110 and #1105. The master branch is currently also failing after #1102 was merged, but I don't think that PR is the cause, as the failures on the mentioned PRs were happening before that got merged.

cc @kevinearls

@ghost ghost added the needs-triage New issues, in need of classification label Jul 3, 2020
@jpkrohling jpkrohling added bug Something isn't working and removed needs-triage New issues, in need of classification labels Jul 3, 2020
@moolen
Copy link
Contributor

moolen commented Jul 3, 2020

I'm looking into this. intel so far:

It boils down to a combination of TestSparkDependenciesES and TestSimpleProd. If i comment out TestSimpleProd everything works just fine.
The TestSimpleProd seems to leave some ES indices behind which confuse TestSparkDependenciesES. If we remove the indices everything works just fine.
This assumes that the TestSimpleProd runs before TestSparkDependenciesES. Unclear: why does this issue arise only when using OTEL? 🤔

Thesis: if we delete the indices created in TestSimpleProd at the end of the test run all following tests should work.

@kevinearls
Copy link
Contributor

I've been able to reproduce this, and you can see repeated stack traces in the log for the test-spark-deps-spark-dependencies cron job here:

https://gist.github.com/kevinearls/400f6d2920fbd16629078a8fcd7c0a7d

@jpkrohling unfortunately I probably won't have much time to look at this today. It might also be better to have @pavolloffay take a look if he's free. @moolen Thanks for the tip, although I'm afraid if we just change test order or clean up it may be covering up another problem. This was passing until recently.

@moolen
Copy link
Contributor

moolen commented Jul 4, 2020

I dug a little and found this in elasticsearch:

{
    "_index": "jaeger-span-2020-07-04",
    "_type": "span",
    "_id": "28USGnMBbz6bVeBZk-Ui",
    "_score": 1.0,
    "_source": {
        "traceID": "41488369ec34f3c8",
        "spanID": "41488369ec34f3c8",
        "operationName": "SmokeTest",
        "references": null, //   <------- should be []
    }
}                

This seems to be caused by returning nil here (introduced ~3d ago in jaegertracing/jaeger#2295):
https://github.com/jaegertracing/jaeger/blob/master/cmd/opentelemetry/app/exporter/elasticsearchexporter/esmodeltranslator/modeltranslator.go#L137

@yurishkuro
Copy link
Member

what about tags and logs, can they be null?

moolen added a commit to moolen/jaeger that referenced this issue Jul 4, 2020
moolen added a commit to moolen/jaeger that referenced this issue Jul 6, 2020
moolen added a commit to moolen/jaeger that referenced this issue Jul 6, 2020
moolen added a commit to moolen/jaeger that referenced this issue Jul 7, 2020
yurishkuro pushed a commit to jaegertracing/jaeger that referenced this issue Jul 7, 2020
outdoorSpirit pushed a commit to outdoorSpirit/Go-Jag that referenced this issue May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants