iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
A production Elasticsearch cluster on Ubuntu is more than an package install. You must prepare the operating system, bind Elasticsearch to a routable address, satisfy its bootstrap checks, configure discovery correctly, enable TLS, and protect the data with snapshots. This guide builds a secure three-node-capable cluster, explains the one-time bootstrap settings, and shows how to add nodes without creating a second cluster or losing data.
What makes an Elasticsearch installation production-ready?
Elasticsearch starts in development mode when it listens only on loopback. The moment you set network.host to a non-loopback address, Elasticsearch assumes that the node is moving to production mode. Checks that were warnings become startup-blocking exceptions. Those checks cover operating-system and JVM prerequisites such as file-descriptor capacity and virtual-memory settings. A node that fails them must be fixed before it is exposed to clients or other cluster members.
Free tools Windows power users keep installed
One-click scans. No signup required.
Production also means that the cluster has a deliberate identity, a failure-domain design, encrypted communication, controlled access, durable storage, and a recovery plan. Installing the package and seeing port 9200 answer is only the beginning.
- Identity: every node uses the same environment-specific
cluster.name; each instance has its ownnode.name. - Discovery: master-eligible nodes are listed in
discovery.seed_hosts, with a one-time initial election list. - Network: the HTTP interface is reachable only where required, while the transport network remains private.
- Security: TLS certificates and authentication are enabled rather than disabled for convenience.
- Recovery: snapshots are stored outside the cluster and restores are tested.
Choose the deployment model and topology
Elastic documents several deployment choices: self-managed Linux packages, Elastic Cloud Hosted, Elastic Cloud Serverless, and Elastic Cloud on Kubernetes. This procedure is for a self-managed Ubuntu installation, where you own operating-system patching, Elasticsearch upgrades, certificates, network controls, capacity planning, and recovery testing.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
Use dedicated hosts for production whenever possible. If that is not practical, Elasticsearch should be the primary resource-intensive service on each host; competing workloads make memory pressure, disk latency, and failure analysis harder to control.
A practical three-node layout
A common starting point is three master-eligible nodes distributed across separate failure domains. Data roles and the number of data nodes must be sized from indexing rate, query load, retention, shard count, and recovery objectives; there is no universal node count that fits every workload.
| Component | Typical default port | Network policy |
|---|---|---|
| Elasticsearch HTTP/REST | 9200-series | Allow only approved clients, administration hosts, and monitoring systems. |
| Elasticsearch transport | 9300-series | Keep private; allow only cluster peers and the ports required for node formation. |
| Kibana | 5601 | Expose only to users or a reverse proxy that needs the interface. |
Use a unique cluster name for each environment. Reusing a name such as production in development, staging, and production makes operator mistakes more likely and complicates automation. The name is shared by all members of one cluster; node.name identifies one instance and must not be copied unchanged to another host.
Prepare Ubuntu before installing Elasticsearch
Verify release support
Check Elastic’s current support matrix for the exact Elasticsearch release and Ubuntu version you plan to run. Support varies by release, so do not infer compatibility from an older installation guide. Keep the Elasticsearch version consistent across the initial cluster unless the release documentation explicitly permits a rolling upgrade path.
Install from a signed Debian package
Elastic’s Debian package is the normal Ubuntu workflow. You can install it from Elastic’s repository or download the package directly. In either case, verify the package signature with Elastic’s published signing key before installation. The package includes a bundled OpenJDK, so a separate Java installation is normally unnecessary; adding an unrelated JVM can create version and service-account confusion.
After configuring the signed repository according to the release documentation, the package installation itself is:
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11sudo apt-get update
sudo apt-get install elasticsearchThe package places configuration under /etc/elasticsearch/, data under a service-owned data directory, logs under /var/log/elasticsearch/, and executable tools under /usr/share/elasticsearch/bin/. Confirm those paths on the installed package before changing ownership or applying automation.
Apply the important system settings
Before the first production start, apply Elastic’s documented Important Elasticsearch settings for the chosen release. Pay particular attention to file-descriptor limits, virtual-memory requirements, and any other bootstrap-check prerequisites. Then start Elasticsearch once in a controlled maintenance window and read the service log. A non-loopback network.host turns a failed prerequisite into a fatal startup error, which is preferable to running an apparently healthy but unsafe node.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
Use both of these views when diagnosing startup:
sudo systemctl status elasticsearch.service
sudo journalctl -u elasticsearch.service -bDo not proceed to firewall exposure until the checks pass cleanly. Fix the operating system or JVM setting named in the error, restart, and confirm that the same check no longer fails.
Configure the first node
Edit /etc/elasticsearch/elasticsearch.yml. The following illustrates a three-node cluster whose hosts have private addresses. Replace the example names and addresses with values from your own environment; do not copy the same node.name to another host.
Recommended Free Tools
cluster.name: 'logs-prod-eu1'
node.name: 'es-master-1'
network.host: '10.20.1.11'
transport.host: '10.20.1.11'
discovery.seed_hosts: ['10.20.1.11', '10.20.1.12', '10.20.1.13']
cluster.initial_master_nodes: ['es-master-1', 'es-master-2', 'es-master-3']
path.data: '/srv/elasticsearch/data'
path.logs: '/var/log/elasticsearch'Bind only the intended interfaces
Elastic examples sometimes use 0.0.0.0 to listen on every interface. That is useful for demonstrating connectivity but is usually too broad for a production host. Set network.host and the transport binding to the host’s intended private or service address, then enforce the same boundary with the operating-system firewall. The transport binding must be reachable by peer nodes; client access belongs on HTTP, not on the transport port.
Place data and logs on durable paths
When you control the filesystem layout, set path.data and path.logs to durable locations outside $ES_HOME. Elastic strongly recommends this separation so package upgrades or replacement of the application directory does not mingle with persistent data. Ensure that only the Elasticsearch service account can modify the data directory. Incorrect ownership or permissions will prevent startup or, worse, allow another process to corrupt files.
Do not treat a filesystem copy of the data directory as a backup. Elasticsearch data files are not a supported substitute for snapshots. Register a supported snapshot repository that survives loss of a node or the entire cluster, and plan restore tests before you need one.
Decide node roles deliberately
Three master-eligible nodes provide a sensible election foundation across failure domains, but the data tier must reflect your workload. Keep the master-eligible hosts stable and avoid placing unrelated heavy services on them. If you use dedicated data, ingest, or coordinating roles, document the role assignment and test shard allocation and recovery with production-sized data.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsBootstrap cluster formation safely
discovery.seed_hosts tells a new or restarting node where to find master-eligible peers. In a multi-host deployment, list the addresses of the master-eligible nodes, not just the first server. DNS names are acceptable when they resolve consistently from every node; fixed private addresses are often easier to troubleshoot.
cluster.initial_master_nodes is different. It is the explicit vote list for the first election of a brand-new cluster. Elastic describes this as necessary because automatic bootstrapping is unsafe in production.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
- On the initial startup only, set
cluster.initial_master_nodesto the exactnode.namevalues of the master-eligible nodes participating in that first election. - Start the initial nodes and confirm that they form one cluster with the expected cluster name.
- Remove
cluster.initial_master_nodesfrom every node’s configuration. - Never add it back for a restart, a full-cluster restart, or a node joining an existing cluster.
Leaving the setting in place after formation can cause an operator to bootstrap a separate cluster during a recovery event. That creates a split-brain-style operational disaster: each group may appear healthy while holding different cluster state.
Start Elasticsearch and complete automatic security setup
Enable the service so it returns after a planned reboot, then start it:
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →sudo systemctl daemon-reload
sudo systemctl enable elasticsearch.service
sudo systemctl start elasticsearch.serviceOn first startup, current package behavior automatically creates TLS certificates for the HTTP and transport interfaces, applies the corresponding TLS settings, sets the elastic superuser password, and creates a Kibana enrollment token. With a Debian install, the password is not printed by the systemd startup output, so reset it explicitly with the bundled tool if you did not capture it:
sudo /usr/share/elasticsearch/bin/elasticsearch-reset-password -u elasticThe Kibana enrollment token is valid for 30 minutes. Use it promptly, and generate a new one rather than trying to reuse an expired token.
Keep TLS and authentication enabled. Store passwords, enrollment tokens, and keystore secrets outside shell history and ticket systems; restrict permissions on certificate and keystore files; and give applications dedicated least-privilege accounts instead of the elastic superuser.
Enroll additional nodes
Before enrolling a host, verify that it can reach an existing node on the required HTTP and transport paths. Check routing, security groups, host firewalls, and name resolution from the new host itself. An enrollment token cannot repair a blocked network path.
Create a node enrollment token
Run this on an existing cluster node:
/usr/share/elasticsearch/bin/elasticsearch-create-enrollment-token -s nodeTokens are valid for 30 minutes. Generate a separate token for each new node and transmit it through a protected channel.
Reconfigure the new host
Install the same supported Elasticsearch package on the new Ubuntu host, stop it if it started automatically, and pass the token to the reconfiguration tool:
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
/usr/share/elasticsearch/bin/elasticsearch-reconfigure-node --enrollment-token <enrollment-token>After reconfiguration, inspect /etc/elasticsearch/elasticsearch.yml. Confirm that the joining node has the intended unique node.name, the same cluster.name, a routable network.host, and discovery settings that point to the existing master-eligible peers. Do not add cluster.initial_master_nodes to a node joining an existing cluster.
Update seed hosts after the second node
Once a second node exists, update the first node’s discovery.seed_hosts so it includes the master-eligible peers. Elastic warns that omitting the peer addresses can prevent the first node from restarting correctly. Apply the same seed list consistently across the cluster and remove the one-time initial-master setting after the original election has completed.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Verify the secured cluster
Test HTTPS with the generated CA
The package-generated HTTP CA certificate is normally at /etc/elasticsearch/certs/http_ca.crt. Test the local secured endpoint with the CA and the password stored in your secret manager:
curl --cacert /etc/elasticsearch/certs/http_ca.crt
-u elastic:$ELASTIC_PASSWORD
https://localhost:9200A successful response confirms that the process is listening, TLS validation works with the CA, and authentication succeeds. A connection refusal points to service or binding problems; a certificate error usually means the wrong CA or hostname; a 401 response means the credentials were rejected.
Check membership and allocation
Use the cluster-health and node APIs with the same CA and credentials to confirm that all expected nodes joined:
curl --cacert /etc/elasticsearch/certs/http_ca.crt
-u elastic:$ELASTIC_PASSWORD
https://localhost:9200/_cluster/health?pretty
curl --cacert /etc/elasticsearch/certs/http_ca.crt
-u elastic:$ELASTIC_PASSWORD
https://localhost:9200/_cat/nodes?vCheck that the node count matches the design, shard allocation is progressing normally, and no primary shards remain unassigned. Health thresholds and alert values should come from the workload’s recovery and availability requirements rather than an arbitrary color alone.
Backups, upgrades, and routine operations
Use snapshots, not data-directory copies
Register a supported snapshot repository on storage that survives node loss, then schedule snapshot lifecycle management appropriate to your retention requirements. Snapshots are the supported recovery mechanism. A copy of path.data while Elasticsearch is running is not a consistent, supported backup.
Regularly restore representative indices into an isolated environment. A snapshot that has never been restored is an assumption, not a recovery plan. Record the time required to restore, the credentials and repository permissions required, and the steps for redirecting applications.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Protect the transport plane
Keep transport traffic on a private network and allow only known peer addresses through host and network firewalls. Expose HTTP 9200-series ports only to approved clients and operators. If Kibana is required, expose 5601 through the intended internal route or reverse proxy. Never publish the transport port directly to the internet.
Operate with controlled changes
- Change one node or one failure domain at a time during rolling maintenance.
- Keep package versions, configuration files, certificates, and keystore changes under change control.
- Watch service logs in
/var/log/elasticsearch/during startup, enrollment, upgrades, and recovery. - Monitor disk capacity, JVM pressure, heap behavior, shard allocation, node availability, and snapshot success.
- Document which addresses are seed hosts and which nodes are master-eligible before replacing hardware.
Troubleshooting common failures
The service stops immediately after setting network.host
This is normally a failed production bootstrap check, not a discovery problem. Read journalctl -u elasticsearch.service -b and the Elasticsearch log, then correct the named file-descriptor, virtual-memory, or other operating-system requirement. Restart only after the prerequisite is actually applied.
The new node starts but does not join
- Confirm the new host uses the exact same
cluster.name. - Confirm its
node.nameis unique. - Test connectivity to the existing nodes on the transport path and verify that the firewall allows the traffic.
- Check that
discovery.seed_hostsresolves to reachable master-eligible addresses. - Inspect certificate and enrollment errors in the service log; generate a new token if the 30-minute validity window has elapsed.
The first node will not restart after another node was added
Check that the first node’s seed-host list includes the other master-eligible peers. Also verify that cluster.initial_master_nodes was removed after the original cluster formed. Do not solve a restart failure by adding the initial list back.
HTTPS testing fails
Use the CA generated for the HTTP interface, not an unrelated certificate, and connect to a hostname or address covered by the certificate. Confirm that the elastic password was reset successfully and that the shell variable used by curl contains the current value. Keep the CA and credentials protected after testing.
Primary shards remain unassigned
First confirm that all expected nodes are present and that the service logs show no disk, permission, or allocation errors. Do not delete indices or change allocation rules blindly. Resolve the underlying node, storage, or role problem, then watch allocation recover and verify health again.
Self-managed Ubuntu or a managed deployment?
A managed option can remove much of the host-level work, but it changes the trade-offs rather than eliminating them. Elastic’s managed choices include Elastic Cloud Hosted and other hosted or Kubernetes-based offerings.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →| Decision factor | Self-managed Ubuntu | Managed deployment |
|---|---|---|
| Operational ownership | You patch Ubuntu and Elasticsearch, manage certificates, tune settings, and operate the service. | The provider handles much of the platform maintenance; you still manage data, access, and application behavior. |
| Network and residency control | You choose hosts, private networks, firewall rules, and storage locations. | Controls depend on the provider’s regions, networking model, and service features. |
| Failure-domain design | You place master and data nodes across your own failure domains. | The service supplies an available design within the selected deployment options. |
| Backups and restores | You register repositories, schedule snapshots, and test restores. | Some backup mechanics may be integrated, but retention, restore testing, and application recovery remain your responsibility. |
| Scaling workflow | You provision hosts, disks, addresses, and capacity changes. | Scaling is typically performed through the managed control plane, subject to its limits and pricing. |
| Total cost | Includes infrastructure, operations, storage, networking, and staff time. | Includes service charges and any network or storage transfer costs; there is no universal cost ranking without your data volume and workload. |
Choose self-managed Ubuntu when host placement, network control, or on-premises residency is central and you have the operational capacity to maintain it. Choose a managed deployment when reducing platform maintenance is worth accepting its service boundaries and ongoing charges.
Production launch checklist
- Ubuntu and Elasticsearch versions are on the current support matrix.
- The signed Debian package and signing key were verified before installation.
- Bundled OpenJDK is used unless a documented release requirement says otherwise.
- File-descriptor, virtual-memory, and other bootstrap prerequisites pass.
- Every node has the same environment-specific
cluster.nameand a uniquenode.name. network.hostand transport binding use intended interfaces, not an unnecessarily broad listener.path.dataandpath.logsare on durable paths outside$ES_HOMEwhere controlled.- Initial master nodes were listed only for the first election and then removed.
- Seed hosts include the master-eligible peers on every relevant node.
- TLS, authentication, certificate permissions, and least-privilege application accounts are in place.
- HTTP and transport firewall rules allow only required paths.
- All expected nodes appear in the node API, allocation is healthy, and no primary shards are unassigned.
- Snapshots run to storage that survives cluster loss, and a restore has been tested in isolation.
With those controls in place, the Ubuntu package is only the delivery mechanism; the production cluster is defined by its identity, one-time bootstrap discipline, private transport network, automatic TLS, durable snapshots, and verified operating procedures.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
