S3 problem alarming remove/create rate richdocuments/remoteData/discovery and capabilities

Abierto
#289 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
aws, php
Área
backend, cloud

Línea de trabajo

Start by tracing where richdocuments/remoteData/discovery and capabilities are removed and recreated, then check how those operations interact with S3 storage. The report says this began after upgrading to 29.0.7 and proposes overwriting the files instead. Done means the files are no longer repeatedly removed and recreated; the issue does not identify a test or code entry point.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

This seems to have started when I updated to 29.0.7 (from 28) a week ago.

I have some 100,000 files in NextCloud and the fileID was at something like 350,000 in oc_file_cache (first installation some 5 years ago)

Now in a week time (without adding a serious amount of files) the fileID is at 411,500+! That means that those two files are removed and placed again about 6 times a minute!

I have a script that checks for orphaned files in my S3 storage, there were hundreds of files with the exact same sizes of discovery and capabilities that were orphaned.. It looks like these two files are removed and created at an alarming rate, which seems to cripple the S3 storage structure..

The problem would probably be solved when the file is overwritten, instead of being removed and created again?

Lenguaje dominante
PHP
Estrellas
156
Forks
37
Merge medio
23 h 51 min
PR fusionados (30 d)
2

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CollaboraOnline/richdocumentscode

Todos los issues de CollaboraOnline/richdocumentscode

Issues similares

Más issues de PHP

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.