JPPF, java, parallel computing, distributed computing, grid computing, parallel, distributed, cluster, grid, cloud, open source, android, .net
JPPF

The open source
grid computing
solution

 Home   About   Features   Download   Documentation   On Github   Forums 
December 13, 2019, 03:30:23 AM *
Welcome,
Please login or register.

Login with username, password and session length
Advanced search  
News: New users, please read this message. Thank you!
  Home Help Search Login Register  
Pages: [1]   Go Down

Author Topic: JPPF Gateway scenario  (Read 1774 times)

clgv

  • JPPF Master
  • ***
  • Posts: 25
JPPF Gateway scenario
« on: August 21, 2012, 12:29:38 PM »

I have the following gateway scenario (with JPPF 3.1.1):
I run a JPPF server on node S with a global IP. There are at least three nodes E1, E2, E3, ... that are accessible via a global IP.
Then there are several nodes L1, L2, ... that are only local to node S in a private subnet (Node S is their gateway).

When using the admin-ui I can connect to the server S and  the node E1, E2, ...., the local nodes where visible when I set their jppf.management.host to their local IP (192.168.X.Y), but the admin-ui could not display any information about them (e.g. Node Name, Threads, Node Status ...).

Can I configure only one driver on node S to implement the scenario or do I need two drivers one for the global nodes and one for the local nodes?
How would that be done?
Logged

clgv

  • JPPF Master
  • ***
  • Posts: 25
Re: JPPF Gateway scenario
« Reply #1 on: August 21, 2012, 01:39:37 PM »

Let me add some additional info. The JPPF connections are all working.
It seems the management connections are established directly to the nodes by the admin-ui.
So the server S knows the local nodes L1, L2, ... and tells the admin-ui about them, but then the admin-ui cannot connect to them directly.

But when I forward the port for management on server S on different ports to each of the local nodes L1, L2, ...
Then the admin-ui does not show the local nodes L1, L2, ... at all.
Logged

lolo

  • Administrator
  • JPPF Council Member
  • *****
  • Posts: 2258
    • JPPF Web site
Re: JPPF Gateway scenario
« Reply #2 on: August 22, 2012, 06:15:00 AM »

Hello,

As you pointed out, the problem is that the admin console makes direct connections to the nodes to access their JMX MBeans. As a result, it will generally be unable to monitor or manage nodes that are in a different subnet. It will see that there are nodes on the local subnet, because that information is initially provided by the JPPF driver, but it will not be able to connect to them.

I believe this is also why port forwarding isn't working: the admin console gets the jmx host/port information for each node from the driver, which in turn gets this information from the node, as part of the handshake protocol when the node connects to the driver. So, the admin console will still try to connect to a host that is unreachable from its perspective.

Unfortunately, we do not have an immediate solution to this. We are addressing it in order to deliver a working solution for JPPF v3.2, however it will take some time.
For reference, we are tracking this via feature request JPPF-26 Enable node management via the driver connection .

Sincerely,
-Laurent
Logged

clgv

  • JPPF Master
  • ***
  • Posts: 25
Re: JPPF Gateway scenario
« Reply #3 on: August 22, 2012, 11:12:32 AM »

Currently, as a workaround I can "ssh -X" to the gateway node and run the admin-ui there.
But good to here that node management via driver connection will be implemented in v3.2.
Logged
Pages: [1]   Go Up
 
JPPF Powered by SMF 2.0 RC5 | SMF © 2006–2011, Simple Machines LLC Get JPPF at SourceForge.net. Fast, secure and Free Open Source software downloads