Gnanesh
> The RG.GETRESULTS is a local operation which means that you will get results of the current shard you are connected to (this is why only shard 3 returns the...
@MeirShpilraien > I think that the other approach you suggested is not good because the client might have disconnected by then and you have no way to know which shard...
Hey @MeirShpilraien, As I said earlier, if we run the execution on one cluster node and try to fetch the results in other cluster node, we get empty results, right?...
Also @MeirShpilraien, I have used the above technique to implement it in RedisInsight v1.5 > Until then you can use RedisGears itself to collect the results, something like this should...
@w3blogfr We are working on a possible solution.
Hey @gouyou Checkout the Proxy section in the documentation: https://docs.redis.com/latest/ri/using-redisinsight/proxy/
@w3blogfr Support has been added. Please confirm whether it works for you then we can close this issue.
@HowellYan @barrychapman @Tobikoehler89 @jianzi0307 Wouldn't it be possible to open a tunnel outside Redisinsight and use the connections inside Redisinsight? This would simply work, right https://serverfault.com/a/445172
Hey @arezvani, Are you running RedisInsight behind a proxy? Can you check what error is it exactly from the network console tab. See if fixes your solution: https://github.com/RedisInsight/RedisInsight/issues/879#issuecomment-1191790107
Hey, This has been fixed in `1.13.0`. Please check - https://docs.redis.com/latest/ri/using-redisinsight/proxy/#trusted-origins. Closing this issue.