| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Website Support
Thread: Multiple Clients on the Same Host |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 5
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
BOINC supports running multiple clients on the same host. Does WCG support that BOINC feature? Both clients would not be run at the same time and would each have it's own data directory. SETI supports that function and each client shows up with the same host name. Does WCG allow multiple active devices with the same host name? This would be used to get through scheduled outages on the larger threaded machines. The 1000 WU limit in BOINC only provides 1 to 1 1/2 days of work for the shorter WUs. During scheduled outages, the plan would be to create two separate clients on the same machine each with 1000 WUs queued. Hopefully, providing 2 to 3 days of queued work to get past the outage. If WCG assigns a unique client identifier (other than hostname) to each client it should work but if the server only knows it assigned work to <hostname> it would get confused as each client instance is stopped and started. How does the WCG BOINC server track assigned work? By hostname? combination of hostname and some other identifier? by unique client id?
|
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
They can run at the same time, used to split threads (think I laid it out in another post few days earlier), without issue to WCG. In the example I used, suppose you have 8 threaded system, set each client to e.g. allow 50% of processors, then connect one client-instance to a profile for say OET1 and the second client-instance to SCC1. Presto pronto, perfect split of resource to 2 sciences of your choice.
----------------------------------------The host name has never been relevant, rather, it's the underlying device ID... that 7 digit number, where the device/host name is just the user friendly face. Use the network suppress option in the cc_config.xml, then it's easier to see which is which in the device statistics and result status pages. Note others run multiple VMs on one device to achieve this, and it might even be easier than the concurrent client instance set-up and managing (each client needing to use a different RPC port, 31416 being the default. edit: The network suppress tag is <suppress_net_info>1</suppress_net_info>. Got it on all the time... no need for WCG to know what my LAN network device names are. [Edit 1 times, last edit by SekeRob* at Nov 10, 2017 4:43:28 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thank you for the information... I was noticing in the sched_request* xml file, there is only a host ID specified but I wasn't sure if the server did something strange with that ID once it was returned. I'm planning on testing it later today.. Again, thanks for the information. Very helpful
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
It doesn't seem to work at WCG. Stopped first client. Started with empty data directory and a different port number for second client. After starting client, log indicates that the client is not attached to any projects as expected. Was able to define the new client to BoincTasks using the new port number and BoincTasks connected to the client. Attached new client to WCG and the normal initialization took place, benchmarks, downloading of .png files etc indicating successful attach. Here's the problem, the first scheduler request to the project used <hostid> of 0 (new client). The reply back from WCG in the sched_reply* xml file had the same <hostid> as the first client. The expectation would have been to assign a new <hostid> to the new client. Since it didn't, all 1000 WUs in the first client went detached. This process works at other projects but not at WCG. Can techs shed some light on what is happening on the server to prevent this from being supported?
----------------------------------------EDIT: may have found the problem. Left out <allow_multiple_clients> from cc_config.xml. Will test again. [Edit 1 times, last edit by Doneske at Nov 10, 2017 9:31:05 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Yep, that was it. Working as expected.
|
||
|
|
|