[MonetDB-users] Running multiple instances on same machine
Hi, Can you please tell me how to run three different MonetDB instances on one machine? I created three different binaries from the install and I tried to change the port from 50000 to 50001, 50002 and 50003. But for some reason I can only connect using 50000. Thanks, -Venks
Venks wrote:
Hi,
Can you please tell me how to run three different MonetDB instances on one machine?
I created three different binaries from the install and I tried to change the port from 50000 to 50001, 50002 and 50003. But for some reason I can only connect using 50000. Hi
You don't need three binaries. You can set the properties on the command line. You only have to ensure that each server has a dedicated (dbfarm/dbname,port) Window 1: mserver5 --dbfarm=`pwd`/monet5/dbfarm --dbname=demo --set mapi_port=50001 # MonetDB server v5.3.0, based on kernel v1.21.0 # Serving database 'demo' # Compiled for x86_64-redhat-linux-gnu/64bit with 64bit OIDs dynamically linked # Copyright (c) 1993-2007 CWI, all rights reserved # Visit http://monetdb.cwi.nl/ for further information #warning: please don't forget to set your vault key! #(see /ufs/mk/monet5//Linux/etc/monetdb5.conf) # Listening for connection requests on mapi:monetdb://127.0.0.1:50001/
Window2: mserver5 --dbfarm=`pwd`/monet5/dbfarm --dbname=tst --set mapi_port=50002 # MonetDB server v5.3.0, based on kernel v1.21.0 # Serving database 'tst' # Compiled for x86_64-redhat-linux-gnu/64bit with 64bit OIDs dynamically linked # Copyright (c) 1993-2007 CWI, all rights reserved # Visit http://monetdb.cwi.nl/ for further information #warning: please don't forget to set your vault key! #(see /ufs/mk/monet5//Linux/etc/monetdb5.conf) # Listening for connection requests on mapi:monetdb://127.0.0.1:50002/
Furthermore, running multiple servers and proper redirection of requests is handled by the merovingian/monetdb packages. regards, Martin
Thanks,
-Venks ------------------------------------------------------------------------
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ ------------------------------------------------------------------------
_______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
Martin,
Thanks for your reply.
I was setting port = xxxx instead of mapi_port and that's when I created
three binaries to see if I could set the mapi_port in each of the
configuration files. Anyhow, now I am able to run 3 instances from one
binary on 3 different ports and three different data/log directories.
On Nov 21, 2007 1:47 AM, Martin Kersten
Venks wrote:
Hi,
Can you please tell me how to run three different MonetDB instances on one machine?
I created three different binaries from the install and I tried to change the port from 50000 to 50001, 50002 and 50003. But for some reason I can only connect using 50000. Hi
You don't need three binaries. You can set the properties on the command line. You only have to ensure that each server has a dedicated (dbfarm/dbname,port)
Window 1: mserver5 --dbfarm=`pwd`/monet5/dbfarm --dbname=demo --set mapi_port=50001 # MonetDB server v5.3.0, based on kernel v1.21.0 # Serving database 'demo' # Compiled for x86_64-redhat-linux-gnu/64bit with 64bit OIDs dynamically linked # Copyright (c) 1993-2007 CWI, all rights reserved # Visit http://monetdb.cwi.nl/ for further information #warning: please don't forget to set your vault key! #(see /ufs/mk/monet5//Linux/etc/monetdb5.conf) # Listening for connection requests on mapi:monetdb://127.0.0.1:50001/
Window2: mserver5 --dbfarm=`pwd`/monet5/dbfarm --dbname=tst --set mapi_port=50002 # MonetDB server v5.3.0, based on kernel v1.21.0 # Serving database 'tst' # Compiled for x86_64-redhat-linux-gnu/64bit with 64bit OIDs dynamically linked # Copyright (c) 1993-2007 CWI, all rights reserved # Visit http://monetdb.cwi.nl/ for further information #warning: please don't forget to set your vault key! #(see /ufs/mk/monet5//Linux/etc/monetdb5.conf) # Listening for connection requests on mapi:monetdb://127.0.0.1:50002/
Furthermore, running multiple servers and proper redirection of requests is handled by the merovingian/monetdb packages.
regards, Martin
Thanks,
-Venks ------------------------------------------------------------------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ ------------------------------------------------------------------------
_______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
On 21-11-2007 07:36:58 -0500, Venks wrote:
Martin,
Thanks for your reply.
I was setting port = xxxx instead of mapi_port and that's when I created three binaries to see if I could set the mapi_port in each of the configuration files. Anyhow, now I am able to run 3 instances from one binary on 3 different ports and three different data/log directories.
By the way; mserver5 has an "auto sensing port" feature that would basically allow you not to bother about setting ports. When you connect to the default port 50000, provided one mserver5 is running on it, the mserver will redirect you to the others if you specify the database you're looking for (which is a good idea in a way anyway). Not surprisingly, merovingian uses parts of this functionality to do its job.
participants (3)
-
Fabian Groffen -
Martin Kersten -
Venks