ElasticSearch in production.log on Free v13.9 of GitLab?

We see the following in our production.log:

Completed 500 Internal Server Error in 28ms (ActiveRecord: 3.9ms | Elasticsearch: 0.0ms | Allocations: 13060)
Completed 500 Internal Server Error in 26ms (ActiveRecord: 3.7ms | Elasticsearch: 0.0ms | Allocations: 13047)
Completed 200 OK in 147ms (Views: 1.4ms | ActiveRecord: 24.9ms | Elasticsearch: 0.0ms | Allocations: 95007)
Completed 200 OK in 157ms (Views: 1.5ms | ActiveRecord: 25.2ms | Elasticsearch: 0.0ms | Allocations: 95001)

My understanding is that Elasticsearch is only available for the Premium License, and best I can tell, we do not have Elasticsearch installed on our GitLab VM. Why do we see ElasticSearch entries in our logs? In an attempt to resolve our seemingly random 500 Internal Server Error (happens a few times a day), are want to eliminate ElasticSearch as a possibility.

Thank you

I have gitlab-ce, and also have Elasticsearch in entries. Since it’s 0.0ms that means it didn’t do anything and is not using elasticsearch. So those don’t have anything to do with elasticsearch, your problem is somewhere else.

Check other logs for errors.

Thank you for the quick response @iwalker

We appear to have hit this bug for the same reasons. All is fine now.

1 Like