Using Multiple Consoles For Distributed Process Control
Permalink
Bookmark
Share
Twitter
Digg
Reddit
Facebook
Stumbleupon
Del.icio.us| IP.com Number | IPCOM000177768D |
|
|
|---|---|---|---|
| Dated | Dec 30, 2008 UTC | ||
| Size | 4 page(s) (68.0 KB) | ||
| Disclosed by |
|
||
Publication Summary
Using multiple consoles for distributed process control| Country | |
|---|---|
| Language | English (United States) |
About this Publication
This document was submitted to IP.com's Prior Art Database and this preview is designed to provide you with information regarding the contents of this document by displaying up to the first four pages of the document as scaled page renderings and displaying a limited amount of text which was extracted from the document on the Text Preview Tab.
To find out more on how to obtain the entire document, click the Download tab. There is a charge for downloading some Prior Art Database documents; please examine carefully whether you believe this document fills your needs before purchasing.
For more information about the Prior Art Database, visit the Learn section of this website. Thank you for visiting IP.com's Prior Art Database! You may wish to check out our Intellectual Property Library website before you leave.
Using Multiple Consoles For Distributed Process Control
In a distributed cluster environment, sometimes we need to handle numerous inputs and outputs of many distributed processes, especially for those parallel programs, the major challenges are the complexity of operating on thousands of processes and tons of messages, some tools were introduced to handle these issues, it either used some message filtering and mining techniques, or used some task switch mechanisms to make the operator's life easier.
The major drawback of existed solutions is that all messages should be processed in one console, the console is either text-based or GUI-based, though it can also apply some convenient process switching mechanisms, there still have some scenarios which maybe hard to dealing with, furthermore, only one operator can work on it at the same time.
Our invention introduces multiple console views to operate on a distributed process set, and each console view can focus on a subset of processes, and each console view can be served as a command acceptor or just a monitor.
The core idea of our invention is to use multiple console views to operate on a set of distributed processes, comparing to existed solutions, our invention has the following advantages:
With multiple consoles (either text-based or GUI-based), each console has its own focus process subset, though you can implement some convenient process switch mechanisms, it is more convenient to have multiple consoles too, especially for some parallel programs, e.g., a parallel debugger.
As mentioned above, each console can serve as different purpose, either as a command acceptor, or as a monitor, it will be extremely useful in some scenarios, e.g., the complexity of the control effort is beyond one operator's ability, therefore more operators can work together with multiple consoles.
Here below is a diagram of our invention's overall structure:
1
There are a set of processes running on distributed cluster system, and the operator need to dealing with the inputs and outputs of the running process set, each process is represented by a Client in the diagram.
In our invention, each Client has an ID, the range of the ID is from 0 to N-1 (N is the number of processes to be dealing with), the Consoles communicate with the underlying Clients via a set of Agents which organized in a tree structure, the function of each Agent process is to serve as a communication bridge between its parent Agent or its children (maybe Clients or Agents).
The communication channels between Agents, Consoles and Clients can be socket connecti...