Problem: An application UPDATE statement against a partitioned PostgreSQL table (UPDATE tab1 SET sys_update_date = $1, agg_status = $2, output_filename = $3, merge_type = $4 WHERE period_key = $5 and record_id = $6) experienced consistent slowdowns in a nightly early‑morning window. The customer reported that partition file sizes showed normal small footprints for partitions p1–p12, […]
Case Studies Data Management and Analytics Database 25 Feb 2026 Resolving Redis timeouts caused by Redisson MapCache eviction and Lua blockingProblem: Applications using Redisson MapCache began throwing RedisResponseTimeoutException errors (client timeout = 3000 ms) during eviction activity. Errors were raised while executing EVALSHA with context pointing to org.redisson.eviction.MapCacheEvictionTask; application threads were reporting “Unable to evict elements” outputs correlated with redisson-timer-* threads. Environment details: a Redis Cluster (client traffic on shard port 7000) served multiple integration […]
Case Studies Data Management and Analytics Database 30 Jan 2026 PostgreSQL Predicate Pushdown OptimizationProblem: The customer reported degraded performance in a PostgreSQL query joining multiple views and tables, including V_PARTY_RELATIONSHIP. Although the outer query applied a highly selective filter (C.FIRST_PARTY_KEY = '<party_key>'), the PostgreSQL optimizer did not push this predicate into the view. As a result, the view was fully evaluated, leading to increased CPU usage, higher I/O, […]
Database 3 Dec 2025 PostgreSQL Patroni FailoverProblem: The client experienced an unexpected failover in a production PostgreSQL Patroni cluster running PostgreSQL Community version 15.8 and Patroni version 2.1.4 configured in asynchronous replication mode. Node A unexpectedly went offline and Patroni automatically promoted Node B to the primary node. The client needed to determine: The reason for the failover. Whether any transactions […]
Database 24 Nov 2025 PostgreSQL: Autovacuum Failures After Database RestoreProblem: After restoring a PostgreSQL 15.8 database from an enterprise backup tool, the client noticed multiple errors during startup. Autovacuum began trying to remove temporary tables, but instead reported issues such as: “Dropping orphan temp table” “pg_attribute catalog is missing attributes” Indexes and constraints appearing only partially restored About 30 temp tables were affected, and […]
Database 3 Nov 2025 Handling DDL Changes and Replication Issues in Multi-DC Cassandra SetupProblem: The client operates a 6-node multi-DC replication setup for Cassandra, consisting of 3 nodes in the PROD datacenter and 3 nodes in the DR datacenter. They are planning to perform DDL changes, including altering tables to adjust the default_time_to_live parameter and dropping and recreating a table with a new definition. However, they are unsure […]
Database 3 Nov 2025 Apache Cassandra: Migration Connectivity Failure During Production DeploymentProblem: The client encountered a critical issue while starting one of their production pods during a Cassandra migration. Although the PostgreSQL migration completed successfully, the Cassandra migration failed with a com.datastax.oss.driver.api.core.AllNodesFailedException, indicating that the driver could not connect to any Cassandra nodes. This blocked the production deployment. Process: Step 1: Initial Analysis The logs revealed […]
Database 1 Aug 2025 Correcting Rack Configuration and Ensuring Topology Consistency in a Multi-Datacenter Cassandra ClusterProblem: A client managing a multi-datacenter Apache Cassandra setup observed an inconsistency in rack configuration between two datacenters. In the primary datacenter (`dc1`), all three nodes were configured with the same rack identifier (`rack1`), whereas in the secondary datacenter (`drdc`), each node was correctly configured with unique rack values (`rack1`, `rack2`, `rack3`). This raised concerns […]
Database 25 Jul 2025 Mitigating Disk Overflow and Repair Issues in Apache Cassandra DR SetupProblem: The client encountered a critical issue in their Apache Cassandra setup: the Disaster Recovery (DR) cluster was consuming significantly more filesystem (FS) space than the primary cluster, despite having the same data replication strategy. As a result, one of the DR nodes hit 100% disk usage, causing the replica to go down. The client […]
Database