Using log objects in object storage for durability of file objects in volatile memory

A system, comprising:

• one or more processors;
• and
• one or more memories, wherein the one or more memories have stored thereon instructions, which when executed by the one or more processors to implement a file-object manager, wherein the file-object manager is configured to:
• determine that one or more eviction criteria are met to evict a file object in a file object construction buffer in a volatile system memory, wherein the file object corresponds to a file;
• in response to the determination that the one or more eviction criteria are met, call an object storage interface to store, via an application-level network protocol, the file object into a file object store in an object storage system;
• and
• in response to a reboot, power failure, or other event that results in loss of content stored in the volatile system memory:
• call the object storage interface to retrieve, via the application-level network protocol, log objects from a file system log of the object storage system;
• and
• replay file system operations indicated by the log objects in a same sequential order that the file system operations were previously applied for one or more file objects in the volatile system memory to restore the one or more file objects in the volatile system memory.

A method, comprising:

• performing, by a file-object manager implemented on one or more computing devices:
• determining that one or more eviction criteria are met to evict a file object in a file object construction buffer in a volatile system memory, wherein the file object corresponds to a file;
• in response to determining that the one or more eviction criteria are met, calling an object storage interface to store, via an application-level network protocol, the file object into a file object store in an object storage system;
• and
• in response to a reboot, power failure, or other event that results in loss of content stored in the volatile system memory:
• calling the object storage interface to retrieve, via the application-level network protocol, log objects from a file system log of the object storage system;
• and
• replaying file system operations indicated by the log objects in a same sequential order that the file system operations were previously applied for one or more file objects in the volatile system memory to restore the one or more file objects in the volatile system memory.

One or more non-transitory computer-accessible storage media storing program instructions that when executed on or across one or more processors cause the one or more processors to implement a file-object manager to:

• determine that one or more eviction criteria are met to evict a file object in a file object construction buffer in a volatile system memory, wherein the file object corresponds to a file;
• in response the determination that the one or more eviction criteria are met, call an object storage interface to store, via an application-level network protocol, the file object into a file object store in an object storage system;
• and
• in response to a reboot, power failure, or other event that results in loss of content stored in the volatile system memory:
• call the object storage interface to retrieve, via the application-level network protocol, log objects from a file system log of the object storage system;
• and
• replay file system operations indicated by the log objects in a same sequential order that the file system operations were previously applied for one or more file objects in the volatile system memory to restore the one or more file objects in the volatile system memory.