[UI] Database dashboard is not updated automatically
Description
Environment
Attachments
Activity
Manish Chawla January 23, 2025 at 8:35 AM
Tested with Feature build · percona/everest@1a44604
Install using helm in the default db namespace everest. Then create some databases in a browser session.
Opened another browser session.
Installed mysql in a1 namespace and created a mysql database.
View the second browser session, the dashboard is updated and the mysql database is displayed.
Installed mongodb in a2 namespace and created a mongodb database.
Opened another browser session.
View the second and third browser session, the dashboard is updated and the mongodb database is displayed.
The issue is fixed, so transitioning it to Ready for Merge.
Diana Birsan January 22, 2025 at 1:02 PM
new FB:
Manish Chawla January 22, 2025 at 12:55 PM
Hi , Please pull the latest main and create a new feature build as changes in the build process has removed some scripts from the everest repo. Hence the old feature builds don’t work now.
Please refer to this slack message for more details:
Thanks.
Diogo Recharte December 10, 2024 at 4:44 PM
This is happening because the GET /namespaces request is only being done when the page is opened so if a new namespace is added the FE doesn’t know about it and by consequence doesn’t do any requests for the DBs in that new namespace.
The GET /namespaces request should be polled regularly.
Tested with Everest v1.4.0-rc1 version.
Install using helm in the default db namespace everest. Then create some databases in a browser session.
Then open the database dashboard in another browser session.
Install mongodb in another namespace a2 using helm.
In the first browser session, create a mongodb sharded database in the a2 namespace, the dashboard is displayed as
View the second browser session, the dashboard is not updated i.e. it does not display the new mongodb database created in the a2 namespace
This is the state after waiting for several hours. The dashboard should be updated after some time to reflect the new mongodb database. I think this was happening in the 1.3.0 release.