ADAPTIVE FILE PLACEMENT IN A DISTRIBUTED FILE SYSTEM

• US 20090307329A1
• Filed: 06/06/2008
• Published: 12/10/2009
• Est. Priority Date: 06/06/2008
• Status: Abandoned Application

• Current Assignee: Oath Inc. (Verizon Communications Inc.)
• Original Assignee: Oath Inc. (Verizon Communications Inc.)
• Inventors: Silberstein, Adam, Reed, Benjamin, OLSTON, CHRIS
• Application Number:
  US12/135,095
• Publication Number:
  US 20090307329A1
• Time in Patent Office: Days
• US Class Current: 709/214
• CPC Class Codes: G06F 16/184 implemented as replicated file system

Abstract

In a distributed system that includes multiple machines, a scheduler attempts to schedule a task on a machine that is not currently overloaded with work. If a task is scheduled on a machine that does not yet have copies of the portions of the data set on which the task needs to operate, then that machine obtains copies of those portions from other machines that already have them. Whenever a “source” machine ships a copy of a portion to another “destination” machine in the distributed system, the destination machine persistently stores that copy on the destination machine'"'"'s persistent storage mechanism. The copy also remains on the source machine. Thus, portions of the data set are automatically replicated whenever those portions are shipped between machines of the distributed system. Each machine in the distributed system has access to “global” information that indicates which machines have which portions of the data set.

Claims

1. A computer-implemented method of peer-to-peer caching, the method comprising:

requesting, at a first storage device, a copy of a file that is stored on a second storage device but not the first storage device;

receiving the copy of the file at the first storage device from the second storage device in response to said requesting;

storing the copy of the file on the first storage device; and

publishing, to a metadata server that is separate from a machine that controls the first storage device, information that indicates that the copy of the file is available on the first storage device.

2. The method of claim 1, further comprising:

determining whether user-specified criteria associated with the file are satisfied; and

after the first storage device receives the copy of the file from the second storage device, persistently storing a non-volatile copy of the file on the second storage device only in response to determining that the user-specified criteria associated with the file are satisfied.

3. The method of claim 1, wherein publishing the information comprises sending, over a network, to the metadata server, which is accessible by both (a) a machine that controls the first storage device and (b) a machine that controls the second storage device, information that indicates that the copy of the file is stored on the second storage device.

4. The method of claim 1, wherein publishing the information comprises sending information over a network to the metadata server, which will (a) store the information in response to receiving the information and (b) make the stored information available to two or more separate machines other than the metadata server.

5. The method of claim 1, further comprising:

receiving a task at a first machine that controls the first storage device;

wherein the task needs to perform at least one operation on the file;

in response to receiving the task, determining, at the first machine, that no copy of the file is currently stored on the first storage device;

wherein the step of requesting the copy of the file from the second storage device is performed in response to the determining, at the first machine, that no copy of the file is currently stored on the first storage device.

6. The method of claim 5, further comprising:

in response to determining, at the first machine, that no copy of the file is currently stored on the first storage device, sending to the metadata server a request for particular information that indicates a set of machines on which a copy of the file is currently stored; and

receiving, from the metadata server, particular information that indicates the set of machines on which a copy of the files is currently stored;

wherein the set of machines includes a machine that controls the second storage device.

7. The method of claim 5, wherein the step of receiving the task at the first machine comprises receiving the task from a task scheduling mechanism that selected the first machine to perform the task due at least in part to the first machine having less than a threshold amount of work to do, even though the first storage device did not store any copy of the file at a time that the task scheduling mechanism selected the first machine to perform the task.

8. The method of claim 1, further comprising:

determining that the first storage device is filled beyond a threshold level of the first storage device'"'"'s capacity;

in response to determining that the first storage device is filled beyond the threshold level, selecting, for eviction, one or more files that are stored on the first storage device; and

deleting, from the first storage device, the one or more files that were selected for eviction.

9. The method of claim 8, wherein the step of selecting the one or more files for eviction comprises:

determining a separate utility measure for each file that is stored on the first storage device; and

selecting, from among the files that are stored on the first storage device, one or more files that are associated with lowest utility measures of utility measures that are associated with the files that are stored on the first storage device;

wherein, for each particular file that is stored on the first storage device, the utility measure associated with that particular file is determined based at least in part on (a) an amount of time that has passed since the particular file was last accessed and (b) a number of times that the particular file was accessed.

10. The method of claim 8, wherein the step of selecting the one or more files for eviction comprises:

determining, for a particular file that is stored on the first storage device, a number of copies of the particular file are currently stored among a plurality of storage devices that includes the first storage device;

determining a specified minimum number of copies of the particular file that are required to be stored among the plurality of storage devices at all times;

determining whether the number of copies of the particular file that are currently stored among the plurality of storage devices is greater than the specified minimum number of copies; and

in response to determining that the number of copies of the particular file that are currently stored among the plurality of storage devices is greater than the specified minimum number of copies, selecting only files other the particular file for eviction from the first storage device.

11. The method of claim 1, further comprising:

in response to an operation being performed on a first file that is stored on the first storage device, incrementing a utility measure that is associated with the first file; and

in response to a specified amount of time passing since the first file was last accessed, decrementing the utility measure that is associated with the first file.

12. A volatile or non-volatile computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, cause the one or more processors to perform the steps recited in claim 1.

13. A volatile or non-volatile computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, cause the one or more processors to perform the steps recited in claim 2.

14. A volatile or non-volatile computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, cause the one or more processors to perform the steps recited in claim 3.

15. A volatile or non-volatile computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, cause the one or more processors to perform the steps recited in claim 4.

16. A volatile or non-volatile computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, cause the one or more processors to perform the steps recited in claim 5.

17. A volatile or non-volatile computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, cause the one or more processors to perform the steps recited in claim 6.

18. A volatile or non-volatile computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, cause the one or more processors to perform the steps recited in claim 7.

19. A volatile or non-volatile computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, cause the one or more processors to perform the steps recited in claim 8.

20. A volatile or non-volatile computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, cause the one or more processors to perform the steps recited in claim 9.

21. A volatile or non-volatile computer-readable storage medium carrying one or more sequences of instructions which, when executed by one or more processors, cause the one or more processors to perform the steps recited in claim 10.