# US 2015/0106327 A1 · Self healing cluster of a content management system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2015/0106327 A1
- Document ID: US20150106327A1
- Status: Published application
- Kind: A1
- Application number: 14/050,847
- Filed: 2013-10-10
- Published: 2015-04-16
- Earliest claimed: 2013-10-10
- Assignees: Adobe Systems Incorporated
- Applicants: Adobe Systems Incorporated
- Inventors: Michael Marth; Dominique Pfister; Thomas Müller Graf; Marcel Reutegger
- Web page: https://patentgrep.com/patent/US20150106327A1

## CPC

- G06F 11/1425: {by reconfiguration of node membership}
- G06F 11/0709: {in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems}
- G06F 11/0793: {Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40)}
- G06F 11/1658: {Data re-synchronization of a redundant component, or initial sync of replacement, additional or spare unit}
- G06F 11/2094: {Redundant storage or storage space (G06F11/2056 takes precedence)}
- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
- H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06)
- G06F 11/2028: {eliminating a faulty processor or activating a spare}
- G06F 11/2035: {without idle spare hardware}
- G06F 11/2046: {where the redundant components share persistent storage (G06F11/2043 takes precedence)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems and methods herein provide for a clustered content management comprising at least two computing nodes. A first node comprises an instance of the content repository. The first computing node may perform content management operations on its instance of the content repository. Changes to the instance of the content repository of the first computing node are synchronized with the content repository by way of a second computing node. The second computing node is communicatively coupled to the first computing node through a network and is operable to synchronize the change with the content repository. The second computing node also determines that synchronization of the change is blocked due to an error. The second computing node identifies the error, determines that the error is correctable, and corrects the error to synchronize the change with the content repository.

## Claims

### Claim 1

A content management system, comprising:
a content repository;
a first computing node operable to load a first instance of the content repository and to change the first instance of the content repository; and
a second computing node communicatively coupled to the first computing node through a network,
wherein the second computing node is operable to synchronize the content repository with the change to the first instance of the content repository, to determine that synchronization of the change is blocked due to an error, to identify the error blocking the synchronization, to determine that the error is correctable, and to correct the error to synchronize the change with the content repository.

### Claim 2 (depends on 1)

The content management system of claim 1, wherein:
the second computing node is further operable to detect another error, to determine that the other error is not correctable, and to relinquish synchronization control of the content repository in response to detecting the other error is not correctable.

### Claim 3 (depends on 2)

The content management system of claim 2, further comprising:
a third computing node operable to change a second instance of the content repository,
wherein the first and the third computing nodes are further operable to detect that the second computing node is relinquishing the synchronization control of the content repository, and to communicate with each other to determine which of the first and the third computing nodes takes the synchronization control of the content repository.

### Claim 4 (depends on 1)

The content management system of claim 1, wherein:
the second computing node is operable on a computer comprising a storage module;
the error is a storage space limit of the storage module; and
the second computing node is operable to delete one or more objects from the storage module to increase available storage space and correct the error.

### Claim 5 (depends on 1)

The content management system of claim 1, further comprising:
a timer operable to start when the second computing node determines that the error is with the second computing node and to direct the second computing node to relinquish synchronization control of the content repository to the first computing node if the error is not corrected upon expiration of the timer.

### Claim 6 (depends on 1)

The content management system of claim 1, wherein:
the error is a network error that prevents the second computing node from communicating with the first computing node; and
the second computing node is operable to reinitialize a network interface to correct the error.

### Claim 7 (depends on 1)

The content management system of claim 1, wherein:
the second computing node comprises an instance of the content repository.

### Claim 8 (depends on 1)

The content management system of claim 1, wherein:
the content repository is a Java Content Repository.

### Claim 9 (depends on 1)

The content management system of claim 1, further comprising:
a Java Management Extension monitor operable to detect the error with the second computing node and to report the error to the second computing node.

### Claim 10 (depends on 1)

The content management system of claim 1, wherein:
the second computing node is operable to detect an error with the first computing node and to direct the first computing node to correct the error.

### Claim 11

A method operable in a clustered content management system comprising a content repository and at least first and second computing nodes, the method comprising:
initiating synchronization of the content repository based on a change to an instance of the content repository by the first computing node;
determining, via the second computing node, that synchronization of the change with the content repository is blocked due to an error;
identifying the error blocking the synchronization; and
correcting the error to synchronize the change with the content repository.

### Claim 12 (depends on 11)

The method of claim 11, further comprising:
detecting another error;
determining that the other error is not correctable; and
relinquishing synchronization control of the content repository in response to detecting the other error is not correctable.

### Claim 13 (depends on 12)

The method of claim 12, further comprising:
detecting that the second computing node is relinquishing the synchronization control of the content repository; and
communicating between the first computing node and a third computing node of the content management system to determine which of the first and the third computing nodes takes the synchronization control of the content repository.

### Claim 14 (depends on 11)

The method of claim 11, wherein:
identifying the error comprises determining that a storage space limit of the second computing node has been exceeded; and
the method further comprises deleting one or more objects from the second computing node to increase available storage space and correct the error.

### Claim 15 (depends on 11)

The method of claim 11, further comprising:
starting a timer when the second computing node determines that the error is with the second computing node; and
transferring synchronization control of the content repository to the first computing node if the error is not corrected upon expiration of the timer.

### Claim 16 (depends on 11)

The method of claim 11, wherein:
identifying the error comprises determining that a network error prevents communication between the second computing node and the first computing node; and
the method further comprises re-initializing a network interface of the second computing node to correct the error.

### Claim 17 (depends on 11)

The method of claim 11, wherein:
the content repository is a Java Content Repository.

### Claim 18 (depends on 1)

The method of claim 1, further comprising:
detecting the error of the second computing node via a Java Management Extension monitor; and
reporting the error to the second computing node from the Java Management Extension monitor.

### Claim 19

A non-transitory computer readable medium comprising instructions operable within a clustered content management system that includes a content repository, wherein the instructions, when executed by a processor, are operable to direct the computing nodes to:
initiate synchronization of the content repository based on a change to an instance of the content repository by the first computing node;
determine, via the second computing node, that synchronization of the change with the content repository is blocked due to an error;
identify the error blocking the synchronization; and
correcting the error to synchronize the change with the content repository.

### Claim 20 (depends on 19)

The computer readable medium of claim 19, further comprising instructions that direct the second computing node to:
detect another error;
determine that the other error is not correctable; and
relinquish synchronization control of the content repository in response to detecting the other error is not correctable,
wherein the computer readable medium further comprises instructions that direct the first computing node and a third computing node in the content management system to:
detect that the second computing node is relinquishing the synchronization control of the content repository; and
determine which of the first and the third computing nodes takes the synchronization control of the content repository.

### Claim 21 (depends on 19)

The computer readable medium of claim 19, wherein:
the error is a storage space limit of the second computing node; and
the computer readable medium further comprises instructions that direct one or more of the computing nodes to delete one or more objects from the second computing node to increase available storage space and correct the error.

### Claim 22 (depends on 19)

The computer readable medium of claim 19, further comprising instructions that direct one or more of the computing nodes to:
start a timer when the second computing node determines that the error is with the second computing node; and
direct the second computing node to transfer synchronization control of the content repository to the first computing node if the error is not corrected upon expiration of the timer.

### Claim 23 (depends on 19)

The computer readable medium of claim 19, wherein:
the error is a network error that prevents the second computing node from communicating with the first computing node; and
the computer readable medium further comprises instructions that direct one or more of the computing nodes to reinitialize a network interface of the second computing node to correct the error.

### Claim 24 (depends on 19)

The computer readable medium of claim 19, wherein:
the content repository is a Java Content Repository.

### Claim 25 (depends on 19)

The computer readable medium of claim 19, the computer readable medium further comprises instructions that direct one or more of the computing nodes to:
detect the error of the second computing node via a Java Management Extension monitor.
