You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened
When load testing immudb, a 1 second test will succeed, but a 5 second test will eventually will eventually return ERRO[0001] GoError: pq: tbtree: max active snapshots limit reached and after this error immudb cannot be used until it is restarted.
What you expected to happen
I expected the tests to complete regardless of the duration.
How to reproduce it (as minimally and precisely as possible)
Install the xk6 binary for building custom versions of k6. go install go.k6.io/xk6/cmd/xk6@latest
Build a version of k6 with sql support in the current directory. xk6 build v0.52.0 --with github.com/grafana/xk6-sql
Add the demo data to a fresh copy of immudb configured with maxActiveSnapshots = 1200:
Using the k6 binary built above, run ./k6 run sqltest.js --duration 1s with the following script:
importsqlfrom'k6/x/sql';exportfunctionsetup(){}exportfunctionteardown(){}exportdefaultfunction(){// The second argument is a PostgreSQL connection string, e.g.// postgres://myuser:mypass@127.0.0.1:5432/postgres?sslmode=disableconstdb=sql.open('postgres','postgres://immudb:immudb@localhost:5432/defaultdb?sslmode=disable');letresults=sql.query(db,`SELECT * FROM orders JOIN customers ON orders.customerid = customers.id WHERE orders.productid = $1;`,1);console.log({results})for(constrowofresults){console.log(`key: ${row.key}, value: ${row.value}`);}db.close();}
Running ./k6 run sqltest.js --duration 1s will succeed.
Running ./k6 run sqltest.js --duration 5s will fail with tbtree: max active snapshots limit reached
All subsequent tests of any duration will will fail with tbtree: max active snapshots limit reached
Restart immudb.
Running ./k6 run sqltest.js --duration 1s will succeed.
Environment
# run "immu* version" and copy/paste the output here
[mike@kijimi immudb-deployment]$ immudb version
immudb 1.9DOM.2
Commit : d422d9f828c6ccfce6ce4af6c565946f764a15ca
Built by: makepkg
[mike@kijimi immudb-deployment]$ immuclient version
immuclient 1.9DOM.2
Commit : d422d9f828c6ccfce6ce4af6c565946f764a15ca
Built by: makepkg
[mike@kijimi immudb-deployment]$ immuadmin version
immuadmin 1.9DOM.2
Commit : d422d9f828c6ccfce6ce4af6c565946f764a15ca
Built by: makepkg
Additional info (any other context about the problem)
The text was updated successfully, but these errors were encountered:
What happened
When load testing immudb, a 1 second test will succeed, but a 5 second test will eventually will eventually return
ERRO[0001] GoError: pq: tbtree: max active snapshots limit reached
and after this error immudb cannot be used until it is restarted.What you expected to happen
I expected the tests to complete regardless of the duration.
How to reproduce it (as minimally and precisely as possible)
Install the xk6 binary for building custom versions of k6.
go install go.k6.io/xk6/cmd/xk6@latest
Build a version of k6 with sql support in the current directory.
xk6 build v0.52.0 --with github.com/grafana/xk6-sql
Add the demo data to a fresh copy of immudb configured with
maxActiveSnapshots = 1200
:Using the
k6
binary built above, run./k6 run sqltest.js --duration 1s
with the following script:Running
./k6 run sqltest.js --duration 1s
will succeed.Running
./k6 run sqltest.js --duration 5s
will fail withtbtree: max active snapshots limit reached
All subsequent tests of any duration will will fail with
tbtree: max active snapshots limit reached
Restart immudb.
Running
./k6 run sqltest.js --duration 1s
will succeed.Environment
Additional info (any other context about the problem)
The text was updated successfully, but these errors were encountered: