Clojurians Log v2

Morning folks 👋 You might have spotted that the 2.2 release is taking a while - today I can share some exciting news about what we've been up to. 2.2 more generally has already got a non-trivial change to the underlying XT implementation details, in order to support the PG and Kafka external sources (CDC import) - XT now has a single node resolving all the transactions for a given topic and the other nodes reading the resolutions (rather than all nodes resolving all txs like it's been for the entirety of XT's history). In rc0 we implemented this using Kafka's transactional producers, but quickly learned (through a design partner - thanks!) that this isn't always available, so in rc1 we removed that dependency. A quicker fix than we'd have liked for a relatively core part of the system, and I just felt uneasy about supporting that in production long term, so rather than releasing rc1 as a stable we've now fixed it "properly". tl;dr XT now does its own leadership election - it no longer relies on Kafka electing our leaders for us - which is the first step towards removing XT's (pretty much) mandatory dependency on Kafka for HA production deploys 🚀 I'll write an article shortly with more details, and we'll put out a pre-release with it in for eager folks to kick the tyres - for now, the ultra-keen can read the https://github.com/xtdb/xtdb/issues/5917 / https://github.com/xtdb/xtdb/pull/5927, and try out 2.2.0-20260917.070748-1 (Maven) or nightly-20260916 (Docker). Let us know what you think, or any questions, in the thread 🧵 (and of course I'll happily nerd out about it with anyone who'll listen 😄)

Evening 👋 As promised, a new release containing the above leadership election changes 🚀 Also, a https://xtdb.com/blog/leadership-election explaining how it all works, for those interested in what happens under the hood 🛠️ As always, let us know what you think, any questions, or any trouble migrating - it should be a rolling release from 2.2.0-rc1 or 2.1.0. Cheers!