菜单
Generic logic for DBClient connectionstress test mode: DatabaseTester.connectionStress() implementation conventions, concurrent connection creation, and connection-leak troubleshooting. Use this skill when modifying the stress model or investigating connection-count issues.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Practical guide for adding a new database or middleware engine to DBClient. Use this skill when you need to introduce a new dbType.
Cross-cutting core mechanisms of DBClient: CLI argument parsing, DBConfig, TesterFactory, TestExecutor, and the DatabaseTester interface. Use this skill when modifying generic flows or adding engine registration, validation, or dependencies.
KV / coordination engines in DBClient: Redis, RedisCluster, Redis Sentinel, Camellia-Proxy, Etcd, and Zookeeper. Use this skill when adding, debugging, or modifying such a Tester.
Message-queue engines in DBClient: Kafka, Pulsar, RabbitMQ, and RocketMQ. Use this skill when adding, debugging, or modifying such a Tester.
Relational / JDBC-protocol-compatible engines in DBClient. Covers MySQL-compatible, PostgreSQL-compatible, Oracle, SQLServer, domestic / regulated databases, and analytical databases such as StarRocks, Doris, and ClickHouse. Use this skill when adding, debugging, or modifying such a Tester.
Search / log-retrieval engines in DBClient: Elasticsearch 8.x and OpenSearch. Use this skill when adding, debugging, or modifying such a Tester.
| name | dbclient-testmode-stress |
| description | Generic logic for DBClient connectionstress test mode: DatabaseTester.connectionStress() implementation conventions, concurrent connection creation, and connection-leak troubleshooting. Use this skill when modifying the stress model or investigating connection-count issues. |
TestExecutor.executeTest()
tester.connectionStress(connectionCount, duration)
Note: connectionStress does not go through tester.connect(); each Tester creates and closes many connections itself.
String connectionStress(int connections, int duration);
connectionCount defaults to 100duration defaults to 60 secondsExecutorService to start connections tasks.connect() -> optionally run a simple command -> close().duration seconds, counting successful/failed connections and QPS.releaseConnections() to clean up.| File | Responsibility |
|---|---|
src/main/java/com/apecloud/dbtester/commons/DatabaseTester.java | connectionStress() interface |
src/main/java/com/apecloud/dbtester/commons/TestExecutor.java | Parameter dispatch |
src/main/java/com/apecloud/dbtester/commons/DatabaseConnection.java | Connection abstraction |
src/main/java/com/apecloud/dbtester/tester/RedisTester.java | Pooled-connection stress reference |
java -jar build/libs/oneclient-1.0-all.jar \
-h 127.0.0.1 -P 3306 -u root -p password \
-e mysql -t connectionstress -c 200 -s 30
| Symptom | Investigation Point |
|---|---|
| Connection count cannot reach target | Server max_connections, client file descriptors, JDBC pool config |
| Mass timeouts | Whether DBConfig.duration is long enough; whether connections are closed and exhausted |
| Redis stress anomaly | Whether JedisPool setMaxTotal() is smaller than -c |
| High memory/CPU | Whether the stress loop caches connections/results without releasing them |
connectionCount changes the stress baseline for all engines.connectionStress is usually one of the first capabilities to verify when adding a new engine.