On one of our systems we had issues that - once a week - the I/O subsystem stalled and causes issues on database operations.
Upgrading a major postgres version using containers with different C libraries caused me some headaches because I go an error "database has no actual collation version, but a version was recorded" - and I did not fix it. At least I can give a hint on why it happend and how you could avoid it.
Uprading postgres with timescaledb caused me some issues related to the collation. After some retries I've found a reliable way to doing the upgrade. This post describes the steps to be done.
When hosting a multinode elasticsearch cluster, you might run in some state where indices are not equally balanced across your nodes, until one of them starts crying about high disk usage while other nodes are barely occupied - exactly this happened in one of our customers environment. In order to
To run postgres in a container on nodes with huge pages enabled requires you to configure the container accordingly. This post shows how to do this on kubernetes/openshift.
This series describes how to migrate a mysql database to timescaledb - use case is to migrate a zabbix application database. This part handles the migration and switchover of the server environment up to completion of the migration.
This part continues our mysql to timescaleDB migration. We prepare our target database and add some helpers on the source to create a resumable process.
Upgrading rocketchat to version 5.0 resulted in some minor issues that prevented the system from starting - both are related to the database and can easily be fixed.