why?
Closed this issue · 11 comments
error
What does the response message say? It's a 400 so it should have a message. Also the API container logs should show additional information.
响应消息消息？这是一条 400 所以它应该有一条消息。此外，API 容器日志应显示其他信息。
I'm unable to read your question, can you please post in English if possible. Looking at the stack trace this can happen if there a massive amount of resolved stacks for the current filter like you are looking at all events across all projects which appears to be the case. How many stack documents do you have?
Very few
Can you tell me how many stack documents you have in your Elasticsearch index?
That's a ton of stacks. What is happening here is when we get events, we resolve stacks matching the filter criteria and then filter events based on stack ids. We did this because we found we were updating hundreds of million / billion of events all the time. We wanted to make marking a stack as fixed super fast and instant in the grid. There is still some more work todo on this. For the short term if you can filter by an event type and or project it will help greatly.
响应消息消息？这是一条 400 所以它应该有一条消息。此外，API 容器日志应显示其他信息。
好家伙，终于看到国人了。哈哈，这玩意国内教程少得可怜。。
Can you please post all replies in English or use a translator. From your stack trace, we are working on improving the search experience in the latest nightly builds.
Please try out the 7.1.0 release and leave a comment with your findings and also make sure you run the CleanupData job :).