Kafka Setup with Script Code प्रकाशित: 03 जुलाई 2026 | श्रेणी: DevOps | लेखक: तकनीकी विशेषज्ञ 🌙 Dark Mode Apache Kafka एक शक्तिशाली डेटा स्ट्रीमिंग प्लेटफॉर्म है। यहाँ इसे स्क्रिप्ट कोड के ज़रिए सेटअप करने की पूरी गाइड दी गई है। Twitter LinkedIn WhatsApp चरण 1: सिस्टम जावा अपडेट काफ्का के लिए जावा आवश्यक है, इसे इंस्टॉल करने की स्क्रिप्ट नीचे दी गई है: Copy sudo apt update && sudo apt install default-jdk -y चरण 2: काफ्का डाउनलोड स्क्रिप्ट Copy wget https://apache.org tar -xzf kafka_2.13-3.5.0.tgz cd kafka_2.13-3.5.0 चरण 3: ज़ूकीपर और सर्वर स्टार्ट टर्मिनल 1 में ज़ूकीपर चलाएं: ...
When a production database CPU hits 95%, you need to act fast. Here are the exact terminal commands and infrastructure metrics to check immediately, categorized by the top database engines and monitoring tools:
1. Active Processes & Runaway Queries
Identify and stop the specific query that is consuming all the CPU cycles.
- PostgreSQL: Run
SELECT pid, age(clock_timestamp(), query_start), usename, query FROM pg_stat_activity WHERE state != 'idle' ORDER BY age DESC;to find long-running queries. If a query is stuck, kill it safely usingSELECT pg_cancel_backend(pid);. - MySQL: Run
SHOW FULL PROCESSLIST;. Sort by theTimecolumn. Look for queries stuck in "Sending data" or "Sorting" states. Terminate the rogue process usingKILL [process_id];. - MongoDB: Run
db.currentOp({"active": true, "secs_running": {$gt: 5}})to list operations running for more than 5 seconds. Terminate them usingdb.killOp(opId).
2. Traffic Spikes & Connection Counts
Determine if the CPU spike is due to a sudden surge in application workload or connection pooling failures.
- AWS CloudWatch: Check the DatabaseConnections and NetworkReceiveThroughput metrics. A sudden vertical spike points to an application loop or an external traffic surge.
- Datadog / New Relic: Look at the Queries Per Second (QPS) or Throughput graph. Compare today's volume with yesterday's baseline to confirm an anomaly.
- Action: If connection limits are breached, you may need to temporarily scale up your connection pooler (like PgBouncer) or apply rate-limiting on the application side.
3. Resource Contention (Memory & Disk I/O)
Ensure the CPU isn't choking because it is waiting on storage or running out of RAM.
- Disk I/O Bottleneck: Check ReadIOPS and WriteIOPS in your cloud console. If the database is hitting its maximum IOPS limit, the CPU will get stuck in an
iowaitstate, driving up CPU utilization.
- Memory Swapping: Use server commands like
toporfree -mto check Swap Usage. If the OS is actively swapping memory to disk because the database ran out of RAM, CPU performance will instantly collapse.
To help you troubleshoot further or prevent this from happening again, tell me:
- Which specific database and version are you using?
- Was there a recent code deployment, automated cron job, or data migration scheduled around the time of the spike?
- Do you have slow query logging enabled?
Comments
Post a Comment