There is an inconsistent bug where during table creation in the end to end tests, some nodes seemingly fail to call the 'setReady()' method on the control for their portion of the table. Not sure if the nodes really have not 'set ready' or if control failed to store the data. Need to clear this up.
Note, I originally thought this was an issue with docker compose overburdening the computer, but turns out it can happen anytime. Just seems random when it does.
Suggestions to reproduce: Build out, without docker, an instance with one control and 3 nodes and manually (via curl) create tables. See how long it takes for the table to get to ready.
There is an inconsistent bug where during table creation in the end to end tests, some nodes seemingly fail to call the 'setReady()' method on the control for their portion of the table. Not sure if the nodes really have not 'set ready' or if control failed to store the data. Need to clear this up.
Note, I originally thought this was an issue with docker compose overburdening the computer, but turns out it can happen anytime. Just seems random when it does.
Suggestions to reproduce: Build out, without docker, an instance with one control and 3 nodes and manually (via curl) create tables. See how long it takes for the table to get to ready.