Changes between Version 1 and Version 2 of Old/NodeHandler/Broadcast


Ignore:
Timestamp:
Apr 10, 2006, 8:14:04 PM (18 years ago)
Author:
sswami
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Old/NodeHandler/Broadcast

    v1 v2  
    77
    88== Introduction ==
    9 The current NodeHandler code works satisfactorily on the small grid and the sandboxes. But this same code fails to work correctly on the big grid. This is due to the fact that in the current grid consisting of 400 nodes, packet loss is a major problem. And this problem escalates sharply with the increase in the no. of nodes. Specifically, when trying to image more than 150 nodes in a single attempt, the high packet loss prevents successful completion. To alleviate this problem, it has been decided to explore the use of broadcast instead of multicast.
     9The current NodeHandler code works satisfactorily on the small grid and the sandboxes. But this
     10same code fails to work correctly on the big grid. This is due to the fact that in the current
     11grid consisting of 400 nodes, packet loss is a major problem. And this problem escalates
     12sharply with the increase in the no. of nodes. Specifically, when trying to image more than 150
     13nodes in a single attempt, the high packet loss prevents successful completion. To alleviate
     14this problem, it has been decided to explore the use of broadcast instead of multicast.
    1015
    1116== Major Design Requirements ==
    1217'''R.1:'''
    1318{{{
    14 It has been decided that all communications from the NodeHandler to the NodAgent will be through broadcast and that all feedbacks from the NodeAgent to the NodeHandler will be sent through TCP. This is because then
     19It has been decided that all communications from the NodeHandler to the NodAgent will be
     20through broadcast and that all feedbacks from the NodeAgent to the NodeHandler will be sent
     21through TCP. This is because then
    1522
    1623- reliable feedbacks can then be ensured,
    … …  
    2633{{{
    2734All communication will be handled in the communication layer which will be a separate process.
    28 The present focus is on exploring reliable communication with minimum packet loss and once this issue is resolved, the issues pertaining to converting this process into a loadable library will be addressed to.
     35The present focus is on exploring reliable communication with minimum packet loss and once this
     36issue is resolved, the issues pertaining to converting this process into a loadable library
     37will be addressed to.
    2938
    3039This will need changes to the communication layer in both the NodeHandler and the NodeAgent.
    … …  
    3544The communication layer will use two separate approaches, one for sending messages and the
    3645other for receiving messages. Messages being sent from the NodeHandler to the NodeAgent will
    37 use broadcast. A single message will be broadcast by the NodeHandler and this message
    38 will be received by all the NodeAgents.
     46use broadcast. A single message will be broadcast by the NodeHandler and this message will be
     47received by all the NodeAgents.
    3948
    4049Messages being received from the NodeAgent will be use TCP. The NodeAgent communication layer
    … …  
    4554{{{
    4655The messages sent from the NodeHandler to the NodeAgent consist of commands to be executed on
    47 the NodeAgent. Since the communication layer will broadcast the message to all the nodes, the NodeAgents will have the filters to deteremine whether a message is to be accepted / rejected. Current NodeAgent code has such filters and these will be enhanced only if necessary.
     56the NodeAgent. Since the communication layer will broadcast the message to all the nodes, the
     57NodeAgents will have the filters to deteremine whether a message is to be accepted / rejected.
     58 Current NodeAgent code has such filters and these will be enhanced only if necessary.
    4859
    4960After a message is sent, the communication server will wait for ACKs from the NodeAgent, which