You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2018/06/07 21:27:30 UTC

[GitHub] bdezonia opened a new issue #5163: It is possible to get locked out of SQL Lab

bdezonia opened a new issue #5163: It is possible to get locked out of SQL Lab
URL: https://github.com/apache/incubator-superset/issues/5163
 
 
   Make sure these boxes are checked before submitting your issue - thank you!
   
   - [ X] I have checked the superset logs for python stacktraces and included it here as text if any
   - [ X] I have reproduced the issue with at least the latest released version of superset
   - [ X] I have checked the issue tracker for the same issue and I haven't found one similar
   
   
   ### Superset version
   0.25.6
   
   ### Expected results
   
   A query in SQL lab should return results or complain that it does not have enough memory or localstorage to complete request.
   
   ### Actual results
   
   VM that is running Superset becomes totally unresponsive. After restarting VM user is locked out of using SQL Lab anymore.
   
   ### Steps to reproduce
   
   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.6 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.
   
   Note I cannot find superset.log anywhere.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org