-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Adding user jwt payload and subscriber limits #1570
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Addresses part of #1552 Signed-off-by: Matthias Hanel <mh@synadia.com>
kozlovic
requested changes
Aug 24, 2020
Signed-off-by: Matthias Hanel <mh@synadia.com>
kozlovic
approved these changes
Aug 25, 2020
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
Something went wrong here, I have a super cluster with the below configuration and all works up till the nightly build for 25th, 26th nightly build I get
|
I'll look into it.
…On Thu, Aug 27, 2020 at 5:52 AM R.I.Pienaar ***@***.***> wrote:
Something went wrong here, I have a super cluster with the below
configuration and all works up till the nightly build for 25th, 26th
nightly build I get [ERR] 172.31.0.1:45184 - cid:10 - maximum
subscriptions exceeded for more or less any action I take.
port: 4222
monitor_port: 8222
server_name: $NAME
cluster {
port: 6222
routes = [
nats-route://nc1:6222
nats-route://nc2:6222
nats-route://nc3:6222
]
}
gateway {
name: $GATEWAY
port: 7222
gateways: [
{
name: "c1"
urls: [
"nats://nc1.c1.example.net:7222"
"nats://nc2.c1.example.net:7222"
"nats://nc3.c1.example.net:7222"
]
}
{
name: "c2"
urls: [
"nats://nc1.c2.example.net:7222"
"nats://nc2.c2.example.net:7222"
"nats://nc3.c2.example.net:7222"
]
}
]
}
accounts {
one: {
users = [
{user: one, password: password}
]
}
two: {
users = [
{user: two, password: password}
]
}
system: {
users = [
{user: system, password: password}
]
}
}
system_account: system
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1570 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEXV3LEGYKF4FGWUVWPCXE3SCYUEJANCNFSM4QJ7IQTA>
.
|
This was referenced Mar 15, 2021
Closed
Closed
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses part of #1552
Signed-off-by: Matthias Hanel mh@synadia.com
While implementing this I noticed casts to int32, from int64 or int.
I intend to resolve this by altering jwtv2 to use int32 instead of int64.
Or would you increase the server side variables?