 |
 |
(Add Cc mailing list) Hi Doug, I think the simplest way to go is to start by installing a single node qserv on each of the nodes. You will need a frontend node and worker nodes. The hardest part is getting the data loaded. If the data can physically fit on one node then you can load it there in a single node configuration and then manually migrate chunks to other nodes. Note that unpartitioned tables, for now, need to be replicated on all worker nodes. Once the data is distributed, you can alert the xrootd/cmsd configuration files in the worker to point at your manager xrootd/cmsd in the usual way(easiest to run the manager on the same node as the frontend), and then on the frontend, configure the xrootd/cmsd as manager, disabling the qserv xrootd plugins for the manager. That's the gist of it, but I've left out a lot of details. It's probably easier to try a single node configuration with a smaller data set to work out any schema or data problems before complicating things with multi nodes. Do you want to try that out and let us know about any issues first? Good luck! -Daniel (typed on a small touch screen) On Jan 31, 2015 12:21 PM, Doug Benjamin <[log in to unmask]> wrote: > > Hi Daniel, > > It was nice meeting you at Xrootd meeting. I talked with my colleagues and ANL > and it was agreed that I would setup a 2-3 node cluster on out Magellan cloud > resources. > > I see the Qserv documentation is here - > > http://lsst-web.ncsa.illinois.edu/~fjammes/qserv-doc/ > > and here is the git repository for the project - > > https://github.com/LSST/qserv/ > > Would it be possible to get instructions for a multi node configuration. > > I have plenty of experience setting xrootd so that should not be a problem. > > Thanks, > > Doug Benjamin > > > ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the QSERV-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1