-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Jaeger Query throws Error 400 (Bad Request): all shards failed [type=search_phase_execution_exception] #2718
Comments
Collectors log
which looks like trace data is successfully written. But trace data is failed at ES with
I believe, https://github.com/jaegertracing/jaeger/blob/master/plugin/storage/es/mappings/jaeger-span-7.json#L58 must be data type long instead of integer. Same applies here https://github.com/jaegertracing/jaeger/blob/master/plugin/storage/es/mappings/jaeger-span.json#L65 |
Query doesn't work when I create templates for service and span:
|
@aug70 please provide the steps to reproduce this locally. FWIW, the integer type |
hi @aug70. the mapping will be changed to
|
That sounds odd. Would it happen during a regular upgrade from the older version to the new one as well? Would you need to delete indexes to use the newer collector? It should not be the case. |
@flf2ko it might be the case, because I had HotRod and my app creating indexes at the same time. I'm suspecting that's what caused this error. Unfortunately I have no access to the collectors, I had to have somebody to stop them so I could delete the indexes and restarted collectors. Problem solved after starting fresh. But it was an inconvenience. |
Running into this again! Just upgraded to Helm Jaeger version 0.43.3 and jaeger 1.22.0
|
@jpkrohling I don't know what other info I can provide you? Please remove the |
@aug70 are you able to consistently reproduce this? If I just install Jaeger 1.22.0 using the current Helm charts on a minikube instance, will I face this issue? |
hmm..I found this error would happen when do a (wildcard) query on a The mapping would be something like following format, via dynamic mapping.
In this case, the wildcard query should query on Not sure if this is the same case as your, @aug70, since I don't find any |
I think the Jaeger version between collectors and the rest of the system caused this error. I put a PR to upgrade collectors and problem is now solved. |
Is it solved after upgrading to latest Jaeger version? Which version do I need to upgrade? |
I also faced same issue.I have uninstalled jaeger and deleted jaeger indices and template and redeploy jaeger ,its started working.Mostly its happened when you change index name or shards number so very important step is to delete index template otherwise this error will come. |
Describe the bug
Jaeger UI throws
Error 400 (Bad Request): all shards failed [type=search_phase_execution_exception]
while all indices are GREEN. Collectors keep adding records but UI doesn't work or be able to show any traces.To Reproduce
Steps to reproduce the behavior:
1.
2.
3.
Expected behavior
Jaeger UI should work as expected.
Screenshots
If applicable, add screenshots to help explain your problem.
Version (please complete the following information):
What troubleshooting steps did you try?
Try to follow https://www.jaegertracing.io/docs/latest/troubleshooting/ and describe how far you were able to progress and/or which steps did not work.
Additional context
Indices are all green, ES queries work just fine. However Jaeger UI doesn't render any results.
The text was updated successfully, but these errors were encountered: