After upgrading to latest Singlestore Studio, I’m unable to view tables in the studio and am also unable to upgrade db to 7.6.8 from 7.6.6
Current version running on Ubuntu 20.04.3 LTS
SingleStore DB Version 7.6.6
Singlestoredb-studio version 4.0.2
SinglestoreStudio loads and I can navigate through Hosts & Nodes, into Databases and to the Schema view. When selecting a table to view I now get “An error occurred: The table or view you are looking for does not exist.” I can access and view procedures, and connect remotely to the master via DBeaver - where data is returned from queries and procedures.
The following commands all appear to be returning as expected -
SHOW LEAVES;
SHOW AGGREGATORS;
SHOW CLUSTER STATUS;
Running ‘sdb-deploy upgrade --pre-check-only’ returns -
“refusing to upgrade a cluster with no master aggregator, make sure that a master aggregator exists in this cluster and it show up in ‘sdb-admin list-nodes’ before continuing”
I’m logging into Studio (and accessing remotely) with the main root account, a separate application with it’s own account is also still able to read the tables.
Could you try to run sdb-toolbox-config list-hosts and see whether all your hosts are registered in the Toolbox? If not you probably need to re-register them with the sdb-toolbox-config register-host command.
That’s allowed my to re-register the hosts on the master aggregator, and the sdb-deploy upgrade --precheck-only is working again. I was actually able to update the cluster to 7.6.8 on the child aggregator earlier.
I’m still getting an error in Studio when I try to view a table on the master aggregator (on Studio 4.0.2). On the child aggregator (not upgraded, on Studio 4.0.1) I can access the tables without issues. This is accessing with root, so I’m not sure if some permissions have been dropped somewhere too.
Unfortunately it seems that a bug was introduced in the databases page and it is causing the "An error occurred: The table or view you are looking for does not exist.”. We’re tracking this and will be addressing it ASAP. For now, consider using information_schema tables and SHOW TABLES and SHOW CREATE TABLE to get information about the tables.