Fast boot
摘要
說(shuō)明書(shū)
In the above example, node N0 first performed a remote read request at 1612 and then subsequently performed a local write at 1614. If it is known ahead of time that the page on node N0 was to be marked exclusive (e.g., similar to a remote write request), the step of sending the page p to the NAM from node N2 in 1612 may be skipped.
Now suppose at 1616 that N1 attempts to perform a local read of page p. However, its copy of page p is invalid. Node N1 then requests the page p from node N0. In response to the remote read request, node N0 transitions its copy of page p to secondary (or in some embodiments invalidates its exclusive copy of page p if the requestor is expected to write into p), and sends page p to node N1. Node N1 marks its received copy of page p as primary. Node N0 also sends a copy of page p to the NAM, which marks its copy of page p as valid and secondary.
As shown in the example above, a page may be in different states on different nodes of a TidalPod. In some embodiments, a parallel data structure is used to maintain the metadata about the state of pages on various nodes in the TidalPod. In some embodiments, the structure is maintained such that re-computation of the state of pages across nodes in the TidalPod need not be performed.
In this example embodiment, the NAM is passive, and is not configured to request pages and write into them. The NAM, over time, builds up a set of secondary pages. If a node attempts to write into a page, the copy on the NAM becomes invalid.
該功能需要專(zhuān)業(yè)版企業(yè)版VIP權(quán)限，您可以：
掃描加專(zhuān)利匯官方微信交流群
