Mailing List Archive

Hi,

we also had to deal with slow dashboard, in our case it was a
misconfiguration of memcached [0], [1].

Check with your configuration and make sure you use oslo.cache.

Hope this helps!

[0] https://bugs.launchpad.net/keystone/+bug/1587777
[1]
https://ask.openstack.org/en/question/102611/how-to-configure-memcache-in-openstack-ha/


Zitat von ?? <gaosong1@syswin.com>:

> After kill one node of a cluster which consist of three nodes,
> I found that Horizon based on keystone with provider set to fernet
> respondes very slowly.
> Admin login will cost at least 20 senconds.
> And cli verbose command return show making authentication is stuck
> about 5 senconds.
> Any help will be appreciated.




_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

After kill one node of a cluster which consist of three nodes,

I found that Horizon based on keystone with provider set to fernet respondes very slowly.

Admin login will cost at least 20 senconds.

And cli verbose command return show making authentication is stuck about 5 senconds.

Any help will be appreciated.

Hi,

It could be a common issue between horizon and keystone.

As a temporary workaround for this, you can apply this [1] patch to
redirect admin user to the different page.

[1] https://review.openstack.org/#/c/577090/

Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/

On Thu, Jul 19, 2018 at 11:47 AM, Eugen Block <eblock@nde.ag> wrote:

> Hi,
>
> we also had to deal with slow dashboard, in our case it was a
> misconfiguration of memcached [0], [1].
>
> Check with your configuration and make sure you use oslo.cache.
>
> Hope this helps!
>
> [0] https://bugs.launchpad.net/keystone/+bug/1587777
> [1] https://ask.openstack.org/en/question/102611/how-to-configur
> e-memcache-in-openstack-ha/
>
>
> Zitat von ?? <gaosong1@syswin.com>:
>
>
> After kill one node of a cluster which consist of three nodes,
>> I found that Horizon based on keystone with provider set to fernet
>> respondes very slowly.
>> Admin login will cost at least 20 senconds.
>> And cli verbose command return show making authentication is stuck about
>> 5 senconds.
>> Any help will be appreciated.
>>
>
>
>
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
>

Sorry for the delay, different timezone huh!

Thanks a lot!
We'll try the solution!





At 2018-07-24 02:35:09, "Ivan Kolodyazhny" <e0ne@e0ne.info> wrote:

Hi,


It could be a common issue between horizon and keystone.


As a temporary workaround for this, you can apply this [1] patch to redirect admin user to the different page.


[1] https://review.openstack.org/#/c/577090/


Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/


On Thu, Jul 19, 2018 at 11:47 AM, Eugen Block <eblock@nde.ag> wrote:
Hi,

we also had to deal with slow dashboard, in our case it was a misconfiguration of memcached [0], [1].

Check with your configuration and make sure you use oslo.cache.

Hope this helps!

[0] https://bugs.launchpad.net/keystone/+bug/1587777
[1] https://ask.openstack.org/en/question/102611/how-to-configure-memcache-in-openstack-ha/


Zitat von ???? <gaosong1@syswin.com>:


After kill one node of a cluster which consist of three nodes,
I found that Horizon based on keystone with provider set to fernet respondes very slowly.
Admin login will cost at least 20 senconds.
And cli verbose command return show making authentication is stuck about 5 senconds.
Any help will be appreciated.





_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Further report!
We finally figure it out.
It because of the original memcache_server configuration which lead to load key from the poweroff controller
configuration example:
[cache]
backend = oslo_cache.memcache_pool
enabled = True
memcache_servers = controller1:11211,controller2:11211,controller3:11211
After change the server set to contoller_vip:11211??problem solved.






At 2018-07-24 02:35:09, "Ivan Kolodyazhny" <e0ne@e0ne.info> wrote:

Hi,


It could be a common issue between horizon and keystone.


As a temporary workaround for this, you can apply this [1] patch to redirect admin user to the different page.


[1] https://review.openstack.org/#/c/577090/


Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/


On Thu, Jul 19, 2018 at 11:47 AM, Eugen Block <eblock@nde.ag> wrote:
Hi,

