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:
- Add the following line to the /etc/sysctl.conf file
vm.max_map_count=262144
- Stop the Jama Connect application
replicatedctl app stop --attach
- Stop the docker service
systemctl stop docker
- Reload the sysctl.conf file
sysctl -p
- Confirm the change has been made. vm.max_map_count=262144 is expected
sysctl -a | grep max_map_count
- Start the Docker service
systemctl start docker
- 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.
Related to
- Authentication
- Relationships
- Administration
- Testing
- REST API and extensibility
- Reports
- Microsoft Word
- Microsoft Excel
- Installation
- Migration
- Coverage and traceability
- Traditional
- Jama Connect Interchange™
- Customer-Validated Cloud
- Security
- Diagram/Graph Editor
- Jama Software® Subscriptions Maintenance and Support Service Agreement
- Supported
- Item Configuration
- Deployment Migration
- Integrations
Comments
0 comments
Please sign in to leave a comment.