Consul Key Question, Request for Documentation
Closed this issue · 1 comments
bradymwilliams commented
So I got my db in a crazy state by accidentally running a query against it outside of litefs -- meaning its internal transaction hashes got out of sync.
After trying all kinds of things I just deleted all machines/volumes -- that didnt work until i slightly altered the lease.consul.key
value in litefs.yml
in response to:
connect,level=INFO msg="cannot connect, \"consul\" lease already initialized with different ID: ID_HASH_HERE"
Luckily this all took place on my staging environment, now that resolved I need to know if i deploy this consul key change to prod if something bad will happen haha.
I am using the same repo for both apps, with my key being differentiated with ${FLY_APP_NAME}
bradymwilliams commented
I did and I could