Database

Problem: The client seeks to configure SSL communication within an existing Patroni/etcd/Postgres cluster, specifically aiming to switch to HTTPS in the Patroni configuration file to secure communication between components. Solution: After a thorough analysis, the following recommendations were made: Certificate Generation Utilize OpenSSL or obtain a certificate from a trusted Certificate Authority (CA). For self-signed […]

Problem: The client is experiencing high read latency in their production cluster monitoring. They are seeking assistance in identifying the cause of this latency and resolving it to prevent potential outages. Process: Steps and measures undertaken to investigate the issue: Initial Assessment: Requested logs/config from all nodes. Observed server overload or potential network issues. Configuration […]

Problem: A leading organization in the tech sector sought to optimize their database infrastructure by deploying MongoDB with a focus on scalability, security, and reliability. They required comprehensive guidance on deployment, load balancing, TLS implementation, role-based access control (RBAC), backup strategies, monitoring, and auditing to ensure a seamless transition to a production-ready environment. The client […]

Problem: The client requires Active Directory/LDAP integration for MongoDB user management similar to the Enterprise edition of MongoDB. This includes managing user permissions, creation, and deletion. Solution: To address the reported requirements, several potential solutions were put forth. Resolution 1. Utilize Percona MongoDB with LDAP Support: Implement LDAP support through Percona MongoDB. Conducted a Proof […]

Problem: The issue stems from confusion surrounding the Replication Factor (RF) in Apache Cassandra, where the documentation implies RF determines the quantity of data copies, but clarity on this matter is lacking. Process: To address this issue, in-depth investigation took place. The team explored the information provided by the client: Cassandra Configurations: Cassandra Version: 4.0.1 […]

Problem: The system is generating alerts indicating replication lag on the “productCatalog” PostgreSQL instance, specifically targeting the machine “pa3fnd02.” However, upon DBA investigation, there is no observable lag in the cluster, with both the leader (pa3fnd02) and the sync standby (pa3fnd01) reporting no lag. The discrepancy raises concerns about the persistence of alerts despite the […]

Problem: The organization is using Cassandra 4.0.x in its Production environment and requires tracking login and logout details from the Cassandra Audit logs. However, the Audit logs only record LOGIN_SUCCESS, LOGIN_ERROR, and UNAUTHORIZED_ATTEMPT events, with no mention of LOGOUT events. The organization seeks clarification on mechanisms for capturing logout-related entries. Solution: Cassandra does not inherently […]

Problem: The client operates a 6-node multi-DC replication setup for Cassandra, consisting of 3 nodes in the PROD datacenter (East US2) and 3 nodes in the DR datacenter (West US2). 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. […]

Problem: The Production (Prod) and Disaster Recovery (DR) environments for Cassandra databases exhibit different sizes, as observed from the nodetool status output. The client needs to identify the reason behind this discrepancy and ensure the readiness and reliability of the Disaster Recovery environment for use in the event of a failure. Process: The client provided […]