Zone consistency
First Claim
Patent Images
1. A computer implemented method-comprising:
- creating strong consistency for a unique data object directly accessible by a client in both of two zones sharing a common file system namespace, each zone representing a different network partition;
wherein the unique data object appears to the client to be the same data object in each of the zones;
wherein the unique data object has a unique way to be accessed by the client within the file system namespace;
wherein strong consistency ensures that if the unique data object is accessed at either zone in the namespace, the data of the unique data object appears to the client to be the same across zones in the namespace whether the unique data object is accessed in a first zone of the two zones or a second zone of the two zones by switching between consistency techniques to keep the unique data object consistent between the two zones;
wherein direct read and write access by the client is enabled to the unique data object in each of the two zones;
wherein the consistency technique includes rules governing access to the unique data object across the two zones;
wherein the consistency techniques include application of synchronous and asynchronous copying of the unique data object from the first zone to the second zone;
wherein the consistency techniques include configuring each of the first zone and the second zone to send each other respective first and second periodic heartbeats, each respective periodic heartbeat configured to ensure its respective recipient zone that the respective sender of the respective periodic heartbeat knows that there has not been a network partition between the first and second zones, wherein the first and second respective zones are each assured that each has the latest data as long as each is receiving its respective heartbeat from the other zone; and
wherein different techniques are applied to each of the unique data objects being synchronized based on the number of read and write requests to the each object at each zone; and
determining, based on the consistency techniques, including at least the first and second heartbeats, and in response to a read request to a specified zone, whether the unique data object in the specified zone has the most up to date information; and
if the specified zone is determined to have the most up to date information, then servicing the read request; and
if the specified zone is determined not to have the most up to date information, at least one of redirecting the read request to another zone or failing the read request.
9 Assignments
0 Petitions
Accused Products
Abstract
A computer implemented method, system, and computer program product for enabling strong consistency of unique objects between zones comprising enabling consistency of an unique data object between in zones by switching between consistency techniques to keep the unique data object consistent between the zones; wherein read and write access is enabled to the unique object in the zones.
-
Citations
20 Claims
-
1. A computer implemented method-comprising:
-
creating strong consistency for a unique data object directly accessible by a client in both of two zones sharing a common file system namespace, each zone representing a different network partition;
wherein the unique data object appears to the client to be the same data object in each of the zones;
wherein the unique data object has a unique way to be accessed by the client within the file system namespace;
wherein strong consistency ensures that if the unique data object is accessed at either zone in the namespace, the data of the unique data object appears to the client to be the same across zones in the namespace whether the unique data object is accessed in a first zone of the two zones or a second zone of the two zones by switching between consistency techniques to keep the unique data object consistent between the two zones;
wherein direct read and write access by the client is enabled to the unique data object in each of the two zones;
wherein the consistency technique includes rules governing access to the unique data object across the two zones;
wherein the consistency techniques include application of synchronous and asynchronous copying of the unique data object from the first zone to the second zone;
wherein the consistency techniques include configuring each of the first zone and the second zone to send each other respective first and second periodic heartbeats, each respective periodic heartbeat configured to ensure its respective recipient zone that the respective sender of the respective periodic heartbeat knows that there has not been a network partition between the first and second zones, wherein the first and second respective zones are each assured that each has the latest data as long as each is receiving its respective heartbeat from the other zone; and
wherein different techniques are applied to each of the unique data objects being synchronized based on the number of read and write requests to the each object at each zone; anddetermining, based on the consistency techniques, including at least the first and second heartbeats, and in response to a read request to a specified zone, whether the unique data object in the specified zone has the most up to date information; and if the specified zone is determined to have the most up to date information, then servicing the read request; and if the specified zone is determined not to have the most up to date information, at least one of redirecting the read request to another zone or failing the read request. - View Dependent Claims (2, 3, 12, 17, 18, 19, 20)
-
-
4. A system comprising:
-
one or more processors; zones, including a different storage device at each zone of the zones; a unique data object stored in the zones; and computer-executable program code operating in memory, wherein the computer-executable program code is configured to cause the one or more processors to execute; creating strong consistency for the unique data object directly accessible by a client in both of two zones in a file system namespace;
wherein the unique data object appears to be the same data object in each of the zones;
wherein the unique data object has a unique way to be accessed by the client within the file system namespace;
wherein strong consistency ensures that if the unique data object is accessed at either zone in the file system namespace, the data of the unique data object appears to be the same across zones in the namespace whether the unique object is accessed in a first zone of the two zones or a second zone of the two zones by switching between consistency techniques to keep the unique data object consistent between the two zones;
wherein direct read and write access by the client is enabled to the unique data object in each of the two zones;
wherein the consistency technique includes rules governing access to the unique data object across the two zones;
wherein the consistency techniques include application of synchronous and asynchronous copying of the unique data object from the first zone to the second zone;
wherein the consistency techniques include configuring the first zone and the second zone to each send each other respective first and second periodic heartbeats, each respective periodic heartbeat configured to ensure that each of the first and second zones knows that there has not been a network partition between the first and second zones and that the respective zone is assured that it has the latest data as long as it is receiving its respective heartbeat from the other zone; and
wherein different techniques are applied to each of the unique data objects being synchronized based on the number of read and write requests to the each data object at each zone;wherein the computer-executable program code further enables one or more processors to execute; determining, based on the consistency techniques, including at least the first and second heartbeats, and in response to a read request to a specified zone, whether the unique data object in the specified zone has the most up to date information; if the specified zone is determined to have the most up to date information, then servicing the read request; and if the specified zone is determined not to have the most up to date information, at least one of redirecting the read request to another zone or failing the read request. - View Dependent Claims (5, 6, 13, 14, 15)
-
-
7. A computer program product comprising:
-
a non-transitory computer-readable storage medium encoded with computer-executable program code enabling one or more processors to execute; creating strong consistency for a unique data object accessible by a client in both of two zones in a file system namespace;
wherein the unique data object appears to be the same data object in each of the zones;
wherein the unique data object has a unique way to be accessed within the file system namespace;
wherein strong consistency ensures that if the unique data object is accessed at either zone in the namespace, the data of the unique data object appears to be the same across zones in the file system namespace whether the unique data object is accessed in a first zone of the two zones or a second zone of the two zones by switching between consistency techniques to keep the unique data object consistent between the two zones;
wherein direct read and write access by the client is enabled to the unique data object in each of the two zones;
wherein the consistency technique includes rules governing access to the unique data object;
wherein the consistency techniques include application of synchronous and asynchronous copying of the unique data object from the first zone to the second zone;
wherein the consistency techniques include configuring the first zone and the second zone to each send each other respective first and second periodic heartbeats, each respective periodic heartbeat configured to ensure that each of the first and second zones knows that there has not been a network partition between the first and second zones and that the respective zone is assured that it has the latest data as long as it is receiving its respective heartbeat from the other zone; and
wherein different techniques are applied to each of the unique data objects being synchronized based on the number of read and write requests to the each data object at each zone;determining, based on the consistency techniques, including at least the first and second heartbeats, and in response to a read request to a specified zone, whether the unique data object in the specified zone has the most up to date information; if the specified zone is determined to have the most up to date information, then servicing the read request; if the specified zone is determined not to have the most up to date information, at least one of redirecting the read request to another zone or failing the read request. - View Dependent Claims (8, 9, 10, 11, 16)
-
Specification