-
Notifications
You must be signed in to change notification settings - Fork 823
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
Counters: Update Default Capacity #3594
Conversation
Build Failed 😱 Build Id: 1672ec84-b184-498d-ac94-fd4f38d9f773 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Build Failed 😱 Build Id: e0f268de-d427-435c-864b-97fe61afb59c To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Try running |
shall I revert the change in |
Build Succeeded 👏 Build Id: 90168406-8321-4437-bb58-206c3dfaa297 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
I have tested with Counters default capacity with Is 0 correct for the Counters default capacity? The Counters info are missing in the status with 9223372036854775807 Counters are present with 0 |
The TL;DR is currently our max capacity per game server = max(int64) / replicas. The fleet aggregates the count and capacity of all the game servers counters in the fleet. So if game server counter capacity = max(int64) and there are 3 replicas in the fleet, then the fleet aggregate counter capacity = 3 * max(int64) which errors. When I put in max(int64) / 3 as the max capacity for a game server, then the fleet and game servers started up just fine. We'll need to change the code, and documentation, so that if the aggregate capacity or count for the fleet goes above max(int64), then the aggregate would be max(int64), so that we don't get an error on aggregation. We should probably do this as a separate PR before updating the defaults. |
Opened #3604 to address the aggregating past int64 issue. |
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.
This link shows the example using |
@markmandel, @zmerlynn, and @igooch, have we decided on updating the default capacity for the Counters or keeping it as is? |
We can't have this default to max(int64) because of the issue with jsonpatch being lossy. So we'll need some other arbitrary value for default. |
Closing this PR and focusing on the documentation updates in PR #3637 |
What type of PR is this?
/kind bug
What this PR does / Why we need it:
Which issue(s) this PR fixes:
Closes #3579
Special notes for your reviewer: