* fix(mito): bound retained scan memory
Compact unused tag dictionary values before merge retention and avoid splitting
a single scan source into redundant batches. Include regression coverage.
Signed-off-by: jeremyhi <fengjiachun@gmail.com>
* perf(snapshot): bound writes and reduce logical export overhead
Bound metadata writes to 8 MiB and abort failed writers. Preserve compatible
string dictionaries, bound conversion work, combine Parquet row groups and
filter single-table exports before routing. Include resource-boundary and
packed-restore regression coverage.
Signed-off-by: jeremyhi <fengjiachun@gmail.com>
* docs: clarify metric snapshot acceptance criteria
Specify populated scale fixtures, controlled S3 request delay, native macOS
validation, paging exclusions and alternating comparison rounds.
Signed-off-by: jeremyhi <fengjiachun@gmail.com>
* fix(mito): split batches only for merged readers
Signed-off-by: jeremyhi <fengjiachun@gmail.com>
* test(snapshot): cover supported types in both layouts
Signed-off-by: jeremyhi <fengjiachun@gmail.com>
* docs: consolidate metric snapshot experiment conclusions
Signed-off-by: jeremyhi <fengjiachun@gmail.com>
* fix(mito): honor series statistics when splitting L0 scans
Apply the existing series-density heuristic to L0 files with known statistics and include them in the batch-size estimate. Preserve the fallback for older files without statistics.
Cover short-series overlapping L0 files with an ordered latest-value regression.
Signed-off-by: jeremyhi <fengjiachun@gmail.com>
* docs(mito): explain memory risk of splitting short L0 series
Signed-off-by: jeremyhi <fengjiachun@gmail.com>
* refactor: address snapshot export review feedback
Signed-off-by: jeremyhi <fengjiachun@gmail.com>
* fix(cli): accept source errors in lazy snapshot contexts
Signed-off-by: jeremyhi <fengjiachun@gmail.com>
---------
Signed-off-by: jeremyhi <fengjiachun@gmail.com>
(cherry picked from commit 18726c7602)
Signed-off-by: WenyXu <wenymedia@gmail.com>
Setup tests for multiple storage backend
To run the integration test, please copy .env.example to .env in the project root folder and change the values on need.
Take s3 for example. You need to set your S3 bucket, access key id and secret key:
# Settings for s3 test
GT_S3_BUCKET=S3 bucket
GT_S3_REGION=S3 region
GT_S3_ACCESS_KEY_ID=S3 access key id
GT_S3_ACCESS_KEY=S3 secret access key
Run
Execute the following command in the project root folder:
cargo test integration
Test s3 storage:
cargo test s3
Test oss storage:
cargo test oss
Test azblob storage:
cargo test azblob
Setup tests with Kafka wal
To run the integration test, please copy .env.example to .env in the project root folder and change the values on need.
GT_KAFKA_ENDPOINTS = localhost:9092
Setup kafka standalone
cd tests-integration/fixtures
docker compose -f docker-compose.yml up kafka
Setup tests with etcd TLS
This guide explains how to set up and test TLS-enabled etcd connections in GreptimeDB integration tests.
Quick Start
TLS certificates are already at tests-integration/fixtures/etcd-tls-certs/.
-
Start TLS-enabled etcd:
cd tests-integration/fixtures docker compose up etcd-tls -d -
Start all services (including etcd-tls):
cd tests-integration/fixtures docker compose up -d --wait
Certificate Details
The checked-in certificates include:
ca.crt- Certificate Authority certificateserver.crt/server-key.pem- Server certificate for etcd-tls serviceclient.crt/client-key.pem- Client certificate for connecting to etcd-tls
The server certificate includes SANs for localhost, etcd-tls, 127.0.0.1, and ::1.
Regenerating Certificates (Optional)
If you need to regenerate the etcd certificates:
# Regenerate certificates (overwrites existing ones)
./scripts/generate-etcd-tls-certs.sh
# Or generate in custom location
./scripts/generate-etcd-tls-certs.sh /path/to/cert/directory
If you need to regenerate the mysql and postgres certificates:
# Regenerate certificates (overwrites existing ones)
./scripts/generate_certs.sh
# Or generate in custom location
./scripts/generate_certs.sh /path/to/cert/directory
Note: The checked-in certificates are for testing purposes only and should never be used in production.