we also had to deal with slow dashboard, in our case it was a misconfiguration of memcached [0], [1].

Check with your configuration and make sure you use oslo.cache.

Hope this helps!

[0] https://bugs.launchpad.net/keystone/+bug/1587777
[1] https://ask.openstack.org/en/question/102611/how-to-configure-memcache-in-openstack-ha/


Zitat von ???? <gaosong1@syswin.com>:


After kill one node of a cluster which consist of three nodes,
I found that Horizon based on keystone with provider set to fernet respondes very slowly.
Admin login will cost at least 20 senconds.
And cli verbose command return show making authentication is stuck about 5 senconds.
Any help will be appreciated.





_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Thanks for the update, Gao!

Let me know if any help is needed.

Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/

On Mon, Jul 30, 2018 at 5:02 PM, gao.song <gaosong_1250@163.com> wrote:

> Further report!
> We finally figure it out.
> It because of the original memcache_server configuration which lead to
> load key from the poweroff controller
> configuration example:
> [cache]
> backend = oslo_cache.memcache_pool
> enabled = True
> memcache_servers = controller1:11211,controller2:11211,controller3:11211
> After change the server set to contoller_vip:11211?problem solved.
>
>
>
>
>
> At 2018-07-24 02:35:09, "Ivan Kolodyazhny" <e0ne@e0ne.info> wrote:
>
> Hi,
>
> It could be a common issue between horizon and keystone.
>
> As a temporary workaround for this, you can apply this [1] patch to
> redirect admin user to the different page.
>
> [1] https://review.openstack.org/#/c/577090/
>
> Regards,
> Ivan Kolodyazhny,
> http://blog.e0ne.info/
>
> On Thu, Jul 19, 2018 at 11:47 AM, Eugen Block <eblock@nde.ag> wrote:
>
>> Hi,
>>
>> we also had to deal with slow dashboard, in our case it was a
>> misconfiguration of memcached [0], [1].
>>
>> Check with your configuration and make sure you use oslo.cache.
>>
>> Hope this helps!
>>
>> [0] https://bugs.launchpad.net/keystone/+bug/1587777
>> [1] https://ask.openstack.org/en/question/102611/how-to-configur
>> e-memcache-in-openstack-ha/
>>
>>
>> Zitat von ?? <gaosong1@syswin.com>:
>>
>>
>> After kill one node of a cluster which consist of three nodes,
>>> I found that Horizon based on keystone with provider set to fernet
>>> respondes very slowly.
>>> Admin login will cost at least 20 senconds.
>>> And cli verbose command return show making authentication is stuck about
>>> 5 senconds.
>>> Any help will be appreciated.
>>>
>>
>>
>>
>>
>> _______________________________________________
>> Mailing list: http://lists.openstack.org/cgi
>> -bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe : http://lists.openstack.org/cgi
>> -bin/mailman/listinfo/openstack
>>
>
>
>
>
>

Interesting, the HA guide [2] states that memcached should be
configured with the list of hosts:

> Access to Memcached is not handled by HAProxy because replicated
> access is currently in an experimental state.
> Instead, OpenStack services must be supplied with the full list of
> hosts running Memcached.

On the other hand, it would be only one of many incorrect statements
in that guide since I've dealt with it, so maybe this is just outdated
information (although the page has been modified on July 25th). Which
OpenStack version are you deploying?

Regards,
Eugen

[2] https://docs.openstack.org/ha-guide/controller-ha-memcached.html

Zitat von "gao.song" <gaosong_1250@163.com>:

