Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tsbs_load load timescaledb error #248

Open
ruoshui9527 opened this issue Mar 12, 2024 · 3 comments
Open

tsbs_load load timescaledb error #248

ruoshui9527 opened this issue Mar 12, 2024 · 3 comments

Comments

@ruoshui9527
Copy link

ruoshui9527 commented Mar 12, 2024

tsbs_generate_data --use-case="iot" --seed=123 --scale=4000
--timestamp-start="2024-03-10T00:00:00Z"
--timestamp-end="2024-03-12T00:00:00Z"
--log-interval="10s" --format="timescaledb"
| gzip > /tmp/timescaledb-data.gz

use tsbs_load:

./tsbs_load config --target=timescaledb --data-source=FILE

vi After modifying the relevant content, execute
./tsbs_load load timescaledb --config=./config.yaml
Using config file: ./config.yaml
2024/03/12 11:50:22 input header in wrong format. got '%!s(uint8=31)', expected 'tags'

##use tsbs_load_timescaledb:
cat /tmp/timescaledb-data.gz | gunzip | ./tsbs_load_timescaledb \

--postgres="sslmode=disable" --host="192.168.1.10" --port=5433 --pass="111111"
--user="postgres" --admin-db-name=tsbs --workers=8
--in-table-partition-tag=true --chunk-time=8h --write-profile=
--field-index-count=1 --do-create-db=true --force-text-format=false
--do-abort-on-exist=false --create-metrics-table=true
could not execute sql: SELECT create_hypertable('readings'::regclass, 'time'::name, replication_factor => NULL, chunk_time_interval => 28800000000, create_defe_hypertable(regclass, name, replication_factor => unknown, chunk_time_interval => bigint, create_default_indexes => boolean) does not exist (SQLSTATE 42883)

goroutine 1 [running]:
github.com/timescale/tsbs/pkg/targets/timescaledb.MustExec(0x8d8971?, {0xc0000e6000, 0x9b}, {0x0?, 0x4?, 0x8?})
/home/ps/tsbs-master/pkg/targets/timescaledb/creator.go:296 +0xd0
github.com/timescale/tsbs/pkg/targets/timescaledb.(*dbCreator).createTableAndIndexes(0xc00008a0f0, 0xc000128dd0, {0xc000178140, 0x8}, {0xc00016a280, 0x8, 0x8}
/home/ps/tsbs-master/pkg/targets/timescaledb/creator.go:224 +0x6ff
github.com/timescale/tsbs/pkg/targets/timescaledb.(*dbCreator).PostCreateDB(0xc00008a0f0, {0x8bc0b4?, 0x9?})
/home/ps/tsbs-master/pkg/targets/timescaledb/creator.go:105 +0x365
github.com/timescale/tsbs/load.(*CommonBenchmarkRunner).useDBCreator(0xc000122790, {0x971cf8, 0xc00008a0f0})
/home/ps/tsbs-master/load/loader.go:252 +0x215
github.com/timescale/tsbs/load.(*CommonBenchmarkRunner).preRun(0xc000122790, {0x972660, 0xc00068e000})
/home/ps/tsbs-master/load/loader.go:128 +0x72
github.com/timescale/tsbs/load.(*CommonBenchmarkRunner).RunBenchmark(0xc000122790, {0x972660, 0xc00068e000})
/home/ps/tsbs-master/load/loader.go:184 +0x37
main.main()
/home/ps/tsbs-master/cmd/tsbs_load_timescaledb/main.go:102 +0x213

@moaazassali
Copy link

I am getting the same error input header in wrong format. got '%!s(uint8=31)', expected 'tags'. Did you find a solution?

@Koheiru
Copy link

Koheiru commented Jun 6, 2024

There are two different issues described.

The first one is like a feature =) It is about that tsbs_load tool couldn't read compressed file with metrics. Error message input header in wrong format. got '%!s(uint8=31)', expected 'tags' is a marker of this issue. So, you can do one of the following:

  • use pipe as described in documentation
#> cat /tmp/timescaledb-data.gz | gunzip | ./tsbs_load_timescaledb ...
  • store and use decompressed version of the logs-file
#> cat /tmp/timescaledb-data.gz | gunzip > /tmp/timescaledb-data.txt
#> tsbs_load config --target=timescaledb --data-source=/tmp/timescaledb-data.txt
... modify config ...
#> tsbs_load load timescaledb --config=./config.yaml

The second issue is critical and there is no workaround but I've already create fix for this issue (check #255). So, you can merge my fix or just use older version of timescaledb.

@maelick
Copy link

maelick commented Aug 4, 2024

FYI I fixed the first issue in #261

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants