[outline on kubernetes] Regular write error on PG Cluster setup #6686
-
Hello, we recently migrated Outline and the dependencies (postgresql and redis) to Kubernetes, and since then we observe error 500 due to issue in the Db layer. Randomly we get write errors which prevents documents creation or modification. The problem appears and disappears without being able to have a reproducer to trigger the problem by ourselves. The error is the following
The block number increase by one each time we get an error. one of the exceptions we get on outline
We modified the setup to make outline skip pgbouncer and directly connect to the primary postgresql, we still had the same issue. we can dump the postgresql data without any issue, so unlikely to be a corruption on database side. On docker we never had such issue 😓 Is someone having the same setup in order there is some tuning to do ? Best |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Turned out to be a corruption on the table Impact: We lost all the revisions since we migrated, we just have the last version of each document if I understand correctly. What could be improve in outline: That would have being great that outline provides the database query when it fails executing it. |
Beta Was this translation helpful? Give feedback.
Turned out to be a corruption on the table
revisions
since day 1 we migrated to kubernetes....id
33617
is the OID of therevisions
table in postgresql. It was possible to read the table but not to write to it. Backup (so reading all data) does not generate any error, no error eith on postgresql side. To fix we deleted all the database and restored it.Impact: We lost all the revisions since we migrated, we just have the last version of each document if I understand correctly.
What could be improve in outline: That would have being great that outline provides the database query when it fails executing it.