-
Notifications
You must be signed in to change notification settings - Fork 197
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
Nats connection names #11144
Nats connection names #11144
Conversation
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
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.
The PR looks good to me.
Final connection names below.
We might need alternatives to the "initial" connection. Despite the unused variable / pointer, it seems something is holding the connection open, and I don't think we can close the stream naturally (I just see The rest of the connections require changes in reva, so we can skip those for the short term. Good to merge from my side. |
ae63410
to
4e42eab
Compare
|
Description
Change the connection names according to the format
hostname:pid:service:type
There are some exceptions:
initial
connection seems to come fromocis/ocis/pkg/runtime/service/service.go
Line 523 in 626d78b
TODO
according to https://github.com/cs3org/reva/blob/edge/pkg/store/store.go#L120-L138 , but they require reva changes in order to be able to change the name from ocis. We can't do anything about it for now.NATS CLI Version development
can be ignored because it comes from the command line executing the actual command.Related Issue
#9594
Motivation and Context
It provides easier identification of which services or processes are accessing nats.
How Has This Been Tested?
Manually tested on an idle environment using the "official" nats client with the command shown above
Screenshots (if appropriate):
Types of changes
Checklist:
Note: there are 2
f0895:13:_ocis:reg
connections when there should be only one. We need to check where the other one comes from.