-
Notifications
You must be signed in to change notification settings - Fork 237
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
Cortex will fail to run analyzers #182
Comments
I was able to get Cortex to fail in this way again. Here are the logs:
|
Lastly, here is the query from the elastic logs:
|
I've confirmed that this portion of the query is breaking it:
I can reproduce the error consistently by reposting this query. What is weird is that it only fails on 2 of the 5 shards
|
Lastly, just to ensure that there wasn't anything wrong with my instance of elasticsearch, I installed a brand new instance and tested the same query. It reacted in the same manner. |
So, not being really well versed in scala, I think I ended up finding the issue. In 8e570b1 the data field was changed from F.stringFmt to F.rawFmt. The e4p model has this defined as a binary field. The only thing I can't figure out is why this only happens some of the time. |
Sorry for the late answer. This problem is related to #178. The format of the data to analyze has changed in order to remove its size limitation. The data is stores using binary mapping, and become unsearchable. This breaks job creation if cache is enable because Cortex searches old similar jobs (with the same data). To solve this issue, I've added a cacheTag attribute which contains a hash of job information (data, dataType, tlp, analyzer/responder ID and parameters). |
Hi! I mention it here, because I think it's related. |
hi @joseluratm some reason parameters is not picking up even though i have specified same as api doc. |
Request Type
Bug
Work Environment
Problem Description
Cortex fails to run analyzers, returning the error "Binary fields do not support searching". This does not happen all the time, but once it starts, much like popping a can of Pringles, it just doesn't stop. I attempted using a fresh index of the database and this did not fix the issue either. I had to roll back to version 2. Running the analyzers from Cortex or TheHive made no difference.
Steps to Reproduce
Complementary information
log entry from the hive
The text was updated successfully, but these errors were encountered: