xtdb 2025-06-02

Hello! I don't understand the error I'm getting. I have an xtdb instance that works normally if I have recently done an INSERT or some sort of transaction, but If I wait a day or so, and then try and make a SELECT, I get the following error:

xtdb=> SELECT * FROM people;

ERROR: snapshot-time (2025-05-29T20:47:08.009060951Z) is after the latest completed tx (#xt/tx-key {:tx-id 5623, :system-time #xt/instant "2025-05-29T16:46:07.940618166Z"})
DETAIL:  {"latest-completed-tx":{"tx-id":5623,"system-time":"2025-05-29T16:46:07.940618166Z"},"snapshot-time":"2025-05-29T20:47:08.009060951Z","category":"cognitect.anomalies\/incorrect","code":"xtdb\/unindexed-tx","message":"snapshot-time (2025-05-29T20:47:08.009060951Z) is after the latest completed tx (#xt\/tx-key {:tx-id 5623, :system-time #xt\/instant \"2025-05-29T16:46:07.940618166Z\"})"}
If I do an INSERT, then the error goes away for a while, but this isn't sustainable. Could there be a configuration issue?

fix out πŸ™‚ could try re-pulling latest? or 2.0.0-beta8.4 if you're specifying manually

It works!

πŸ™Œ 2
πŸŽ‰ 1

Thank y'all! I'm hoping to prove to my company that the ease and bitemporal features of xtdb will make our current task much much more doable.

awesome πŸ™‚ let us know if we can help!

I believe you’re running into this bug: https://github.com/xtdb/xtdb/issues/4465 This is definitely not intended!

Ah. Yep. That's definitely it.. I hope this bug is contained to just the standalone docker..

recommendation for now is to fix to beta8.2 - this issue is a prio for us to fix

πŸ‘ 1

sounds like we have a repro internally, let's see if we can get to the bottom of it πŸ™‚

πŸ’ͺ 1