-
Notifications
You must be signed in to change notification settings - Fork 96
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
missing or extra cluster name in server ls and --trace is not working #191
Comments
When I enable jetstream with different domains in each server I get this output (notice the Missing line)
|
hm, so this is must be the result of deteting the amount of connected servers via the new statz addition, can you show statsz output on these machines? |
Being able to specify a receive count would be nice.
btw --trace does not work on ping either
|
So is active servers wrong here? If it is we need to know why and fix that. Else I can’t rely on that number at all. trace tend to be mainly added where APIs are accessed so many server req ones won’t have it. You can specify the expected servers generally as last, optional, argument. |
Ah so this must be because cluster name is not set in the hub? That should not be possible because jetstream requires it. Though your req results shows JS off while list shows JS on, are these the same servers and same settings producing both? |
It's not set in the hub. But it's also not set in the leaf. |
then this is working as expected, your non cluster named environment is not a cluster, why would it be reported as a cluster? |
why does the non clustered leaf report as clustered then? |
Statz for that leaf has |
I literally did not configure that. see above |
Servers are full of magical magic things doing magical setting changes for you. Somethings doing it :) I know in some cases we auto generate cluster names but I would imagine its not going to be auto generated as Regardless, this is the cause and I can only do what statz tells me alas |
oh man magic is fine, inconsistency is not. but yeah, wrong place for this |
config used:
server.conf
leaf.conf
accounts.conf
nats cli command with either an extra cluster name or a missing one. (output is the same no matter which server nats is pointed at)
In addition
--trace
does not seem to workThe text was updated successfully, but these errors were encountered: