Web server content replication

• US 8,108,347 B2
• Filed: 08/05/2005
• Issued: 01/31/2012
• Est. Priority Date: 05/29/1998
• Status: Expired due to Fees

• Current Assignee: R2 Solutions LLC (Acacia Research Corporation)
• Original Assignee: Yahoo! Inc. (Apollo Global Management, Inc.)
• Inventors: Lara, Marco, Yamane, Stanley, DeBettencourt, Jason
• Primary Examiner(s): Perveen, Rehana
• Assistant Examiner(s): Hoffler, Raheem
• Application Number:
  US11/198,923
• Publication Number:
  US 20060031188A1
• Time in Patent Office: 2,370 Days
• Field of Search: None
• US Class Current: 707/638
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: 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
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 16/1734 Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
• CPC Class Codes: G06F 16/1844 Management specifically adapted to replicated file systems
• CPC Class Codes: G06F 16/1873 Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06F 2201/875 Monitoring of systems including the internet
• CPC Class Codes: G06F 2201/88 Monitoring involving counting
• CPC Class Codes: H04L 41/024 using relational databases for representation of network management data, e.g. managing via structured query language [SQL]
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 41/0896 Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76
• CPC Class Codes: H04L 41/5083 wherein the managed service relates to web hosting
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1027 Persistence of sessions during load balancing
• CPC Class Codes: H04L 67/1029 : using data related to the state of servers by a load balancer
• CPC Class Codes: H04L 67/1031 : Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
• CPC Class Codes: H04L 67/1034 : Reaction to server failures by a load balancer
• CPC Class Codes: H04L 67/1095 : Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/56 : Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/563 : Data redirection of data network streams
• CPC Class Codes: H04L 67/564 : Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/5682 : Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: Y10S 707/99952 : Coherency, e.g. same view to multiple users

Abstract

This invention relates to managing multiple web servers, and more particularly to a web service system and method that allows a system operator to distribute content to each web server in the web service system. In one embodiment, a method for replicating changes in a source file set on a destination file system includes identifying changes in a source file set, storing the identified changes in a modification list, and transmitting the modification list to an agent having access to a destination file system. In another embodiment, a method for replicating changes in a source file set on a destination file system includes identifying changes in a source file set, storing the identified changes in a modification list, and transmitting the modification list to a plurality of web servers. In another embodiment, a web service system includes a manager for managing the web service system, a host comprising a web server for receiving web page requests and an agent in communication with the manager, and a content distributor for providing content changes to the host. In another embodiment, a content distributor includes an identification module for identifying changes in a source file set, a modification list for storing identified changes, and a transmitter for transmitting the modification list to an agent having access to a destination file system.

Claims

1. A method comprising:

(a) identifying changes, by a content distributor, in a master source file set on a master computer of a destination file system on one or more hosts, the destination file system for access by a respective web server in each of the hosts;

the identifying step comprising the steps of;

inspecting a current version of the master source file set, and

comparing the current version to a previous version of the master source file set on the master computer;

(b) storing the identified changes, by the content distributor, in a first manifest, wherein the first manifest identifies at least one changed file and at least one change made to the at least one file;

(c) transmitting the first manifest and a copy of the changed file of the master source file set, by the content distributor, to a respective agent at each respective host in communication with a respective one of the web servers running in the same host, thereby notifying each of the web servers that the master source file set had changed, the agents having access to the destination file systems at the corresponding hosts;

(d) waiting until a predetermined non-zero number of the agents determine that their respective web servers are able to receive the identified changes before transmitting the identified changes to the agents; and

(e) receiving, a response from at least one of the agents after step (d) indicating that the destination file system installed the identified changes.

2. The method of claim 1 wherein the identifying step comprises the steps of:

installing a device driver to perform file operations and monitor changes to the master source file set; and

recording, by the device driver, changes to the master source file set.

3. The method of claim 1 wherein the identifying step comprises:

receiving a second manifest describing changes to the master source file set.

4. The method of claim 1 wherein the comparing step comprises comparing a file attribute of the file of the current version of the master source file set to a file attribute of a file of the previous version of the master source file set.

5. The method of claim 4 wherein the file attribute comprises at least one attribute from the group consisting of file size, file permissions, file ownership, modification time, and a hash of the file.

6. The method of claim 1, further comprising, before the identifying step, the step of calling a script of user configurable instructions by calling an operating system function.

7. The method of claim 1, further comprising, before the transmitting step, the step of calling a script of user configurable instructions by calling an operating system function.

8. The method of claim 1, further comprising, after the transmitting step, the step of calling a script of user configurable instructions by calling an operating system function.

9. The method of claim 8, further comprising the step of determining whether the transmitting step has successfully completed, and wherein the calling step occurs after the determining step.

10. The method of claim 8, wherein the step of calling a script occurs after the success of the transmission is known.

11. The method of claim 1 wherein the transmitting step comprises multicasting.

16. The method of claim 4 wherein the file attribute is stored in a list of file attributes.

12. Apparatus for web servicing, comprising:

a manager for managing the web service system;

a computer having one or more hosts, each host comprising a web server for receiving web page requests and an agent in communication with the manager and the web server; and

a content distributor in communication with the hosts and the manager, the content distributor providing notification of changes to a master source file set on a master computer to the hosts, the content distributor waiting until a predetermined non-zero number of the agents determine that their respective web servers are able to receive the identified changes before transmitting the identified changes to the agents, and the content distributor receiving a response indicating that the identified changes are installed,

the content distributor comprising;

(a) an identification module for identifying changes in the master source file set on a master computer by inspecting a current version of the master source file set and comparing the current version to a previous version of the master source file set on the master computer;

(b) a manifest for storing identified changes to the master source file set, wherein the manifest identifies at least one changed file and at least one change made to the at least one file;

(c) a transmitter for transmitting the manifest and a copy of the changed file of the master source file set to an agent, the agent having access to a destination file system; and

(d) a receiver for receiving a response indicating that the destination file system received the identified changes.

13. The system of claim 12, further comprising a traffic manager in communication with the manager, the traffic manager for directing web page requests to the web server.

14. The system of claim 12, wherein the agent comprises an installer for installing a copy of a changed file on the master source file set on the destination file system.

15. Apparatus for content distribution, comprising:

(a) a master computer for storing at least one master file set;

(b) an identification module coupled to the master computer, and which identifies changes in the master source file set and stores the changes into a manifest, wherein the manifest identifies a least one changed file and at least one change made to the at least one file, wherein the identification module inspects a current version of the master source file set and compares the current version to a previous version of the master source file set on the master computer;

(c) a transmitter coupled to the master computer and the identification module, and which transmits the manifest and a copy of the at least one changed file of the master source file set to one or more agents in communication with the master computer, the agents having access to the destination file system, the transmitter waiting until a predetermined non-zero number of the agents determine that their respective web servers are able to receive the identified changes before transmitting the identified changes to the agents; and

(d) a receiver coupled to the computer, and which receives a response from the agents after the manifest in transmitted, the response indicating that the destination file system received the identified changes.