Adaptive self-repair and configuration in distributed systems

• US 20040103185A1
• Filed: 11/21/2002
• Published: 05/27/2004
• Est. Priority Date: 11/21/2002
• Status: Abandoned Application

• Current Assignee: BBN Technologies Corporation (Rtx Corporation)
• Original Assignee: BBN Technologies Corporation (Rtx Corporation)
• Inventors: Combs, Nathan Hideaki
• Application Number:
  US10/301,265
• Publication Number:
  US 20040103185A1
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A distributed application [200] includes the ability to adaptively mirror components in the application, giving the application the ability to self-heal. Hint data [600] and constraint data [500] are used when mirroring a failing component and when initially assembling a distributed workflow. The constraint data [500] defines relatively rigid service rules and the hint data defines less-rigid “suggestive” service rules.

Claims

1. A method for replacing a first service in a distributed application, the method comprising:

monitoring the first service;

determining, based on the monitoring, when the first service stops providing an acceptable level of service; and

substituting a mirror service for the first service when the first service is determined to have stopped providing the acceptable level of service, the mirror service being determined based on directive information that includes hint information and constraint information, the constraint information defining rigid service rules and the hint information providing suggestive information relating to services.

2. The method of claim 1, wherein determining when the first service stops providing an acceptable level of service is based on information provided by software probes associated with the first service.

3. The method of claim 2, wherein the information provided by the software probes is gathered by software gauges.

4. The method of claim 3, wherein the software gauges aggregate and interpret the information provided by the software probes.

5. The method of claim 1, wherein determining when the first service stops providing an acceptable level of service includes:

determining that the first service has failed.

6. The method of claim 1, wherein determining when the first service stops providing an acceptable level of service includes:

determining that the first service has violated a constraint defined by the constraint information.

7. The method of claim 1, wherein a connector component is used to substitute the mirror service for the first service.

8. A distributed application comprising:

means for monitoring a first service of the distributed application;

means for determining, based on an output of the means for monitoring, when the first service stops providing an acceptable level of service; and

means for substituting a second service for the first service when the first service is determined to have stopped providing an acceptable level of service, the second service being determined based on directive information that includes hint information and constraint information, the constraint information defining rigid service rules and the hint information providing suggestive information relating to services.

9. A method for assembling a workflow of distributed service providers, the method comprising:

receiving a request for a first service, the request including constraint information and hint information, the constraint information defining rigid service rules and the hint information providing suggestive information relating to services;

requesting a second service required to complete the first service based on the constraint information and the hint information;

receiving feedback information from the second service; and

modifying the hint information based on the feedback information.

10. The method of claim 9, wherein the workflow is assembled based on a Service and Contract workflow protocol.

11. The method of claim 9, wherein the first service and the second service are provided by service providers on different computer systems.

12. The method of claim 9, wherein the constraint information includes at least one of:

a list of suitable service providers, and

a service specification.

13. The method of claim 9, wherein the hint information includes at least one of:

suggested service destinations, and

historical invocation time information.

14. The method of claim 9, wherein modifying the hint information based on the feedback information is performed using a set of predefined rules.

15. A system comprising:

a first computing device including

a first processor, and

a first memory operatively coupled to the first processor, the first memory including instructions for implementing a first service, the first service including constraint information and hint information, the constraint information defining rigid service rules and the hint information providing suggestive information relating to the first service, the hint information being based on feedback information; and

a second computing device including

a second processor, and

a second memory operatively coupled to the second processor, the second memory including

instructions for implementing a second service,

instructions for receiving a request from the first service to invoke the second service, the request including the constraint information and the hint information, and

instructions for providing the feedback information to the first service based on execution of the first service.

16. The system of claim 15, wherein the second service is selected by the first service based on the hint information.

17. The system of claim 15, wherein the first service further includes:

a hint generation engine that receives the feedback information from the second service and modifies the hint information based on the feedback information.

18. The system of claim 15, wherein the constraint information includes at least one of:

a list of suitable service providers, and

a service specification.

19. The system of claim 15, wherein the hint information includes at least one of:

suggested service destinations, and

historical invocation time information.

20. The system of claim 15, wherein the first and the second services define a distributed application.

21. A computer-readable medium storing instructions for causing at least one processor to perform a method for assembling a workflow of distributed service providers, the computer-readable medium comprising:

instructions for receiving a request from a first service, the request including constraint information and hint information, the constraint information defining rigid service rules and the hint information providing suggestive information relating to services;

instructions for requesting a second service required to complete the first service based on the constraint information and the hint information;

instructions for receiving feedback information from the second service; and

instructions for modifying the hint information based on the feedback information.

22. The computer-readable medium of claim 21, wherein the workflow is assembled based on a Service and Contract workflow protocol.

23. The computer-readable medium of claim 21, wherein the first service and the second service are provided by service providers on different computer systems.

24. The computer-readable medium of claim 21, wherein the constraint information includes at least one of:

a list of suitable service providers, and

a service specification.

25. The computer-readable medium of claim 21, wherein the hint information includes at least one of:

suggested service destinations, and

historical invocation time information.

26. The computer-readable medium of claim 21, wherein modifying the hint information based on the feedback information is performed using a set of predefined rules.