ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #mysql
Recovery needs to recreate the working service and its required data after a machine or process is lost. Which artifacts and state need protection, and how should the restore be checked?
Transactional Migrations vs. Disabling Transactions The goal is to deploy schema changes in a small application without downtime. Knex runs migrations inside a transaction by default, ensuring atomicity, but MySQL 5.7+ rejects certain ALTER TABLE statements that cannot be executed transactionally. Setting migrations: { transaction: false } allows those ALTER
MLMD schema mismatch after Kubeflow Pipelines database restore Restoring the ML Metadata (MLMD) MySQL database for Kubeflow Pipelines should recover pipeline execution history. The restored schema must match the version expected by the deployed KFP control plane, or the UI may fail to reconcile executions. A restored MLMD store can also reference artifacts i
Goal Define alert thresholds for MySQL metrics exposed by mysqld_exporter that remain actionable across fluctuating workloads, including batch jobs and backup windows, while keeping the alerting pipeline simple enough for a small operations team. Constraints Static thresholds are easy to maintain but generate noise during predictable load spikes; dynamic or
When a mysql_upgrade operation is terminated unexpectedly, it is unclear whether InnoDB’s redo‑log entries have been fully flushed before crash‑recovery begins. The upgrade utility may consider partially upgraded tables as still requiring changes, and foreign‑key constraints remain enabled, creating ambiguity about data integrity. How can we verify that all
Goal: obtain predictable pagination results for a JPQL/HQL query that uses fetch joins on a OneToMany association and includes an ORDER BY clause when upgrading from Hibernate 5.6 to 6.0 with the MySQL dialect. In Hibernate 5.6 the limit/offset is applied before distinct root‑entity filtering, which can cause duplicate root rows in the result set. Hibernate
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
We are planning a schema migration for a small MySQL 8.0 application and want to avoid visible downtime. The plan uses ALTER TABLE with ALGORITHM=INPLACE and LOCK=NONE , documented to permit concurrent DML for most of the operation. However, MySQL still requires a brief exclusive metadata lock at the start and end of the DDL to install the new table definiti
knexjs
kubeflow
prometheus
hibernate