Methods and apparatus for remotely updating executing processes

• US 9,886,257 B1
• Filed: 04/21/2014
• Issued: 02/06/2018
• Est. Priority Date: 06/30/2011
• Status: Expired due to Fees

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Sorenson, III, James Christopher, Lin, Yun, Brugiolo, Ivan
• Primary Examiner(s): Baturay, Alicia
• Application Number:
  US14/257,696
• Time in Patent Office: 1,387 Days
• Field of Search: 709220
• CPC Class Codes: G06F 3/0607 by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device
• CPC Class Codes: G06F 3/0632 by initialisation or re-initialisation of storage systems
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

Methods, apparatus, and computer-accessible storage media for remotely updating an executing process that receives I/O requests on I/O port(s), stores write data to a write log on local storage, and uploads data from the write log to remote storage. An update for the process is detected and downloaded, and an updated process is instantiated from the update. The current process is directed to perform a shutdown for update during an update window. In response, the current process saves its current configuration, flushes an in-memory portion of the write log to local storage, and releases its I/O port(s). The updated process loads the saved configuration, detects that the port(s) have been released, and starts accepting I/O requests on the ports. During flushing, the current process flushes current data in memory while continuing to append new write data, stops accepting new write requests, and then flushes the new write data.

Claims

1. A system, comprising:

one or more processors; and

program instructions that are executable by the one or more processors to implement a storage gateway process on a computing device, the storage gateway process configured to;

perform storage gateway operations that include;

receive I/O requests including write requests from one or more client processes on a local network via one or more I/O ports,

append write data indicated by the write requests to an in-memory portion of a write log on a local data store, and

upload write data from the write log to a remote data store;

receive an indication that the storage gateway process is to shut down so that an updated storage gateway process can take over the storage gateway operations; and

in response to receipt of said indication;

persist a storage gateway configuration that includes an indication of the one or more I/O ports,

flush write data from the in-memory portion of the write log to the local data store, and

release the one or more I/O ports so that the updated storage gateway process can take over the storage gateway operations.

2. The system as recited in claim 1, wherein, to take over storage gateway operations from the storage gateway process, the updated storage gateway process is configured to detect that the one or more I/O ports have been released by the storage gateway process, open the one or more I/O ports, and receive and process I/O requests including write requests from the one or more client processes via the one or more I/O ports.

3. The system as recited in claim 1, wherein, to flush write data from the in-memory portion of the write log to the local data store, the storage gateway process is further configured to:

flush current write data in the in-memory portion of the write log to the local data store while accepting I/O requests including new write requests on the one or more I/O ports and append new write data indicated by the new write requests to the in-memory portion of the write log; and

after flush of the current write data in the in-memory portion of the write log to the local data store, flush the new write data in the in-memory portion of the write log to the local data store while rejecting subsequent write requests on the one or more I/O ports.

4. The system as recited in claim 3, wherein the storage gateway process is further configured to reply to each of the subsequent write requests to inform a respective client process to retry the write request.

5. The system as recited in claim 1, wherein the storage gateway process is further configured to persist the storage gateway configuration, flush the write data from the in-memory portion of the write log to the local data store, and release the one or more I/O ports during a specified update window.

6. The system as recited in claim 1, wherein the storage gateway process is further configurable to terminate subsequent to said releasing the one or more I/O ports.

7. The system as recited in claim 1, wherein the remote data store is maintained by a storage service on a remote network, wherein the storage gateway process is a version of a storage gateway that serves as an interface between the one or more client processes on the local network and the storage service on the remote network, and wherein the updated storage gateway process is a newer version of the storage gateway.

8. A computer-implemented method, comprising:

performing storage gateway operations that include;

receiving I/O requests including write requests from one or more client processes on a local network via one or more I/O ports,

appending write data indicated by the write requests to an in-memory portion of a write log on a local data store, and

uploading write data from the write log to a remote data store;

receiving an indication that a storage gateway process is to shut down so that an updated storage gateway process can take over the storage gateway operations; and

in response to receipt of said indication;

persisting a storage gateway configuration that includes an indication of the one or more I/O ports,

