aristeo Posted December 10, 2018 Share Posted December 10, 2018 In our Hyperserver, a node is created when a new session starts (ScreenShot attached). With this hypersever.cfg i don't know why. I think, one node for all sessions is the correct. [transport] pool_size=0 command_timeout=20000 request_timeout=300000 connect_timeout=20000 [http_transport] start_port=20000 [hyper_server] binary_name=portalsii.dll initial_nodes=2 max_nodes=8 max_sessions=0 sessions_per_nodes=0 prompt_login=1 persistent_node_zero=0 port=8077 url_path= url_referer= ext_root=C:\inetpub\Sitios\portalSII\WebApp\files\js\1.50.0.1483\ext uni_mobile_root=[unim]\ uni_root=C:\inetpub\Sitios\portalSII\WebApp\files\js\1.50.0.1483\uni uni_packages_root=[unipack]\ max_requests=500 antiflood_per_ip=0 [node_recycling] enabled=1 recycle_after_secs=3600 recycle_after_sessions=0 recycle_after_idle_secs=300 recycle_when_empty=1 Thanks Quote Link to comment Share on other sites More sharing options...
Administrators Farshad Mohajeri Posted December 10, 2018 Administrators Share Posted December 10, 2018 Hi, Yes, this is the correct behavior. HyperServer will try to evenly distribute load among all Nodes. If you want to have fewer Nodes then you can decrease the Max_nodes parameter. Quote Link to comment Share on other sites More sharing options...
aristeo Posted December 10, 2018 Author Share Posted December 10, 2018 Ok, thanks Quote Link to comment Share on other sites More sharing options...
Stemon63 Posted December 11, 2018 Share Posted December 11, 2018 Hi, Farshad, Other than actual way, I remember you that I need nodes loading on needs, one by one when the previuos have max session connected... So I have only one node on start... Best Job! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.