Skip to content

Playground zone to prepare the Elasticsearch engineer exam

Notifications You must be signed in to change notification settings

pistocop/elastic-certified-engineer

 
 

Repository files navigation

Tips on Elastic Certified Engineer Exam

outline full mapping

Relationships among Elastic Training Lessons, Elastic Exam Objectives, and Elastic Docs

Presentations

📝 Tips on Elastic Certified Engineer Exam (Chinese Version)

📝 Tips on Elastic Certified Engineer Exam (English Version)

Self-Learning Path

📝 Reorder Exam Objectives (XLSX Version)

📝 Reorder Exam Objectives (PDF Version)

Docker Environments

File Description
single_node.yml simple node env
node_role.yml cluster and node role env
elastic_security.yml elastic stack security env
backup_and_recovery.yml backup and recovery env
cross_cluster_search.yml cross cluster search env
shard_allocation.yml shard allocation env

How to Use

Startup a testing environment in foreground:

docker-compose -f your_config_file.yml up

Or Startup a testing environment in background:

docker-compose -f your_config_file.yml up -d

Shutdown a testing environment:

docker-compose -f your_config_file.yml down

Or Shutdown a test environment and delete all data:

docker-compose -f your_config_file.yml down -v

Common issues

  • Error `bootstrap check failure [1] of [1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

    • Increase the virtual memory areas - 🔗stackoverflow:
          # Change for current session: 
          $ sysctl -w vm.max_map_count=262144
      
          # Tip: modify the /etc/sysctl.conf for permanent changes
      
    • Official Elasticsearch tutorial - docs
  • Error ERROR: for <node_name> Cannot create container for service <node_name>: not a directory

    • You are probably on WSL: reboot your pc, prune (docker volume prune) the volumes and try again
  • Error FileNotFoundError: [Errno 2] No such file or directory

    • If you are on WSL and have just added a new volume:
      • Cut the container section that use the volume, but keep the volume creation
      • Run the docker-compose command
      • Paste the container section again
      • Run the docker-compose command
    • If you are on WSL and you are sure the code is correct:
      • Restart the docker desktop app
      • Close all WSL window instances
      • Reopen a WSL and clear all containers and volumes
      • Try again

About

Playground zone to prepare the Elasticsearch engineer exam

Topics

Resources

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Shell 59.8%
  • HTML 40.2%