New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Record the stream and consumer info timestamps #4133
Conversation
This records the server time when info for streams and consumers are created so that tools such as the nats cli can calculate time deltas for last ack, last delivered and so forth in the context of the server clock. This will help aleviate problems with client devices experiencing clock jitter that can show up in user interfaces as negative seconds since last ack etc Signed-off-by: R.I.Pienaar <rip@devco.net>
8dd7474
to
fb1d86d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - Should we consider that when this is used elsewhere it is called Now() in the struct?
Line 2684 in 91607d8
|
To me, |
All monitor things using |
I am not hard set on either one, just brought it up to gather thoughts and opinions. I think since we are putting it in Stream and Consumer info should match the precedent set in JetStream to date, which sounds like what we already have in this PR. |
This records the server time when info for streams and consumers are created so that tools such as the nats cli can calculate time deltas for last ack, last delivered and so forth in the context of the server clock.
This will help aleviate problems with client devices experiencing clock jitter that can show up in user interfaces as negative seconds since last ack etc