Issue with QUERY_DEFAULTS_LIMIT and QUERY_MAXIMUM_RESULTS

Description

We have added below to increase the query limit in our terraform file. But, it is causing service restart due to health check fail.
Prior to these variables, our Weaviate Instance was stable.

map_environment = {
“QUERY_DEFAULTS_LIMIT” = 11000
“QUERY_MAXIMUM_RESULTS” = 20000
“LIMIT_RESOURCES” = true
“GOMAXPROCS” = 1
}

Server Setup Information

  • Weaviate Server Version: 1.26
  • Deployment Method: Docker
  • Multi Node? Number of Running Nodes: Single
  • Client Language and Version: Python
  • Multitenancy?: No

@DudaNogueira

hi @saurbhhsharrma !!

Do you see any outstanding logs from server side?

was GOMAXPROCS and LIMIT_RESOURCES already set before this change?

do you have any readings on resource usage?

The logs aren’t having much information. Neither, it is showing any error.

We have already set GOMAXPROCS and LIMIT_RESOURCES before this change was made.
Below were already set before this change:
LIMIT_RESOURCES : true
GOMAXPROCS: 1
Weaviate Docker config: 2vCPU, 4GB memory.

Resource usage looks normal.

I believe that because of the increase of QUERY_MAXIMUM_RESULTS, it may be failing to answer the check probe.

If you use QUERY_MAXIMUM_RESULTS with the defaults, it does get back to normal, right?

I have removed QUERY_MAXIMUM_RESULTS from the environment and it is still creating issue.

Everytime, it is failing to start and it doesn’t even print any logs for the same.
@DudaNogueira @Mohamed_Shahin

I believe this is a resource issue.

Do you still see this issue if you increase the allocated resource for this cluster?