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
Restore forwarding may be problematic #1088
Comments
I'm frequently getting into a state when loading into a follower does not restore the data. I'm still not 100% sure how to get to that state, but these are the commands I run to reproduce the issue with the current state: 1- Create a table with some data: curl -XPOST '10.96.1.223:4001/db/execute?pretty' -H "Content-Type: application/json" -d '[
"CREATE TABLE foo (id INTEGER NOT NULL PRIMARY KEY, name TEXT, age INTEGER)",
"INSERT INTO foo(name, age) VALUES(\"fiona\", 20)"
]' 2- Make sure the data is there:
3- Take a backup:
4- Delete the data:
5- Make sure data is not here:
6- Restore the data directly into a follower or through the load balancer (and making sure the
7- Check that the data is restored:
In my case, the data is not restored. I'll attach the output of |
|
|
|
|
Fixed by #1089 |
Issue was the load commands between nodes were limited at 2^16 bits in size. This was too small, and has been increased to 2^64 bytes in size. |
There are reports that restoring via a follower is not working correctly. I can't reproduce any issues.
Test case 1: spin up a 2-node cluster by hand and restore through the follower.
Start node 1:
Start node 2 and join it to node 1:
Restore a SQLite file into the cluster via the follower:
Query the leader:
Query the follower, using
none
consistency (so the local SQLite database is queried:Test case 2: I did something very similar on Minikube, using the following configs, and restored fine through a follower (the Load Balancer routed me to a follower).
Services:
Stateful set:
The text was updated successfully, but these errors were encountered: