Hey team. We are seeing an interesting
Hey team. We are seeing an interesting behaviour were a KV entry appears to have been added 5 hours after it was originally created and then deleted. I understand that KV is an eventually consistent store... but find it unlikely that there could've been a 5 hour gap between replication.
Any tips on what debugging we can do to understand why a certain key appeared in our KV store when we didn't expect it?
I also see there is no way for us to verity that a
kb.delete call would have actually removed a real key from the store.6 Replies
Unknown User•14mo ago
Message Not Public
Sign In & Join Server To View
No. We don't set a TTL
I can write down our setup and scenario - that would be good context to be able to at least guide us where to look. But first, any chance we can jump on a huddle? Might be easier to talk.
I'll pencil down sometime to share context in this thread anyway
Unknown User•14mo ago
Message Not Public
Sign In & Join Server To View
@Hady (Atlassian) were you able to determine the issue in your setup?
Hey! I worked with Hady on this. We weren't able to find an issue in our setup, and we just had another instance of this behaviour come through last night with a 15-16 hour delay.
We have an idea of how to work around it in the meantime, but would be good to get your thoughts too – I'll DM you our emails, @Charlie B | KV, Queues, PubSub
Unknown User•14mo ago
Message Not Public
Sign In & Join Server To View