Derek Collison

We are starting to put some more work into KV layer around tombstones and watchers. This is also on the list to evaluate.

Would it be acceptable if the sequence number and timestamp was not stable? Meaning simply internally re-put the same message?

Each message in JetStream has a sequence number and timestamp. What I was inquiring about was if it would be acceptable for those to change on a direct get like...

This situation seems to have quite a few moving pieces, some we know and some are probably not known to us. Recreating this and trying to reproduce could take several...

If extremely important on your side I could do early PT tomorrow, otherwise early PT Monday as I am traveling to customers starting mid-day tomorrow. Shoot me an email, [email protected]

Sounds like ensuring the cluster names are unique might have resolved? ok to close? We are looking at ways the system can help out when we detect this situation.

For what you are trying to do, there is a better approach by using ephemeral consumers with no acks and re-creating the consumer if you miss a message (chunk). Will...

100% agree and this has been in discussions for awhile. We will be turning our attention more towards the clients soon (we have alot!) and this as well as general...

Might make sense to create a discussion from this.

In your scenario, how would the new JWT be delivered to the client in order for the client to resend to the server?