Comment 8 for bug 1804239

Thank you, Maurice.

Regarding the issue that Fernando has pointed out, we are working on providing
a patch to fix it. We created a cache to be used for all share server pool status.
Measuring the time for collecting the pool for the share servers (no cache):

Server | Time update pool (s)|
-------|---------------------|
1 | 0.44 |
-------|---------------------|
10 | 4.01 |
-------|---------------------|
50 | 20.02 |
-------|---------------------|
100 40.40 |
-------|---------------------|
200 | 80.27 |
-----------------------------

With the cache, the time is always around 1 second, no matter the number of servers
We are not sure if the patch will fix the bug, though, because we are still struggling
to reproduce the Timeout error.

Maurice, in order to reproduce, could you provide some extra information:

1. How many nodes are in the cluster ?!

2. How many backends are you using ?

3. How many aggregates (pools) ?

4. What does the cluster respond when sending this XML http://paste.openstack.org/show/799078/ ?

Best regards, Felipe.