Skip to content

Does scaling up restart old pods & supply a new shard count? #3

@MacDue

Description

@MacDue

Just want to clarify something in the readme you state:

Meaning: if we scale up, all existing shards will need to re-identify with Discord to present the new shard count, and update their local cache as necessary.

But in the code:

// Set the shard count environment variable - will force existing shards to restart

If they restarted with a new count anyway that'd handle the re-idenify & stuff.

Sorry not super familiar with kubernetes to tell exactly what happens here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions