asyncpg INSERT error
#12269
-
Has anyone seen this before When looking at the admin console for the table it's in good health with all shards available and nothing to indicate that it's "read-only" Any ideas on how to debug this @proddata ? |
Beta Was this translation helpful? Give feedback.
Answered by
robd003
Mar 29, 2022
Replies: 1 comment 2 replies
-
Turns out this was a side-effect when we did performance testing on this cluster and hit the high water mark on the disk. I fixed it by running |
Beta Was this translation helpful? Give feedback.
2 replies
Answer selected by
proddata
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Turns out this was a side-effect when we did performance testing on this cluster and hit the high water mark on the disk.
I fixed it by running
ALTER TABLE tablename SET ("blocks.read_only_allow_delete" = FALSE);
on every single table which was annoying...