metaplay test database-resharding [flags]

PREVIEW: This command is currently in preview and may change in the future. If you encounter problems or have feedback, please file an issue at https://github.com/metaplay/cli/issues/new.

Validate end-to-end database resharding for your project.

The test runs entirely within containers using on-disk SQLite shard files:

1. Build the game server image (unless --skip-build).
2. Populate a 4-shard database by running bots against a background server, then shut it down gracefully so the shard files are checkpointed and closed.
3. Reshard the database through a sequence of shard counts (4 -> 1 -> 2 -> 4), running the server once per step with a different --Database:NumActiveShards.
4. After each step, open each shard's SQLite file directly and assert that the tables exist only on active shards and that row counts are preserved across steps.

The 1 -> 2 step duplicates shard 0 to shard 1 first, which exercises the resharding fast-path (integer-multiple up-sharding); the other steps exercise the generic path.

Examples

# Run the full database resharding test
metaplay test database-resharding
# Run without rebuilding the server image (faster if already built)
metaplay test database-resharding --skip-build
# Keep the on-disk shard files after the run for debugging
metaplay test database-resharding --keep-db
# Populate with more bots over a longer duration
metaplay test database-resharding --bot-count=50 --bot-duration=3m

Flags

• --bot-count <int>: Number of bots to run when populating the database (default: 30)
• --bot-duration <duration>: How long to run the bots when populating the database (e.g., 1m, 2m30s) (default: 2m0s)
• --keep-db: Keep the on-disk SQLite shard directory after the run (for debugging)
• --shard-dir <string>: Host directory to store the SQLite shard files in (defaults to a temporary directory)
• --skip-build: Skip the docker image build step (faster if you already built the image)
• --timeout <duration>: Timeout for running the test (e.g., 30m, 1h). Does not apply to the image build. (default: 1h0m0s)

Inherited Flags

• --color <string>: Should the output be colored (yes/no/auto)? [env: METAPLAYCLI_COLOR] (default: auto)
• --project <string>: Path to the to project directory (where metaplay-project.yaml is located)
• --skip-version-check: Skip the check for a new CLI version being available
• --verbose: Enable verbose logging, useful for troubleshooting [env: METAPLAYCLI_VERBOSE]