-
Notifications
You must be signed in to change notification settings - Fork 640
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
Previewing alerts fails with "too many substreams open" due to case similarity process #280
Comments
Hi @Amateur-Professional, |
I would imagine so, or I wouldn't be getting this error ;) How exactly would I check that anyway? The preview fails, so I can't see it from there, and the API call fails due to the nature of the error anyway. It doesn't appear that there would be any way I could check it. |
After clearing out some old cases we no longer get the error, but that is a crappy "fix" for some undocumented, unconfigurable upper limit to related cases. Is there anything in the works to potentially adjust this? Especially since I am sure it will happen again. |
Any updates for this? We keep seeing this issue, and with no other way to preview alerts, we have to either cut our past cases, or mark alerts as read without reading them. Neither is really acceptable for a case management system. |
@To-om with our current case load we cannot keep cases around for longer than a week. We lose a ridiculous amount of data by pruning the cases to no longer show the error. We need some sort of solution, or at least some confirmation that somebody is working on it. |
I still have the problem. I am running 3.0.8 and I have the limit set to maxSimilarCases to 30. |
Hi there, I have set maxSimilarCases to 1000 and I still get the same issue. Basically, regardless of what I set the maxSimilarCases to, I still get the error when trying to open an alert with more than 100 similar cases.... |
Hello again, I am still having the problems with 3.10.0. Any idea what can be done, I am currently filtering out observables that cause the issue when creating alerts but that's not really the intention :) |
Thanks for your answers. I'm working with @raomin on this. The maxSimilarCases was taken into account after killing all JVMs on the server and then restarting TheHive and Elasticsearch |
I can provide logs, let me try the kill-all-then-restart method from above first :) |
I did kill all JVMs and rebooted the systems, no effect. I sill have the error message. Here are the logs ##################### 2018-06-08 10:42:32,226 [INFO] from org.elastic4play.ErrorHandler in application-akka.actor.default-dispatcher-1218 - GET /api/alert/8123a1f876f2e618f7deb33a28fb7826?similarity=1 returned 500 |
Request Type
Bug
Work Environment
Problem Description
Attempting to preview certain alerts gives an error:
Steps to Reproduce
Not sure. This only seems to happen sporadically. Some alerts seem to cause this error, some don't. At a guess, alerts that exceed some unwritten threshold of similar cases seem to cause this error.
Possible Solutions
The problem appears to originate when finding similar cases to a particular alert. This seems to open too many substreams (to what, I have no idea) and cause previewing the alert to fail. See logs below.
Complementary information
Log info of a failure:
The text was updated successfully, but these errors were encountered: