Mauricio
Also on: - Kubernetes version: v1.31.1 - Kubernetes distribution: vanilla - mariadb-operator version: 0.36 - Install method: [helm, OLM, or static manifests]: helm
Still seeing this on the mariadb operator version 0.37.1 It would be great if the operator is able to run something like the following pod if there is a tc.log...
I also see this message on the replica when restarted: ``` Last_IO_Error: Fatal error: The slave I/O thread stops because master and slave have equal MariaDB server ids; these ids...
And if you are running an even newer version change the trigger recreation by this: `CREATE TRIGGER ts_insert_blocker BEFORE INSERT ON sensor_data FOR EACH ROW EXECUTE FUNCTION _timescaledb_functions.insert_blocker();`
Also happened for me when the a 3 nodes galera cluster was restarted and one node did not terminate. I had to force the dblnms-1 termination. Now they have the...
+1 on 0.37.1 kubernetes 1.31.1. Pods randomly restarting. Many timeout on operator commands as shown on the first log.
The same thing happens for BYTE_ARRAY type. In that case the workaround is to cast to TEXT.
I would say this would make pantab usable for my project. Many thanks.
Also affected by this. Removing the FK on the hypertable seems to work. It would be nice if there is a bugfix for this please.