GRID ORIENTED DISTRIBUTED PARALLEL COMPUTING PLATFORM

• US 20160034191A1
• Filed: 07/28/2015
• Published: 02/04/2016
• Est. Priority Date: 08/01/2014
• Status: Abandoned Application

• Current Assignee: Toshiba Memory Corporation (Kioxia Corporation)
• Original Assignee: Kabushiki Kaisha Toshiba (Toshiba Corporation)
• Inventors: KINOSHITA, Atsuhiro, RAM, Johri
• Application Number:
  US14/811,665
• Publication Number:
  US 20160034191A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/24532 of parallel queries
• CPC Class Codes: G06F 16/90339 by using parallel associative memories or content-addressable memories
• CPC Class Codes: G06F 3/061 Improving I/O performance
• CPC Class Codes: G06F 3/0635 by changing the path, e.g. traffic rerouting, path reconfiguration
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Abstract

A distributed computing system includes a group of interconnected memory nodes, where one of the memory nodes is configured as a transaction ID manager. The transaction ID manager is configured to manage concurrency of database transactions by issuing a transaction ID for each database transaction performed in the system. In some embodiments, each memory node in the two-dimensional matrix is configured as a transaction ID manager. In such embodiments, the unique transaction IDs generated by the transaction ID manager at each memory node are transmitted with node-specific information, so that the unique transaction IDs generated at each memory node are distinguished from the unique transaction IDs generated by other memory nodes.

Claims

1. A memory system comprising:

a plurality of memory nodes interconnected with each other; and

at least one connection server having an interface to a network switch and connected to the memory nodes,

wherein each of the memory nodes includes a non-volatile memory device and a node controller configured to communicate with node controllers of other nodes, and the node controller of at least one of the memory nodes includes a transaction ID generator configured to generate a unique transaction ID in response to a request for a transaction ID received from the connection server.

2. The memory system of claim 1, wherein the connection server is configured to transmit the request for the transaction ID to one of the plurality of memory nodes prior to issuing an IO command that includes the transaction ID in the IO command.

3. The memory system of claim 2, wherein the IO command includes one of a read command including an address from which data is to be read and a write command including data to be written and an address to which the data is to be written.

4. The memory system of claim 2, wherein each of the plurality of memory nodes includes a transaction ID generator configured to generate a unique transaction ID, independently with respect to other transaction ID generators, in response to the request for a transaction ID received from the connection server.

5. The memory system of claim 4, wherein the address from which data is to be read corresponds to the memory node that includes the transaction ID generator that generated the unique transaction ID and the address to which data is to be written corresponds to the memory node that includes the transaction ID generator that generated the unique transaction ID.

6. The memory system of claim 1, further comprising an additional connection server having an interface to the network switch and connected to the memory nodes.

7. The memory system of claim 6, wherein transaction ID generator is further configured to generate a unique transaction ID in response to a request for a transaction ID received from the additional connection server.

8. The memory system of claim 1, wherein the unique transaction ID comprises a sequentially issued number.

9. The memory system of claim 1, wherein each of the plurality of memory nodes includes a transaction ID generator configured to generate a unique transaction ID in response to the request for a transaction ID received from the connection server and the unique transaction ID comprises a sequentially issued number and a node ID of the memory node.

10. A method of processing a read request at a target memory node of a data storage device that includes at least one connection server and a plurality of memory nodes, including the target memory node, interconnected with each other and connected to the at least one connection server, the method comprising:

receiving a read command from a connection server that includes a transaction ID, an ID of a memory node, and a memory address from which data is to be read;

reading data stored at the memory address from the target memory node, if an ID of the target memory node matches the ID of the memory node included in the read command and a transaction ID associated with data stored in the memory address is less than the transaction ID included in the read command; and

transmitting from the target memory node to the connection server the data read from the memory address.

11. The method of claim 10, further comprising, if the transaction ID associated with data stored in the memory address is greater than the transaction ID included in the read command, determining that the read command is invalid with respect to data stored at the memory address.

12. The method of claim 10, further comprising determining whether a write command that includes the memory address is currently in progress and, if so, wherein reading data stored at the memory address comprises:

pausing the read command until the write command is completed; and

reading data that are stored at the memory address and have been written as a result of the write command.

13. The method of claim 10, further comprising, if the ID of the target memory node does not match the ID of the memory node included in the read command, routing the read command to a memory node that is adjacent to the target memory node.

14. The method of claim 10, wherein transmitting from the target memory node to the connection server the data read from the memory address comprises routing the data to the connection server via one or more of the plurality of memory nodes.

15. The method of claim 10, further comprising,

receiving a second read command, wherein the second read command is received from an additional connection server and includes a second transaction ID, a second ID of a memory node, and a second memory address from which data is to be read;

reading data stored at the second memory address from the target memory node, if an ID of the target memory node matches the second ID of the memory node and a transaction ID associated with data stored in the second memory address is less than the second transaction ID; and

transmitting from the target memory node to the additional connection server the data read from the second memory address.

16. A method of processing a write request at a target memory node of a data storage device that includes at least one connection server and a plurality of memory nodes, including the target memory node, interconnected with each other and connected to the at least one connection server, the method comprising:

receiving a write command from a connection server that includes data to be written, a transaction ID, an ID of a memory node, and a memory address to which the data are to be written; and

writing the data in the memory address, if an ID of the target memory node matches the ID of the memory node included in the write command and a transaction ID associated with data most recently stored in the memory address is less than the transaction ID included in the write command.

17. The method of claim 16, further comprising, if the transaction ID associated with data most recently stored in the memory address is greater than the transaction ID included in the write command, determining that the write command is invalid with respect to data stored at the memory address.

18. The method of claim 16, further comprising, if the ID of the target memory node does not match the ID of the memory node included in the write command, routing the write command to a memory node that is adjacent to the target memory node.

19. The method of claim 16, wherein writing the data in the memory address comprises replacing an oldest version of data stored in the target memory node at the memory address.

20. The method of claim 16, wherein receiving the write command from the connection server comprises receiving the write command routed from a memory node adjacent to the memory node receiving the write command.