Add cluster-aware gateway routing and client presentation#29
Closed
VG-prog wants to merge 4 commits into
Closed
Conversation
Add the shared protobuf, generated runtime code, events, GUID helpers, auth identity helpers, and configuration contracts used by clustered gateway, registry, group, guild, matchmaking, and sidecar flows. Tests, local tooling, and broad documentation are intentionally excluded from this upstream-focused scope.
Wire service discovery, map readiness, stale-safe health and metrics observers, degraded game-server health handling, gateway-scoped cleanup, and shared GUID allocation support. Registry and health code now distinguish world-loop degraded state from process or transport death while preserving live map ownership.
Keep world-loop degraded game servers registered for ownership and existing lookups, but mark them as non-admitting so new player placement skips them. Clear the drain state on successful health recovery and fall back to healthy all-map nodes when an assigned owner is degraded.
Route gateway sessions through cluster-aware worldserver selection, native transport handoff, bounded retry/backoff, cross-service event listeners, and client-facing packet rendering for social, group, guild, guild bank, LFG, battleground, arena, mail, channel, and player-state flows.
Author
|
Closing this draft because it was opened from a stacked branch while targeting That replacement PR presents the current integration honestly as one review surface. Sorry for the review noise. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
This PR turns the gateway into the cluster presentation layer for connected clients.
The gateway now understands clustered worldserver selection, native transport handoff, session lifecycle transitions, bounded retry/backoff, and service-driven packet rendering. The goal is to keep AzerothCore authoritative for gameplay while allowing ToCloud9 to route cross-worldserver and crossrealm presentation safely.
What changed
Why this matters
Gateway is the right place to adapt distributed service state into client-visible packets. This avoids high-frequency worldserver polling and keeps most cross-server presentation outside the AzerothCore gameplay loop.
Validation
git diff --check origin/master..HEADenv GOCACHE=/tmp/tc9-go-build GOFLAGS=-buildvcs=false go build ./...env GOCACHE=/tmp/tc9-go-build GOFLAGS=-buildvcs=false make install