Skip to content
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

nsqadmin: better nodes list info #197

Merged
merged 2 commits into from
May 13, 2013
Merged

Conversation

mreiferson
Copy link
Member

there was an issue where an NSQ installation was sending nsqlookupd duplicate broadcast_address data and nsqadmin wasn't very helpful in discovering this.

this change adds remote_address info to the /nodes list so that we can use that for uniqueness.

cc @devdazed @jehiah

@mreiferson
Copy link
Member Author

RFR @jehiah

@@ -7,6 +7,7 @@
<div class="row-fluid"><div class="span12">
<table class="table table-bordered">
<tr>
<th>Remote Addresses</th>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's call this "lookupd connections", and display it as a count of connections. There should then be some sort of option to display the detailed actual connection info, and a prompt in the IsAmbiguous case where the number != expected lookupd's.

@@ -12,16 +12,23 @@
<th>TCP Port</th>
<th>HTTP Port</th>
<th>Version</th>
<th>Lookupd Conns.</th>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This column should be conditional in the case where nsqadmin is running against nsqd's directly and not nsqlookupd's

@jehiah
Copy link
Member

jehiah commented May 13, 2013

LGTM aside from comments

@mreiferson
Copy link
Member Author

updated

* show the remote addresses over which the producer is connected to lookupd
jehiah added a commit that referenced this pull request May 13, 2013
@jehiah jehiah merged commit eba421f into nsqio:master May 13, 2013
arussellsaw pushed a commit to arussellsaw/nsq that referenced this pull request Mar 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants