mirror of
https://github.com/GreptimeTeam/greptimedb.git
synced 2026-10-03 18:45:35 +00:00
dennis zhuang
d59725b04a
* test(sqlness): run environments concurrently with external backends The runner forced both environment and instance parallelism to 1 whenever etcd/PG/MySQL or an external Kafka was set up, so the standalone and distributed environments ran one after the other. Only distributed uses the kv backend, and the two environments use different Kafka topic prefixes, so they can run at the same time. Keep one instance per environment, since instances would share the metadata table and Kafka topics. Runs with a runner-managed Kafka, an external server, a test filter, or `-j 1` stay fully serial. Signed-off-by: Dennis Zhuang <killme2008@gmail.com> * test(sqlness): drop redundant restarts and sleeps - flow_rebuild: drop the R2 block, which repeats R1 from the same state, and the restart in R5, whose result R1 already asserts. - flow_advance_ttl, flow_view, ttl_instant: drop sleeps that no assertion depends on. - flow_basic, flow_null, flow_call_df_func: drop the bytes_log section (covered by flow_insert), a duplicate state_size query, an unchecked insert, and flushes that run with no new data. - alter_table_options, skip_wal: share restarts between independent tables. - session_skip_wal, copy_skip_wal: check every case after a single restart. Tables copied or inserted with skip_wal = true first get a WAL row that is truncated, so the check that truncated WAL entries are not replayed stays. - region_statistics: wait once for the statistics of all three tables. - build_index_table: fold its index_size checks into build_index_table_restart, which runs the same fixture and waits. Signed-off-by: Dennis Zhuang <killme2008@gmail.com> * test(sqlness): restore session_skip_wal and copy_skip_wal Checking every case after a single restart dropped two state transitions the original cases cover: recovering a region whose memtable only held skipped rows, and writing to the recovered region before restarting again. Restore the original cases. Signed-off-by: Dennis Zhuang <killme2008@gmail.com> * test(sqlness): restore the one-restart check in flow_auto_sink_table #5112 checked the auto-created sink before a restart and the flow and sink after it. #5987 moved the restart in front of the first SHOW and added a second one. Flow recovery only creates the sink when it is missing, so the second restart recovers from the same persisted state as the first. Restore the original before/after check with one restart. Signed-off-by: Dennis Zhuang <killme2008@gmail.com> * test(sqlness): keep one instance per environment with external store addresses Instances of the distributed environment share the etcd behind --store-addrs, so run one instance per environment when it is set, same as --setup-etcd. Signed-off-by: Dennis Zhuang <killme2008@gmail.com> * test(sqlness): restore the false-branch batch in flow_basic and assert it The kept batch (20, 22) is all above the threshold. The second batch (10, 23) is the only input that hits the false branch of the CASE and makes the flow compute again. Restore it and check the result, which the original case never did. Signed-off-by: Dennis Zhuang <killme2008@gmail.com> --------- Signed-off-by: Dennis Zhuang <killme2008@gmail.com>
74 lines
1.9 KiB
SQL
74 lines
1.9 KiB
SQL
CREATE TABLE system_metrics (
|
|
host STRING,
|
|
idc STRING,
|
|
cpu_util DOUBLE,
|
|
memory_util DOUBLE,
|
|
disk_util DOUBLE,
|
|
ts TIMESTAMP DEFAULT CURRENT_TIMESTAMP(),
|
|
PRIMARY KEY(host, idc),
|
|
TIME INDEX(ts)
|
|
) WITH (skip_wal = "true");
|
|
|
|
INSERT INTO system_metrics
|
|
VALUES
|
|
("host1", "idc_a", 11.8, 10.3, 10.3, 1667446797450),
|
|
("host2", "idc_a", 80.0, 70.3, 90.0, 1667446797450),
|
|
("host1", "idc_b", 50.0, 66.7, 40.6, 1667446797450);
|
|
|
|
CREATE TABLE alter_skip_wal (
|
|
host STRING,
|
|
val DOUBLE,
|
|
ts TIMESTAMP,
|
|
PRIMARY KEY(host),
|
|
TIME INDEX(ts)
|
|
);
|
|
|
|
INSERT INTO alter_skip_wal VALUES ('host1', 1, 1000);
|
|
|
|
ALTER TABLE alter_skip_wal SET 'skip_wal' = 'true';
|
|
|
|
SHOW CREATE TABLE alter_skip_wal;
|
|
|
|
-- This row is intentionally not written to WAL.
|
|
INSERT INTO alter_skip_wal VALUES ('host2', 2, 2000);
|
|
|
|
ALTER TABLE alter_skip_wal SET 'skip_wal' = 'false';
|
|
|
|
SHOW CREATE TABLE alter_skip_wal;
|
|
|
|
-- Repeating the transition is idempotent.
|
|
ALTER TABLE alter_skip_wal SET 'skip_wal' = 'false';
|
|
|
|
ALTER TABLE alter_skip_wal UNSET 'skip_wal';
|
|
|
|
-- This row uses the restored WAL provider.
|
|
INSERT INTO alter_skip_wal VALUES ('host3', 3, 3000);
|
|
|
|
SELECT * FROM alter_skip_wal ORDER BY ts;
|
|
|
|
-- SQLNESS ARG restart=true
|
|
SELECT * FROM system_metrics;
|
|
|
|
-- Re-enabling WAL does not retroactively write the skipped row to WAL.
|
|
SHOW CREATE TABLE alter_skip_wal;
|
|
|
|
SELECT * FROM alter_skip_wal ORDER BY ts;
|
|
|
|
DROP TABLE alter_skip_wal;
|
|
|
|
INSERT INTO system_metrics
|
|
VALUES
|
|
("host1", "idc_a", 11.8, 10.3, 10.3, 1667446797450),
|
|
("host2", "idc_a", 80.0, 70.3, 90.0, 1667446797450),
|
|
("host1", "idc_b", 50.0, 66.7, 40.6, 1667446797450);
|
|
|
|
ADMIN flush_table('system_metrics');
|
|
|
|
-- SQLNESS ARG restart=true
|
|
SELECT * FROM system_metrics;
|
|
|
|
-- A table created without a real WAL provider cannot enable WAL later.
|
|
ALTER TABLE system_metrics SET 'skip_wal' = 'false';
|
|
|
|
DROP TABLE system_metrics;
|