nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s if you ever want to migrate tigerbeetle between clusters if it gets too big or you change replication

create an account for the purpose of closing and closing only

when you want to migrate, create a linked set of events

- transfer all balance from source to closing account (use balancing_debit)

- pending transfer, close source account

after that on the new cluster both create the account and credit it the previous cluster’s balance (read back the transfer you sent to get how much it was at that instant)

your client should always try on the old cluster, if it fails with a closed error, try on the new cluster, and retry if you get an account nonexistent error

Reply to this note

Please Login to reply.

Discussion

No replies yet.