I’ll try to peruse the logs later, if I can find some jdbc connection related problems… but I would expect pull to fail if it can’t get the doc

not seeing any exception from xtdb

Ah, this sounds like https://github.com/xtdb/xtdb/issues/1897 - we have broadly addressed these document store failure modes on master already now (so I think the issue can be closed, but I'll double check tomorrow) and the next release will happen in a few days. In the meantime you could try building master if you are particularly concerned about the potential impact for your app

ok, good to know… this was a little scary, but I think I could add some pull&verify check to health endpoint in the mean time

we are using a “serverless” rds postgres on aws, which will scale down when not in use, so this morning nothing was being pulled… but there was no log entry anywhere about any sql query timeout or failure

Can I do some check in user space, that validates doc store connection and doesn’t use the doc cache

@U11SJ6Q0K can I ask what XTDB version you were running when you observed this?

1.23.1