SQL Lab uses the browser's "local storage" (similar to cookies, limited to 1MB I think), you can go and delete that from your browser the same way you delete cookies. SQL Lab should be responsive again.
Seems like 10k rows shouldn't be an issue but you may want to tweak your `superser_config.py` settings to limit all queries to say 1k rows to prevent this. Max On Thu, Jun 7, 2018 at 11:02 AM Barry DeZonia <[email protected]> wrote: > Hello, > > I have been working on deploying Superset to a VirtualBox virtual machine > running Ubuntu. The setup directions are easy to follow and I have a > running Superset instance setup in less than a couple hours. > > I have defined a database connection to an external MySQL database. I am > able to define queries and everything seems to work. However I find that I > can permanently cripple the system with a simple query. > > My database has a table that has 10,000 rows where each row might be 1024 > bytes. My vm has 4 gig of ram and 25 gig of disk space. There is nothing on > it other than stock ubuntu and Superset. I've tried Superset versions 24.0 > and 25.x from yesterday. > > If I do select * from the_table; in SQL Lab the app says the query is > calculating. It never completes. And the VM becomes unresponsive. I have to > power off the VM from VIrtualBox to get anywhere. > > If I startup the VM again it runs and I can launch Superset again. I can > visit any of the menus except SQL Lab. If I go into SQL Lab again the > system locks ups showing that a query is running (when I haven't launched > any this time) and my VM is stuck again. It's like SuperSet has persisted > the fact that it is in the middle of a query and never clears this state. > And something it does in response ties up all resources. > > I'm not sure if I should open a github issue or not. What system > particulars would be helpful for a github issue if I made one. Does anyone > have an opinion? Thanks. >