> Further report!
> We finally figure it out.
> It because of the original memcache_server configuration which lead
> to load key from the poweroff controller
> configuration example:
> [cache]
> backend = oslo_cache.memcache_pool
> enabled = True
> memcache_servers = controller1:11211,controller2:11211,controller3:11211
> After change the server set to contoller_vip:11211?problem solved.
>
>
>
>
>
>
> At 2018-07-24 02:35:09, "Ivan Kolodyazhny" <e0ne@e0ne.info> wrote:
>
> Hi,
>
>
> It could be a common issue between horizon and keystone.
>
>
> As a temporary workaround for this, you can apply this [1] patch to
> redirect admin user to the different page.
>
>
> [1] https://review.openstack.org/#/c/577090/
>
>
> Regards,
> Ivan Kolodyazhny,
> http://blog.e0ne.info/
>
>
> On Thu, Jul 19, 2018 at 11:47 AM, Eugen Block <eblock@nde.ag> wrote:
> Hi,
>
> we also had to deal with slow dashboard, in our case it was a
> misconfiguration of memcached [0], [1].
>
> Check with your configuration and make sure you use oslo.cache.
>
> Hope this helps!
>
> [0] https://bugs.launchpad.net/keystone/+bug/1587777
> [1]
> https://ask.openstack.org/en/question/102611/how-to-configure-memcache-in-openstack-ha/
>
>
> Zitat von ?? <gaosong1@syswin.com>:
>
>
> After kill one node of a cluster which consist of three nodes,
> I found that Horizon based on keystone with provider set to fernet
> respondes very slowly.
> Admin login will cost at least 20 senconds.
> And cli verbose command return show making authentication is stuck
> about 5 senconds.
> Any help will be appreciated.
>
>
>
>
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack




_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Ocata.
Document is rigjht,But our platform is deployed using kolla-ansible, So,we utilize haproxy to
handle memcache access through virtual IP





At 2018-07-31 20:40:26, "Eugen Block" <eblock@nde.ag> wrote:
>Interesting, the HA guide [2] states that memcached should be
>configured with the list of hosts:
>
>> Access to Memcached is not handled by HAProxy because replicated
>> access is currently in an experimental state.
>> Instead, OpenStack services must be supplied with the full list of
>> hosts running Memcached.
>
>On the other hand, it would be only one of many incorrect statements
>in that guide since I've dealt with it, so maybe this is just outdated
>information (although the page has been modified on July 25th). Which
>OpenStack version are you deploying?
>
>Regards,
>Eugen
>
>[2] https://docs.openstack.org/ha-guide/controller-ha-memcached.html
>
>Zitat von "gao.song" <gaosong_1250@163.com>:
>
>> Further report!
>> We finally figure it out.
>> It because of the original memcache_server configuration which lead
>> to load key from the poweroff controller
>> configuration example:
>> [cache]
>> backend = oslo_cache.memcache_pool
>> enabled = True
>> memcache_servers = controller1:11211,controller2:11211,controller3:11211
>> After change the server set to contoller_vip:11211??problem solved.
>>
>>
>>
>>
>>
>>
>> At 2018-07-24 02:35:09, "Ivan Kolodyazhny" <e0ne@e0ne.info> wrote:
>>
>> Hi,
>>
>>
>> It could be a common issue between horizon and keystone.
>>
>>
>> As a temporary workaround for this, you can apply this [1] patch to
>> redirect admin user to the different page.
>>
>>
>> [1] https://review.openstack.org/#/c/577090/
>>
>>
>> Regards,
>> Ivan Kolodyazhny,
>> http://blog.e0ne.info/
>>
>>
>> On Thu, Jul 19, 2018 at 11:47 AM, Eugen Block <eblock@nde.ag> wrote:
>> Hi,
>>
>> we also had to deal with slow dashboard, in our case it was a
>> misconfiguration of memcached [0], [1].
>>
>> Check with your configuration and make sure you use oslo.cache.
>>
>> Hope this helps!
>>
>> [0] https://bugs.launchpad.net/keystone/+bug/1587777
>> [1]
>> https://ask.openstack.org/en/question/102611/how-to-configure-memcache-in-openstack-ha/
>>
>>
>> Zitat von ???? <gaosong1@syswin.com>:
>>
>>
>> After kill one node of a cluster which consist of three nodes,
>> I found that Horizon based on keystone with provider set to fernet
>> respondes very slowly.
>> Admin login will cost at least 20 senconds.
>> And cli verbose command return show making authentication is stuck
>> about 5 senconds.
>> Any help will be appreciated.
>>
>>
>>
>>
>>
>> _______________________________________________
>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>