Welcome to the new Gigaspaces XAP forum. To recover your account, please follow these instructions.

Ask Your Question
0

Use GSC or gsInstance or both?

(GigaSpaces 6.0) I want to deploy PU's against a partitioned space with backup (2,1). I can use GSC's for this, and simply pudeploy against them. However, it's not clear to me how I can explicitly specify a space name (such as ServiceSpace) and avoid the default name of mySpace. All the examples show mySpace, and don't really address the issue of using a different name.

Or, I can use gsInstance with an appropriate cluster schema, etc. and explicitly specify the desired space name (URL). I'd still need to deploy GSC's for the PU's, which will reference the space by jini:// URL in the pu.xml.

Is this correct, or am I missing/overlooking something -- or just don't understand how this can/should be done?

Thanks. h4. Attachments

[pu.xml|/upfiles/13759717775260909.xml]

{quote}This thread was imported from the previous forum. For your reference, the original is [available here|http://forum.openspaces.org/thread.jspa?threadID=2468]{quote}

asked 2008-07-21 01:45:38 -0500

updated 2013-08-08 09:52:00 -0500

jaissefsfex gravatar image
edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted
0

John,

Using gsInstance gets progressively more difficult as the size of the cluster grows. I strongly recommend using GSCs and Processing Units exclusively. I've attached a simple example pu.xml file that starts one worker for each node of a space with a specified name. To start a 2,1 sync-to-backup topology with this file (and associated code, of course) from the command line, first start four GSCs and a GSM, then run:

${JSHOMEDIR}/bin/gs.sh pudeploy -cluster schema=partitioned-sync2backup total_members=2,1 hello-world-worker

The space name is specified in the pu.xml.

Regards,

Patrick

Attachments

  1. pu.xml

answered 2008-07-21 11:10:26 -0500

patrickm gravatar image
edit flag offensive delete link more

Comments

Thanks to Shay and Patrick for your prompt responses -- much appreciated.

Patrick, good to hear from you! Thanks for a concise explanation and an example to demonstrate. I +thought+ that's the way it +should+ work, but having never done this before ;-) one doesn't trust their intuition!

I tried that and it works as advertised. We'll stick with GSC's then, and forego the gsInstance's.

Once again, good to hear from you. Hope to see you again soon.

John

bluesbrother gravatar imagebluesbrother ( 2008-07-21 18:38:44 -0500 )edit
0

Here is how you specify the space name when deployed via the pu.xml: <os-core:space id="space" url="/./MySpaceName"/>

Here is the URL a remote client should use to connect to the above deployed space with multicast lookup discovery: jini:////MySpaceName or with unicast lookup discovery: jini:////MySpaceName?locators=HOST_NAME_RUNNING_GSM

The above means that a PU that needs to connect to a remote space should have the following within its pu.xml: <os-core:space id="space" url="jini://*/*/MySpaceName"/>

When using the gsInstance to start the space (single one non clustered) - here is how the URL should look like: gsInstance "/./MySpaceName"

Shay

answered 2008-07-21 07:58:41 -0500

shay hassidim gravatar image
edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2008-07-21 01:45:38 -0500

Seen: 25 times

Last updated: Jul 21 '08