Open yazun opened 3 years ago
It happened only for a single dn so far, but from any coordinator.
And bouncing DB does not help.
@yazun I try to reproduce this promble, but it hasn't happend yet. I want to confirm some questions: 1、 Whether tbl_partition_1 is partition table or not? 2、Is there "corrupted statistics file" or "out of file descriptors" in datanode4's log? 3、Is it shows that stats collector process exitting when the promble occurs in datanode4's log? And if you have a simple way to reproduce the promble, please let me know. Thanks.
@yazun Have you solved the problem?Or more clues for it? Do you have a way to reproduce this problem?
Rescuing a very old thread just because I landed here in search for answers, I had a very similar issue and I got the erratic results resolved by means of issuing an ANALYZE VERBOSE my_table;
We rely on updating stats on the coordinators on a global view by comparing pg_stat_all_tables differences between datanode and coordinator. Noticing however very worrisome, erratic behaviour of the pg_stat_all_tables values. Below you can see that values returned are either ok or nulls - they query is executed in second intervals and seem randomy returning proper values or nothing. This basically breaks coordinators update (
analyze(coordinator
).Do you have any idea why that could be happening? - Seems like a caching problem of some stale pool connection maybe? How to fix it?
Thanks