These are chat archives for getredash/redash
Rethinking how data is queried, shared and visualized. A web application that allows to easily query an existing database, share the dataset and visualize it in different ways. Oh and you can also create dashboards.
select pid, trim(user_name), starttime, substring(query,1,20) from stv_recents where status='Running';
@parkeristyping It can be what @alexdebrie described, but then I would expect to see some queries in Redshift's queue as well. In your case it might be connectivity settings between your EC2 instance and Redshift. I stumbled at this a few times. I would start with verifying your MTU setting is 1500 (see http://docs.aws.amazon.com/redshift/latest/mgmt/connecting-drop-issues.html for details) and if this doesn't help verify the keep alive settings (http://docs.aws.amazon.com/redshift/latest/mgmt/connecting-firewall-guidance.html).
But if both the cluster and Redash instance on the same VPC, it's more likely the MTU than the keep alive.
If both settings are correct, try increasing # of Re:dash workers to eliminate the case that some queries keep the queue busy.