JAX

From Server rent store
Jump to navigation Jump to search
  1. JAX Server Configuration

This article details the JAX server configuration, a high-performance server cluster designed to support our growing MediaWiki infrastructure. It is intended for newcomers responsible for server maintenance, troubleshooting, and future expansion. This document covers hardware specifications, software configuration, network topology, and maintenance procedures. Understanding this configuration is crucial for ensuring the stability and performance of our wiki.

Overview

JAX represents a significant upgrade to our previous server setup, utilizing modern hardware and optimized software configurations to handle increased traffic and data storage demands. It’s a clustered environment comprised of several specialized nodes, each with a specific role in delivering wiki content. The primary goals of the JAX configuration are high availability, scalability, and improved performance for all users. The entire cluster is monitored by Monitoring Dashboard and alerts are sent via Alerting System.

Hardware Specifications

The JAX cluster consists of four primary node types: Web Servers, Database Servers, Cache Servers, and a dedicated Storage Node. Each node type has specific hardware requirements, detailed below.

Node Type CPU Memory (RAM) Storage (SSD) Network Interface
Web Servers (3 nodes) 2x Intel Xeon Gold 6248R @ 3.0 GHz 128 GB DDR4 ECC 1 TB NVMe SSD (RAID 1) 10 Gbps Ethernet
Database Servers (2 nodes) 2x Intel Xeon Platinum 8280 @ 2.5 GHz 256 GB DDR4 ECC 2 TB NVMe SSD (RAID 1) 10 Gbps Ethernet
Cache Servers (4 nodes) 2x Intel Xeon Silver 4210 @ 2.1 GHz 64 GB DDR4 ECC 500 GB NVMe SSD 10 Gbps Ethernet
Storage Node (1 node) 2x Intel Xeon Gold 6338 @ 2.0 GHz 512 GB DDR4 ECC 32 TB SAS HDD (RAID 6) 25 Gbps Ethernet

These specifications were chosen to provide optimal performance for the expected workload. Note the use of NVMe SSDs for all servers requiring fast read/write access. The Storage Node utilizes traditional SAS HDDs optimized for capacity and redundancy. For further details on hardware procurement see Hardware Inventory.

Software Configuration

The JAX cluster runs a dedicated installation of Ubuntu Server 22.04 LTS. All nodes utilize a consistent software stack to ensure compatibility and simplify management.

Software Version Purpose Node Type(s)
Operating System Ubuntu Server 22.04 LTS Base Operating System All
Web Server Apache 2.4 Handles HTTP requests and serves wiki pages. Web Servers
PHP 8.1 Processes wiki logic and interacts with the database. Web Servers
MariaDB 10.6 Stores wiki content and metadata. Database Servers
Redis 6.2 Caching layer for frequently accessed data. Cache Servers
Load Balancer HAProxy 2.4 Distributes traffic across web servers. All (configured, active on Web Servers)

The configuration files for each service are managed using Ansible, allowing for automated deployments and consistent configurations across the cluster. Detailed configuration examples can be found in the Configuration Repository. Security patching is handled automatically via Unattended Upgrades.

Network Topology

The JAX cluster utilizes a dedicated VLAN for internal communication.

Component IP Address Range Purpose
Web Servers 192.168.10.101-192.168.10.103 Serve wiki pages to users.
Database Servers 192.168.10.201-192.168.10.202 Store and manage wiki data.
Cache Servers 192.168.10.301-192.168.10.304 Provide caching services.
Storage Node 192.168.10.401 Provide storage services.
Load Balancer (HAProxy) 192.168.10.1 Distribute traffic to Web Servers.

All communication between nodes is encrypted using TLS. External access is provided through a firewall managed by the Network Security Team. The DNS records are managed by DNS Management.

Maintenance Procedures

Regular maintenance is crucial for ensuring the continued stability and performance of the JAX cluster. This includes:

  • **Log Rotation:** Logs are rotated daily and archived for 30 days. See Log Management.
  • **Database Backups:** Full database backups are performed nightly and incremental backups are performed hourly. These backups are stored on the Storage Node and offsite. See Backup Procedures.
  • **Security Updates:** Security updates are applied automatically using Unattended Upgrades.
  • **Performance Monitoring:** The Monitoring Dashboard is monitored regularly for performance bottlenecks and anomalies.
  • **Capacity Planning:** Storage capacity and server load are monitored to anticipate future needs. See Capacity Planning Documentation.


Troubleshooting

Common issues and their resolution can be found in the Troubleshooting Guide. For critical incidents, contact the On-Call Schedule.


Intel-Based Server Configurations

Configuration Specifications Benchmark
Core i7-6700K/7700 Server 64 GB DDR4, NVMe SSD 2 x 512 GB CPU Benchmark: 8046
Core i7-8700 Server 64 GB DDR4, NVMe SSD 2x1 TB CPU Benchmark: 13124
Core i9-9900K Server 128 GB DDR4, NVMe SSD 2 x 1 TB CPU Benchmark: 49969
Core i9-13900 Server (64GB) 64 GB RAM, 2x2 TB NVMe SSD
Core i9-13900 Server (128GB) 128 GB RAM, 2x2 TB NVMe SSD
Core i5-13500 Server (64GB) 64 GB RAM, 2x500 GB NVMe SSD
Core i5-13500 Server (128GB) 128 GB RAM, 2x500 GB NVMe SSD
Core i5-13500 Workstation 64 GB DDR5 RAM, 2 NVMe SSD, NVIDIA RTX 4000

AMD-Based Server Configurations

Configuration Specifications Benchmark
Ryzen 5 3600 Server 64 GB RAM, 2x480 GB NVMe CPU Benchmark: 17849
Ryzen 7 7700 Server 64 GB DDR5 RAM, 2x1 TB NVMe CPU Benchmark: 35224
Ryzen 9 5950X Server 128 GB RAM, 2x4 TB NVMe CPU Benchmark: 46045
Ryzen 9 7950X Server 128 GB DDR5 ECC, 2x2 TB NVMe CPU Benchmark: 63561
EPYC 7502P Server (128GB/1TB) 128 GB RAM, 1 TB NVMe CPU Benchmark: 48021
EPYC 7502P Server (128GB/2TB) 128 GB RAM, 2 TB NVMe CPU Benchmark: 48021
EPYC 7502P Server (128GB/4TB) 128 GB RAM, 2x2 TB NVMe CPU Benchmark: 48021
EPYC 7502P Server (256GB/1TB) 256 GB RAM, 1 TB NVMe CPU Benchmark: 48021
EPYC 7502P Server (256GB/4TB) 256 GB RAM, 2x2 TB NVMe CPU Benchmark: 48021
EPYC 9454P Server 256 GB RAM, 2x2 TB NVMe

Order Your Dedicated Server

Configure and order your ideal server configuration

Need Assistance?

⚠️ *Note: All benchmark scores are approximate and may vary based on configuration. Server availability subject to stock.* ⚠️