Bug #4425
closed
Rudder should not query all nodes when checking login
Added by Christophe Nowicki almost 11 years ago. Updated about 8 years ago.
Description
Hi,
I'am doing scalability testing of the rudder server, I've generated 4k
hosts with tsung ( http://tsung.erlang-projects.org/ ) and now
I can't login to my rudder-server ;-)
The login screen does timeout randomly.
Do you load all the pending hosts when the user log in ?
Thanks,
Files
Updated by Matthieu CERDA almost 11 years ago
- Category set to Web - Nodes & inventories
- Status changed from New to Discussion
- Assignee set to Matthieu CERDA
- Priority changed from N/A to 1 (highest)
Hi Christophe,
So you finally managed to get Tsung to cooperate :D
Well, to begin with, can you please take a look at the webapp's logs, and also try to boost the allocated RAM to Rudder in /etc/default/jetty ?
Thanks in advance.
Updated by Christophe Nowicki almost 11 years ago
Matthieu CERDA wrote:
Hi Christophe,
Hi Matthieu,
So you finally managed to get Tsung to cooperate :D
Yep ;-) And now everything is much funnier ;-)
Well, to begin with, can you please take a look at the webapp's logs, and also try to boost the allocated RAM to Rudder in /etc/default/jetty ?
The Webapp's log is empty :-( Do you need DEBUG information ?
I can't / want add more memory ;-)
Thanks,
Updated by Christophe Nowicki almost 11 years ago
Matthieu CERDA wrote:
Well, to begin with, can you please take a look at the webapp's logs, and also try to boost the allocated RAM to Rudder in /etc/default/jetty ?
Done, setup rudder 2.9.2 on my laptop with JAVA_XMX=2048 and JAVA_MAXPERMSIZE=512, I can log in with 2K hosts.
Updated by Nicolas CHARLES almost 11 years ago
That's awesome \o/
Thank you for the feedback
Updated by Jonathan CLARKE almost 11 years ago
- Status changed from Discussion to Rejected
OK, so if I understand correctly, this works fine if there is enough RAM?
Then I'll close this ticket, and hope it is useful to anyone having this same problem. Documentation work is ongoing to clarify Rudder's requirements in terms of RAM for large installations.
Christophe if you disagree, just say so, and we can reopen this.
Updated by Christophe Nowicki almost 11 years ago
- Status changed from Rejected to Discussion
Jonathan CLARKE wrote:
OK, so if I understand correctly, this works fine if there is enough RAM?
Non, The issue is not about RAM requirements.
We all agreed that you need enough RAM for handling a lots of nodes.
But loading all nodes when the user is logging on, it's an issue.
Then I'll close this ticket, and hope it is useful to anyone having this same problem. Documentation work is ongoing to clarify Rudder's requirements in terms of RAM for large installations.
Christophe if you disagree, just say so, and we can reopen this.
I strongly disagree.
Updated by Jonathan CLARKE almost 11 years ago
Christophe Nowicki wrote:
Jonathan CLARKE wrote:
OK, so if I understand correctly, this works fine if there is enough RAM?
Non, The issue is not about RAM requirements.
We all agreed that you need enough RAM for handling a lots of nodes.
But loading all nodes when the user is logging on, it's an issue.Then I'll close this ticket, and hope it is useful to anyone having this same problem. Documentation work is ongoing to clarify Rudder's requirements in terms of RAM for large installations.
Christophe if you disagree, just say so, and we can reopen this.
I strongly disagree.
OK, sorry for the misunderstanding.
Can we please clarify what this ticket is about then? I read the title that say "can't login when the number of hosts is too large", then you said "I can log in with 2K hosts". So I consider that problem is fixed.
If you'd like to refocus the ticket on "Rudder should not query all nodes when checking login", that's fine by me, but can we agree to change the title to that?
Updated by Jonathan CLARKE almost 11 years ago
- Assignee changed from Matthieu CERDA to Christophe Nowicki
Updated by Christophe Nowicki almost 11 years ago
Jonathan CLARKE wrote:
If you'd like to refocus the ticket on "Rudder should not query all nodes when checking login", that's fine by me, but can we agree to change the title to that?
I agree.
Updated by Jonathan CLARKE almost 11 years ago
- Subject changed from Can't login / proxy timeout when the number of hosts is too large to Rudder should not query all nodes when checking login
- Status changed from Discussion to New
- Assignee changed from Christophe Nowicki to François ARMAND
- Priority changed from 1 (highest) to 3
Christophe Nowicki wrote:
Jonathan CLARKE wrote:
If you'd like to refocus the ticket on "Rudder should not query all nodes when checking login", that's fine by me, but can we agree to change the title to that?
I agree.
Perfect, thanks :)
Updated by François ARMAND almost 11 years ago
In our tests, even will >2000 nodes, we weren't able to reproduce a case where the login was not possible, or even where LDAP requests took more than a few seconds to return WHEN (a big when) no inventories where received by the endpoint in parallele.
On the other hand, we exibited #4497, where a memory exhaustion was initiated by accumulating incoming inventories to proccess. That memory exhaustion lead to global stalling of both Rudder inventory endpoint and Rudder UI part, which look similar to what was described here.
Updated by François ARMAND about 8 years ago
- Status changed from New to Rejected
I'm closing that ticket because Rudder is not querying pending nodes on login, and the problem was with #4497 + compliance culculus done on login.