Elasticsearch container won't start after upgrade (Native)

Author: Jason Ritz

Date: December 6th, 2023

Audience: Everyone

Environmental details: Self-hosted 

Summary: 

Changes made to Elasticsearch in Jama Connect version 8.49.x requires the max map count variable to be updated for the Elasticsearch container to start. 

Solution:

1. Add the following line to the /etc/sysctl.conf file

   vm.max_map_count=262144

2. Stop the Jama Connect application

   replicatedctl app stop --attach

3. Stop the docker service

   systemctl stop docker

4. Reload the sysctl.conf file

   sysctl -p

5. Confirm the change has been made. vm.max_map_count=262144 is expected

   sysctl -a | grep max_map_count

6. Start the Docker service

   systemctl start docker 

7. Start Jama Connect 

   replicatedctl app start

Cause:

The vm.max_map_count variable was added to the Elasticsearch library 

Additional Information/Metadata:

• Elasticsearch
• Jama Connect 8.49

Feedback: Please leave feedback in the comments below.