MariaDB binay logs growing more than 1GB per hour after upgrading to Build 240420-ef5f14bc4 about photoprism

[alexislefebvre]

You can format the error log by adding ``` before and after the text.

And/or hide the long logs by using a section: https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections

[lastzero]

@cvinhaes see https://mariadb.com/kb/en/using-and-maintaining-the-binary-log/ for how to limit the binary log size

Reading your issue description, it is not entirely clear if you use the default MariaDB image and configuration we provide with our Docker Compose example file(s) or if you run a custom MariaDB server?

[cvinhaes]

Thank you for your reply. I run my own setup of MariaBD, the compose file is provided herein.

Now, my point is that the exact same configuration for the DB was not generating such amount of logs when using the Nov-28th version of photoprism. The binary log should not be the problem because it's been in used with this same DB configuration for quite some time and the default 30 days rotation was more than enough to contain it until upgrading Photoprism few days ago.

From the logs, it seems to me that some faces-related operation is in loop or is generating way more transactions than the previous version of Photoprism. The only change to the environment was the upgrade of Photoprism from Nov-28th to Apr-20th , which was done by redeploying the container with the new image. BTW, I have upgraded Photoprism many other times by following this exact same process with no issues until now.

Would you say that there is a way to understand what Photoprism is doing with faces and if there's a backlog to be processed?

Compose file for the database...

  db:
    image: mariadb
    restart: "unless-stopped"
    command: --transaction-isolation=READ-COMMITTED --log-bin=mysqld-bin --binlog-format=ROW --innodb-buffer-pool-size=512M --log_error=/var/lib/mysql/log/mysql_error.log
 --general_log_file=/var/lib/mysql/log/mysql.log --general_log=0
    volumes:
      - ./maria-db/data:/var/lib/mysql:rw
      - /srv/dev-disk-by-uuid-dd78971a-d609-4028-8a64-b971e31b2d29/_Backups/mariadb:/maria_backup:rw
      - ./maria-db/scripts:/maria_backup/scripts:rw
    environment:
      - TZ=America/Sao_Paulo
      - MYSQL_ROOT_PASSWORD=*************
      - MYSQL_PASSWORD=***********
      - MYSQL_DATABASE=photoprism
      - MYSQL_USER=photoprism
      - MYSQL_HOST=db:3306
    networks:
      - backend

[lastzero]

I'm not aware of any faces related changes in our latest release. It could simply be that some data changed, like you assigned different names for the same face. Might be a typo? We already have an issue for improving the face recognition in general, see our public roadmap.