The skipped searches we have are ones that run for over an hour. Is there a way to limit by configurations the run time of queries?
There is a way to limit search execution time. You do it by role and you put the configs in authorize.conf.
For example you can limit power users to 30 minutes. This is applicable for ad-hoc or scheduled searches
[role_power]
srchMaxTime = 1800
There is a way to limit search execution time. You do it by role and you put the configs in authorize.conf.
For example you can limit power users to 30 minutes. This is applicable for ad-hoc or scheduled searches
[role_power]
srchMaxTime = 1800
That's amazing. So how come, by default, it's 100days?
Haha. I didn't know the default was 100 days.
if this is the answer you need can you accept the answer? Thanks!
Write better searches and/or add more indexers and boost the IOPs of current indexers. Can you post a sample of your query that is skipping? Does it have any joins/appends etc..?
How frequently are the searches running? Skips are expected if the runtime is longer than the search frequency