Method and apparatus for providing fault tolerance in a collaboration environment

• US 20070168720A1
• Filed: 11/30/2005
• Published: 07/19/2007
• Est. Priority Date: 11/30/2005
• Status: Abandoned Application

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Chatterjee, Ramkrishna, Arun, Gopalan
• Application Number:
  US11/291,351
• Publication Number:
  US 20070168720A1
• Time in Patent Office: Days
• US Class Current: 714/15
• CPC Class Codes: G06F 11/1482 by means of middleware or OS functionality

Abstract

A fault processor in a collaboration server models collaborative operations as a state machine. The fault processor divides collaboration operations into discrete segments, in which each segment corresponds to a repository update. A state definition defines the progression of states between the segments, and defines transitions to recovery states in the event of unexpected interruption. A state log maintains the completion status of each segment in the operation, and recovery logic employs the state log to perform recovery of an abnormally terminated operation. The recovery logic computes the segments to be performed in a recovery. Compatibility logic selectively prohibits operations which may affect or be affected by inconsistencies presented prior to successful recovery. In this manner, collaboration software defined according to configurations herein identifies failures, implements recovery based on a state machine corresponding to segments of an operation, and preserves consistency by recovering the incremental segments defined by the states.

Claims

1. A method of performing fault tolerance in a collaboration environment comprising:

identifying a plurality of segments of an operation, each segment indicative of partial completion of the operation;

defining a state corresponding to each segment;

performing each of the segments in the order defined by the states; and

transitioning to a recovery state if performing a segment results in an incomplete result.

2. The method of claim 1 wherein each of the segments corresponds to an update to a particular repository from among the plurality of repositories included in the operation.

3. The method of claim 2 wherein performing the segments further comprises writing to a state log, the state log operable to identify the state of the operation as at least one of successfully completed, just failed and ongoing.

4. The method of claim 3 further comprising identifying a state definition indicative of, for each state, a next state for success and failure transitions, a failure transition corresponding to a recovery state.

5. The method of claim 4 wherein transitioning to a recovery state further comprises selecting between completion based recovery and rollback based recovery.

6. The method of claim 5 wherein performing the rollback based recovery further comprises:

reverting to the last completed state; and

performing a compensating step for each completed state to achieve consistency for the compensated step.

7. The method of claim 1, further comprising defining recovery logic operable to identify, from a particular current state, a transition state for advancement.

8. The method of claim 7 wherein identifying the transition state further comprises:

storing a current state;

referencing a state definition indicative of the next state based on a particular current state;

updating a state log upon completion; and

transitioning to the referenced next state.

9. The method of claim 8 wherein the state definition defines a deterministic state of the operation from each state based on the outcome of the previous state.

10. The method of claim 9 wherein each of the segments corresponds to a repository update, performing the segment further comprising writing the corresponding update to the repository.

11. The method of claim 10 further comprising defining a plurality of states corresponding to segments, the segments indicative of predetermined demarcations of a portion of the entire operation, the predetermined demarcations indicative of partial completion of the operation.

12. The method of claim 11 wherein partial completion is indicative of storing the updates in a subset of a plurality of repositories corresponding to the entire operation.

13. The method of claim 12 further comprising:

writing the completed state to a state log; and

storing the state log and the update corresponding to the segment in the same volume such that a single SQL statement is operable to update both.

14. The method of claim 12 further comprising, in the event of partial completion of an operation:

identifying concurrent operations being attempted during recovery of a partial completion;

computing if the identified concurrent operation is compatible with the partial completion; and

selectively disallowing the concurrent operation if it is not compatible with the partial completion.

15. The method of claim 1 wherein the states define a nonlinear finite state machine, at least one of the states corresponding to a conditional transition based on completion of a predetermined set of data repositories.

16. A fault tolerant collaboration server operable in a collaboration environment comprising:

a fault processor operable to identify a plurality of segments of an operation, each segment indicative of partial completion of the operation;

a state definition operable to define a state corresponding to each segment, the collaboration server operable to perform each of the segments in the order defined by the states; and

recovery logic operable to transition to a recovery state if performing a segment results in an incomplete result.

17. The server of claim 16 wherein each of the segments corresponds to an update to a particular repository from among the plurality of repositories included in the operation.

18. The server of claim 17 further comprising a state log indicative of completed segments, wherein the recovery logic is further operable to write to a state log, the state log operable to identify the states as at least one of successfully completed, just failed and ongoing.

19. The server of claim 18 wherein the state log is further operable to identify a state definition indicative of, for each state, a next state for success and failure transitions, a failure transition corresponding to a recovery state.

20. The server of claim 19 wherein the recovery logic is further operable to select between completion based recovery and rollback based recovery during transition to a recovery state.

21. The server of claim 20 wherein the recovery logic is further operable to performing the rollback based recovery by:

reverting to the last completed state; and

performing a compensating step for each completed state to achieve consistency for the compensated step.

22. The server of claim 21 wherein the recovery logic is further operable to:

write the completed state to a state log; and

store the state log and the update corresponding to the segment in the same volume such that a single SQL statement is operable to update both.

23. The server of claim 22 further comprising compatibility logic operable to, in the event of partial completion of an operation:

identify concurrent operations being attempted during recovery of a partial completion;

compute if the identified concurrent operation is compatible with the partial completion; and

selectively disallow the concurrent operation if it is not compatible with the partial completion.

24. A computer program product having a computer readable medium operable to store computer program logic embodied in computer program code encoded thereon, the computer program code receivable by a processor for executing computer program instructions for performing fault tolerance in a collaboration environment comprising:

computer program code for identifying a plurality of segments of an operation, each segment segments corresponding to an update to a particular repository from among the plurality of repositories included in the operation;

computer program code for defining a state corresponding to each segment;

computer program code for performing each of the segments in the order defined by the states; and

computer program code for transitioning to a recovery state if performing a segment results in an incomplete result.

25. A computing device for performing fault tolerance in a collaboration environment comprising:

means for identifying a plurality of segments of an operation, each segment indicative of partial completion of the operation;

means for defining a state corresponding to each segment;

means for performing each of the segments in the order defined by the states; and

means for transitioning to a recovery state if performing a segment results in an incomplete result, each of the segments corresponding to an update to a particular repository from among the plurality of repositories included in the operation; and

means for writing to a state log, the state log indicative of segment completion and operable to identify the state of the operation as at least one of successfully completed, just failed and ongoing.