These are chat archives for getredash/redash

5th
Sep 2015
DBY
@Dnile
Sep 05 2015 00:01
why not use a vm?
with vagrant perhaps
Sri Kidambi
@kidambisrinivas
Sep 05 2015 00:04
oh this whole setup is hosted in aws and we've docker based deployments setup
DBY
@Dnile
Sep 05 2015 00:11
i see
Sri Kidambi
@kidambisrinivas
Sep 05 2015 00:11
Is there any way to debug why this is happening: "Redash responds with results of different queries while editing other queries"
DBY
@Dnile
Sep 05 2015 00:12
a good question, we can wait for an arik is online, as this got me interested too
Arik Fraimovich
@arikfr
Sep 05 2015 06:02

@kidambisrinivas @Dnile re. Docker: indeed we should split it into several images, and containers (the same image can be used for re:dash processes, but they should be separate containers). The best reference at the moment is the bootstrap.sh script, but I can provide additional details later today or tomorrow (Sunday).

If you only need this for debugging, you should consider using the Vagrant VM (http://docs.redash.io/en/latest/dev/vagrant.html), it should be much less effort. But I'll be happy if you get to implement the docker images :-)

Re. the issue you have with queries getting wrong results, I'll be happy to help w/ debugging and fixing this. Can you provide more details on what the scenario that makes this happen (if there is one)?

Sri Kidambi
@kidambisrinivas
Sep 05 2015 21:30

@arikfr : Thanks for the quick reply explaining best practices/ideal setup in docker world. Yes, It'll be gr8 if you could help me debug this. Here are the details:

I setup a set of 10 queries in redash. Then we had to migrate the redash to a higher aws instance. We moved the data folder from the old machine to the new one. The queries started returning results of other queries from the list of queries I'd written. After this, I deleted all the data of redash (redis and postgres), and re-created new queries. Even then I keep getting out-of-order responses. Is it due to some nginx caching (as the query numbers had changed when created new queries, but they get intercepted at nginx layer to return results of old query at tht num)?