Fix logs in oai-backend and cassandra-oai

[eloiferrer]

Issue description:
It looks like the oai-backend service is currently saving almost 200 GB of logs in a backend-logs volume:

portal-compose/docker-compose-extra.yml

Line 138 in 78c0ca6

- backend-logs:/usr/local/tomcat/logs

Also cassandra-oai has a volume named cassandra-data

portal-compose/docker-compose-extra.yml

Line 64 in 78c0ca6

- cassandra-data:/var/lib/cassandra/

with more than 30 GB. I am not sure if these are also just logs.

Could someone check if this is necessary and change the configuration if it is not?

For context, these two volumes were taking >50GB and >60GB in staging and causing space-related problems.

TODOS:

• decrease log level of tomcat once development of oai-importer has been completed.

[physikerwelt]

The configuration looks good to me. 30GB of data seems okay, and 200GB of log storage is not unexpected overall. Once the development is done we can decrease the log-level.

[eloiferrer]

I might be wrong, but I thought the development for this was taking place in staging. These logs currently take half the size of our database, if they are not being actively used it would be helpful if we can deactivate them in production @physikerwelt @Mazztok45

[Mazztok45]

I didn’t deactivate the logs, but removed them since they weren’t crucial to our current work. I recognize this isn’t a sustainable long-term approach. As a future step, many .txt logs could be stored in Parquet or Arrow formats to compress and secure them, reducing disk usage.