Die MySQL -Bereitstellung auf ASS schlägt mit Azure -Dateien -basierten PV [geschlossen] fehl. ⇐ MySql

[Anonymous]

Ich stelle MySQL in einem Azure Kubernetes -Cluster (AKS) mit dem Bitnami MySQL -Helm -Diagramm ein. Für den anhaltenden Speicher verwende ich anhaltende Volumenansprüche (PVCs), um das Datenverzeichnis für MySQL zu montieren. Ich habe die Möglichkeit, entweder Azure-Datenträger- oder Azure-Dateien als persistierendes Volumen (PV) zu verwenden. Azure-Dateien unterstützt jedoch den Access-Modus (ReadWritemany), der für Multi-Knoten-Zugriff flexibler ist. Deshalb habe ich (fälschlicherweise) Azure -Dateien zuerst gesichert und finde etwas Interessantes. Im Folgenden finden Sie die Protokolle des MySQL-Containers. Sie werden sehen, dass die Initialisierung in der InnoDB fehlgeschlagen war.2025-03-14T08:42:22.310762Z 0 [System] [MY-015017] [Server] MySQL Server Initialization - start.
2025-03-14T08:42:22.312113Z 0 [Note] [MY-010096] [Server] Ignoring --secure-file-priv value as server is running with --initialize(-insecure).
2025-03-14T08:42:22.312126Z 0 [Note] [MY-013932] [Server] BuildID[sha1]=bcc26062017cfae7f7729d2ba4924e103b5ad9d1
2025-03-14T08:42:22.312129Z 0 [Note] [MY-010949] [Server] Basedir set to /opt/bitnami/mysql/.
2025-03-14T08:42:22.312138Z 0 [System] [MY-013169] [Server] /opt/bitnami/mysql/bin/mysqld (mysqld 8.4.4) initializing of server in progress as process 40
2025-03-14T08:42:22.323310Z 0 [Note] [MY-010458] [Server] --initialize specified on an existing data directory.
2025-03-14T08:42:22.397665Z 0 [Note] [MY-010938] [Server] Generating a new UUID: 3f4156be-00b0-11f0-a881-aa4d378db943.
2025-03-14T08:42:22.414227Z 0 [Note] [MY-012366] [InnoDB] Using Linux native AIO
2025-03-14T08:42:22.449238Z 0 [Note] [MY-015140] [InnoDB] Using innodb_flush_method=O_DIRECT
2025-03-14T08:42:22.449346Z 0 [Note] [MY-010747] [Server] Plugin 'FEDERATED' is disabled.
2025-03-14T08:42:22.449410Z 0 [Note] [MY-010747] [Server] Plugin 'ndbcluster' is disabled.
2025-03-14T08:42:22.449425Z 0 [Note] [MY-010747] [Server] Plugin 'ndbinfo' is disabled.
2025-03-14T08:42:22.449430Z 0 [Note] [MY-010747] [Server] Plugin 'ndb_transid_mysql_connection_map' is disabled.
2025-03-14T08:42:22.449456Z 0 [Note] [MY-010747] [Server] Plugin 'mysqlx' is disabled.
2025-03-14T08:42:22.449471Z 0 [Note] [MY-010747] [Server] Plugin 'mysql_native_password' is disabled.
2025-03-14T08:42:22.450356Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2025-03-14T08:42:22.450406Z 1 [Note] [MY-013546] [InnoDB] Atomic write enabled
2025-03-14T08:42:22.452812Z 1 [Note] [MY-012274] [InnoDB] The first innodb_system data file 'ibdata1' did not exist. A new tablespace will be created!
2025-03-14T08:42:22.452848Z 1 [Note] [MY-012932] [InnoDB] PUNCH HOLE support available
2025-03-14T08:42:22.452857Z 1 [Note] [MY-012944] [InnoDB] Uses event mutexes
2025-03-14T08:42:22.452862Z 1 [Note] [MY-012945] [InnoDB] GCC builtin __atomic_thread_fence() is used for memory barrier
2025-03-14T08:42:22.452872Z 1 [Note] [MY-012948] [InnoDB] Compressed tables use zlib 1.3.1
2025-03-14T08:42:22.454117Z 1 [Note] [MY-012951] [InnoDB] Using hardware accelerated crc32 and polynomial multiplication.
2025-03-14T08:42:22.456959Z 1 [Note] [MY-012203] [InnoDB] Directories to scan './'
2025-03-14T08:42:22.459176Z 1 [Note] [MY-012204] [InnoDB] Scanning './'
2025-03-14T08:42:22.469311Z 1 [Note] [MY-012208] [InnoDB] Completed space ID check of 0 files.
2025-03-14T08:42:22.513533Z 1 [Note] [MY-012955] [InnoDB] Initializing buffer pool, total size = 128.000000M, instances = 1, chunk size =128.000000M
2025-03-14T08:42:22.519089Z 1 [Note] [MY-012957] [InnoDB] Completed initialization of buffer pool
2025-03-14T08:42:22.521563Z 0 [Note] [MY-011952] [InnoDB] If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2025-03-14T08:42:22.527121Z 1 [Note] [MY-012265] [InnoDB] Setting file './ibdata1' size to 12 MB. Physically writing the file full; Please wait ...
2025-03-14T08:42:22.527164Z 1 [Warning] [MY-012638] [InnoDB] Retry attempts for writing partial data failed.
2025-03-14T08:42:22.527180Z 1 [ERROR] [MY-012639] [InnoDB] Write to file ./ibdata1 failed at offset 0, 1048576 bytes should have been written, only 0 were written. Operating system error number 22. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quota exceeded.
2025-03-14T08:42:22.527190Z 1 [ERROR] [MY-012640] [InnoDB] Error number 22 means 'Invalid argument'
2025-03-14T08:42:22.527198Z 1 [Note] [MY-012641] [InnoDB] Refer to your operating system documentation for operating system error code information.
2025-03-14T08:42:22.527203Z 1 [ERROR] [MY-012267] [InnoDB] Could not set the file size of './ibdata1'. Probably out of disk space
2025-03-14T08:42:22.527209Z 1 [ERROR] [MY-012929] [InnoDB] InnoDB Database creation was aborted with error Generic error. You may need to delete the ibdata1 file before trying to start up again.
2025-03-14T08:42:23.026332Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2025-03-14T08:42:23.026366Z 0 [ERROR] [MY-013236] [Server] The designated data directory /bitnami/mysql/data/ is unusable. You can remove all files that the server added to it.
2025-03-14T08:42:23.026375Z 0 [ERROR] [MY-010119] [Server] Aborting
2025-03-14T08:42:23.026428Z 0 [Note] [MY-010120] [Server] Binlog end
2025-03-14T08:42:23.027017Z 0 [Note] [MY-015021] [Server] MySQL Server: Components Shutdown - start.
2025-03-14T08:42:23.027181Z 0 [Note] [MY-015022] [Server] MySQL Server: Components Shutdown - end (with return value = 0).
2025-03-14T08:42:23.027286Z 0 [System] [MY-015018] [Server] MySQL Server Initialization - end.
< /code>
Wenn ich zu Azure -Disk -basierten PVC wechsle, ist alles in Ordnung! Ich denke, RWX ist ein Superet von RWO. Wenn meine Meinung richtig ist, warum kann mein MySQL dann keine Azure -Dateien als Persistenzschicht verwenden? Hat jemand die Grundursache kennen?