Team, I get an error like this on my datahub UI (screenshot). And at the same time I could see the below messages on the log. Anyone knows what might be the reason, if anyone bumped into the same before. I assume it might be something to do with the elasticsearch docker container not running as expected. FYI - I have used the 

quickstart.sh

 to setup the installation.

kibana                    | {"type":"log","@timestamp":"2021-04-18T14:30:23Z","tags":["warning","elasticsearch","data"],"pid":7,"message":"No living connections"}
kibana                    | {"type":"log","@timestamp":"2021-04-18T14:30:23Z","tags":["warning","elasticsearch","data"],"pid":7,"message":"Unable to revive connection: <http://elasticsearch:9200/>"}
kibana                    | {"type":"log","@timestamp":"2021-04-18T14:30:23Z","tags":["warning","elasticsearch","data"],"pid":7,"message":"No living connections"}

I think the most common issues is not providing enough memory to docker. Try allocating 8GB.

Right. Can you check logs for “elasticsearch” container?

thanks @broad-flag-97458 and @early-lamp-41924 for the quick replies. Just a one more question, I assume there are multiple containers running (one for elasticsearch, mysql, neo4j etc etc..). Do I need to specify 8GB memory to a specific container or is it an overall setting for docker ?

overall setting!

@calm-addition-66352 Did this help?

I am using a CentOS box for this (but not a docker / devops guy 😄). I assume I can use something like ->

docker run -it -m 8GB --memory-swap 2G

?

so for docker-compose you may want to do something as outlined here: https://www.baeldung.com/ops/docker-memory-limit

Thanks @big-carpet-38439 , a quick question on this -

datahub/docker/*docker-compose.yml*

file has multiple services like elasticsearch, mysql, neo4j etc etc.. against which service should I set 8GB as memory ? for all services / or for a specific high memory consuming service like elasticsearch ? 🙂

i think just limiting to elasticsearch should suffice!

Thanks everyone. After I increased the memory of the elasticsearch container (as code snippet below), it seems to be working without the error

elasticsearch:
    ...
    deploy:
      resources:
        reservations:
          memory: 8192M
    ...

Woohoo!