flushing write data from the in-memory portion of the write log to the local data store, and

releasing the one or more I/O ports so that the updated storage gateway process can take over the storage gateway operations.

9. The computer-implemented method as recited in claim 8, further comprising:

taking over, by the updated storage gateway process, storage gateway operations from the storage gateway process, wherein said taking over comprises;

detecting, by the updated storage gateway process, that the one or more I/O ports have been released by the storage gateway process,

opening, by the updated storage gateway process, the one or more I/O ports, and

receiving and processing, by the updated storage gateway process, I/O requests including write requests from the one or more client processes via the one or more I/O ports.

10. The computer-implemented method as recited in claim 8, wherein flushing write data from the in-memory portion of the write log to the local data store comprises:

flushing current write data in the in-memory portion of the write log to the local data store while accepting I/O requests including new write requests on the one or more I/O ports and appending new write data indicated by the new write requests to the in-memory portion of the write log; and

after flushing the current write data in the in-memory portion of the write log to the local data store, flushing the new write data in the in-memory portion of the write log to the local data store while rejecting subsequent write requests on the one or more I/O ports.

11. The computer-implemented method as recited in claim 10, further comprising replying, by the storage gateway process, to each of the subsequent write requests to inform a respective client process to retry the write request.

12. The computer-implemented method as recited in claim 8, further comprising persisting, by the storage gateway process, the storage gateway configuration, flushing the write data from the in-memory portion of the write log to the local data store, and releasing the one or more I/O ports during a specified update window.

13. The computer-implemented method as recited in claim 8, further comprising terminating the storage gateway process subsequent to said releasing the one or more I/O ports.

14. The computer-implemented method as recited in claim 8, wherein the remote data store is maintained by a storage service on a remote network, wherein the storage gateway process is a version of a storage gateway that serves as an interface between the one or more client processes on the local network and the storage service on the remote network, and wherein the updated storage gateway process is a newer version of the storage gateway.

15. A non-transitory computer-accessible storage medium storing program instructions that when executed by one or more processors implement:

a storage gateway process configured to;

perform storage gateway operations that include;

receiving I/O requests including write requests from one or more client processes on a local network via one or more I/O ports,

appending write data indicated by the write requests to an in-memory portion of a write log on a local data store, and

uploading write data from the write log to a remote data store;

receive an indication that the storage gateway process is to shut down so that an updated storage gateway process can take over the storage gateway operations; and

in response to receiving said indication;

persist a storage gateway configuration that includes an indication of the one or more I/O ports,

flush write data from the in-memory portion of the write log to the local data store, and

release the one or more I/O ports so that the updated storage gateway process can take over the storage gateway operations.

16. The non-transitory computer-accessible storage medium as recited in claim 15, wherein, to take over storage gateway operations from the storage gateway process, the updated storage gateway process is configured to detect that the one or more I/O ports have been released by the storage gateway process, open the one or more I/O ports, and receive and process I/O requests including write requests from the one or more client processes via the one or more I/O ports.

17. The non-transitory computer-accessible storage medium as recited in claim 15 wherein, to flush write data from the in-memory portion of the write log to the local data store, the storage gateway process is further configured to:

flush current write data in the in-memory portion of the write log to the local data store while accepting I/O requests including new write requests on the one or more I/O ports and appending new write data indicated by the new write requests to the in-memory portion of the write log; and

after flushing the current write data in the in-memory portion of the write log to the local data store, flush the new write data in the in-memory portion of the write log to the local data store while rejecting subsequent write requests on the one or more I/O ports.

18. The non-transitory computer-accessible storage medium as recited in claim 17, wherein the storage gateway process is further configured to reply to each of the subsequent write requests to inform a respective client process to retry the write request.

19. The non-transitory computer-accessible storage medium as recited in claim 15, wherein the storage gateway process is further configured to persist the storage gateway configuration, flush the write data from the in-memory portion of the write log to the local data store, and release the one or more I/O ports during a specified update window.

20. The non-transitory computer-accessible storage medium as recited in claim 15, wherein the storage gateway process is further configured to terminate subsequent to said releasing the one or more I/O ports.