You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "shenqiong (JIRA)" <ji...@apache.org> on 2018/11/12 13:21:00 UTC
[jira] [Updated] (KYLIN-3681) kylin + nginx failed
[ https://issues.apache.org/jira/browse/KYLIN-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
shenqiong updated KYLIN-3681:
-----------------------------
Description:
Hi， I use two kylin instances with nginx to set up a query cluster, and I also config a session server with redis as the [link|https://blog.csdn.net/rlnLo2pNEfx9c/article/details/78796545] told. but there are still some query fail and hanging when queries from a page were sent to both of two instance. Because If I remove one kylin instance and left only one , query is working well.
To be further, I tried to shut down the auth of query instance by modify kylinSecurity.xml by making all access = "permitAll", but still no help. As far as I can see, there should be a easy way to shut down auth for the query instance, because the auth can be done by higher domain system .Query is just for querying data but faster and still safe.
was:
Hi， I use two kylin instances with nginx to set up a query cluster, and I also config a session server with redis as the [link|https://blog.csdn.net/rlnLo2pNEfx9c/article/details/78796545] told. but there are still some query fail and hanging when queries from a page were sent to both of two instance. Because If I remove one kylin instance and left only one , query is working well.
To be further, I tried to shut down the auth of query instance by modify kylinSecurity.xml by making all access = "permitAll", but still no use. As far as I can see, there should be a easy way to shut down auth for the query instance, because the auth can be done by higher domain system .Query is just for querying data but faster and still safe.
> kylin + nginx failed
> ---------------------
>
> Key: KYLIN-3681
> URL: https://issues.apache.org/jira/browse/KYLIN-3681
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: v2.5.0
> Environment: kylin2.5.0
> Reporter: shenqiong
> Priority: Major
>
> Hi， I use two kylin instances with nginx to set up a query cluster, and I also config a session server with redis as the [link|https://blog.csdn.net/rlnLo2pNEfx9c/article/details/78796545] told. but there are still some query fail and hanging when queries from a page were sent to both of two instance. Because If I remove one kylin instance and left only one , query is working well.
> To be further, I tried to shut down the auth of query instance by modify kylinSecurity.xml by making all access = "permitAll", but still no help. As far as I can see, there should be a easy way to shut down auth for the query instance, because the auth can be done by higher domain system .Query is just for querying data but faster and still safe.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)