US8769208B2 - Method, system and server of removing a distributed caching object - Google Patents

Method, system and server of removing a distributed caching object Download PDF

Info

Publication number
US8769208B2
US8769208B2 US13/320,509 US201113320509A US8769208B2 US 8769208 B2 US8769208 B2 US 8769208B2 US 201113320509 A US201113320509 A US 201113320509A US 8769208 B2 US8769208 B2 US 8769208B2
Authority
US
United States
Prior art keywords
cache server
server
present
status
removal
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
US13/320,509
Other languages
English (en)
Other versions
US20130145099A1 (en
Inventor
Gang Liu
Qing Ren
Wensong Zhang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Assigned to ALIBABA GROUP HOLDING LIMITED reassignment ALIBABA GROUP HOLDING LIMITED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: LIU, GANG, REN, Qing, ZHANG, WENSONG
Publication of US20130145099A1 publication Critical patent/US20130145099A1/en
Priority to US14/266,549 priority Critical patent/US8838904B2/en
Application granted granted Critical
Publication of US8769208B2 publication Critical patent/US8769208B2/en
Priority to US14/468,774 priority patent/US8935482B2/en
Priority to US14/562,224 priority patent/US9047224B2/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02—Addressing or allocation; Relocation
    • G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
    • G06F12/12—Replacement control
    • G06F12/121—Replacement control using replacement algorithms
    • G06F12/122—Replacement control using replacement algorithms of the least frequently used [LFU] type, e.g. with individual count value
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02—Addressing or allocation; Relocation
    • G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
    • G06F12/12—Replacement control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • H04L67/5682—Policies or rules for updating, deleting or replacing the stored data

Definitions

  • the present disclosure relates to the field of network technology, and particularly, relates to methods, systems and servers of removing a distributed caching object.
  • a large-scale website system usually stores and retrieves data through a distributed cache structure.
  • the taobao website i.e., tabao.com
  • a distributed cache system includes a source data server, multiple cache servers which communicate with the source data server, and a dispatcher. Responsive to a user's request, the distributed cache system generally uses the dispatcher to determine which cache server the user may obtain data through a consistent Hashing algorithm that is based on the received user's request. If the cache server so determined has the data, the determined cache server returns the data to the dispatcher. If the determined cache server does not have the data, the determined cache server requests the data from the source data server, stores the data therein, and returns the data to the dispatcher which returns the data to the user.
  • an existing distributed cache system such as an image system of taobao website
  • a malicious image e.g., an infringing image or an illegal image
  • the image is first uploaded to a source image server.
  • a network user accesses the malicious image through a link of taobao network
  • he/she first accesses a certain image cache server that is determined based on the consistent Hashing algorithm. If that image cache server does not have the malicious image, the image cache server obtains the malicious image from the source image server and stores the malicious image.
  • the system will need to remove this malicious image.
  • Existing technology performs removal operations for that malicious image in the source image server and all the image cache servers of the distributed cache system.
  • Exemplary embodiments of the present disclosure aim to provide methods, systems and servers of removing a distributed caching object in order to solve the problem that exists in existing technology which requires to perform removal operations in all distributed cache servers and hence wastes resources of the servers and reduces the overall system performance.
  • the exemplary embodiments provide a method of removing a distributed caching object, which is implemented as follows.
  • the method of removing a distributed caching object may include receiving a removal request.
  • the removal request may include an identifier of an object.
  • the method may apply consistent Hashing, for example, to the identifier of the object to obtain a Hash result value of the identifier. Based on the Hash result value, the method may locate a corresponding cache server. In one embodiment, the method may render the corresponding cache server to be a present cache server. In some embodiments, the method may determine whether the present cache server is in an active status and has an active period greater or longer than an expiration period associated with the object. In response to determining that the present cache server is in an active status and has an active period longer than the expiration period associated with the object, the method may remove the object from the present cache server.
  • the exemplary embodiments further provide a system of removing a distributed caching object, which is implemented as follows.
  • the system of removing a distributed cache object may include a removal server and multiple cache servers.
  • the multiple cache servers may be configured to cache objects that are accessed by users.
  • the removal server may be configured to receive a removal request.
  • the removal request may include an identifier of an object.
  • the removal server may further be configured to apply consistent Hashing to the identifier of the object to obtain a Hash result value of the identifier.
  • the removal server may locate a corresponding cache server based on the Hash result value and render the corresponding cache server to be a present cache server.
  • the removal server may determine whether the present cache server is in an active status and has an active period greater than an expiration period associated with the object. In response to determining that the present cache server is in an active status and has an active period greater than the expiration period associated with the object, the removal server may remove the object from the present cache server.
  • the exemplary embodiments provide a removal server, which is implemented as follows.
  • the removal server may include a receiving unit.
  • the receiving unit may be configured to receive a removal request, where the removal request may include an identifier of an object.
  • the removal server may further include a computation unit that is configured to apply consistent Hashing to the identifier of the object to obtain a Hash result value of the identifier.
  • the removal server may further include a locating unit which is configured to locate a corresponding cache server based on the Hash result value and render the corresponding cache server to be a present cache server.
  • the removal server may include a determination unit configured to determine whether the present cache server is in an active status and has an active period greater than an expiration period associated with the object.
  • the removal server may further include a removal unit configured to remove the object from the present cache server in response to determining that the present cache server is in an active status and has an active period greater than the expiration period associated with the object.
  • the exemplary embodiments of the present disclosure receive a removal request which includes an identifier of an object, apply consistent Hashing to the identifier of the object to obtain a Hash result value of the identifier, locate a corresponding cache server based on the Hash result value, render the corresponding cache server to be a present cache server, determine whether the present cache server is in an active status and has an active period greater than an expiration period associated with the object, and remove the object from the present cache server in response to determining that the present cache server is in an active status and has an active period greater than the expiration period associated with the object.
  • the exemplary embodiments of the present disclosure therefore do not need to perform removal operations in all cache servers.
  • the exemplary embodiments precisely locate a cache server that includes the object to be removed and perform a removal operation, thus saving the other cache servers from wasting resources to perform removal operations and hence improving the overall performance of the distributed cache system.
  • FIG. 1 shows a schematic diagram illustrating a consistent Hashing ring in accordance with an embodiment of the present disclosure.
  • FIG. 2 shows a flowchart illustrating a first exemplary method of removing a distributed caching object.
  • FIG. 3 shows a flowchart illustrating a second exemplary method of removing a distributed caching object.
  • FIG. 4 shows a diagram illustrating a system structure implementing the exemplary method of removing a distributed caching object.
  • FIG. 5 shows a process of removing an object using the system structure described in FIG. 4 .
  • FIG. 6 shows a schematic diagram illustrating an example use of a consistent Hashing ring in accordance with an embodiment of the present disclosure.
  • FIG. 7 shows a block diagram illustrating an exemplary system of removing a distributed caching object.
  • FIG. 8 shows a block diagram illustrating a first removal server.
  • FIG. 9 shows a block diagram illustrating a second removal server.
  • FIG. 10 shows the exemplary removal server described in FIG. 8-9 in more detail.
  • the exemplary embodiments of the present disclosure provide methods, systems and servers of removing a distributed caching object.
  • an object removed in a distributed cache system is an object that has been stored in a distributed cache server of the system. Therefore, how an existing system stores and retrieves an object in a distributed cache server is described first with reference to the consistent Hashing algorithm.
  • cache servers are arranged in a 0-232 ring based on respective Hash values computed from the consistent Hashing algorithm.
  • the Hash value is obtained by applying a selected Hash function to an IP address of the cache server.
  • the Hash value is a 32-digit integer.
  • the cache server is mapped correspondingly onto a position in the ring based on the value of the integer.
  • FIG. 1 shows an example of a 0-2 32 ring.
  • the four cache servers namely, cache server 1, cache server 2, cache server 3 and cache server 4 which are arranged in a clockwise direction, are mapped onto the ring based on respective Hash values as shown in FIG. 1 .
  • a Hash calculation is applied to the object (generally, applying a Hash calculation to an identifier of the object, URL).
  • the obtained Hash value is used as a key and is mapped correspondingly onto a position in the 0-2 32 ring based on the value of the key.
  • the position of the key is used as an initial position to find a first cache server on the ring in a clockwise direction.
  • the user accesses the object through the first cache server so found. If the first cache server that is found through this clockwise search is unavailable (for example, down or crashed), the clockwise search continues until an available cache server is found. If the object which the user wants to access exists in that available cache server, the object is returned to the user through a dispatcher. If the object which the user wants to access does not exist in that available cache server, that cache server requests the object from a source data server, stores the object therein, and returns the object to the dispatcher which returns the object to the user.
  • Each object stored in a cache server has an expiration period.
  • the cache server removes the object automatically. Thereafter, if a user wants to access the object again through the cache server, the cache server may obtain the object from the source data server again and repeat the aforementioned process.
  • FIG. 2 shows a flowchart illustrating a first exemplary method of removing a distributed caching object. This embodiment shows a process of removing an object when an active period of a located cache server is greater than an expiration period of the object.
  • the method receives a removal request.
  • the removal request includes an identifier of an object to be removed.
  • the object refers to a network resource such as an image, audio, video, etc.
  • Each particular network resource is positioned through a URL (Universal Resource Locator).
  • the method applies Hashing to the identifier of the object to obtain a Hash result value of the identifier.
  • this block corresponds to a process of applying consistent Hashing to an identifier of an object to obtain a Hash result value.
  • the Hashing is consistent with a computation process that is implemented in existing technologies for storing and retrieving an object. This block therefore is not redundantly described herein.
  • the method locates a corresponding cache server based on the Hash result value and renders the corresponding cache server to be a present cache server.
  • the Hash result value may be used as a key to be mapped onto a corresponding position of the consistent Hashing ring, and a search may be performed in a clockwise direction to find a first cache server, starting from that position. Because the first cache server so found is the cache server that was dispatched when a user accessed the object, the first cache server has cached the object to be removed (given that the first cache server is in an active status, the object has been accessed by a user and an expiration period of the object has not been exceeded yet).
  • the method determines whether the present cache server is in an active status and has an active period greater than an expiration period of the object.
  • the method removes the object from the present cache server in response to determining that the present cache server is in an active status and has an active period greater than the expiration period of the object.
  • An active period refers to a time duration during which the cache server is in an active status.
  • an operation of removing the URL needs to be performed only in the located first cache server. It is because this cache server is presently active and all requests for accessing the object have been sent to this cache server. Even if the object exists in other cache servers, the object is automatically removed as the time duration of the object exceeds the expiration period of the object.
  • FIG. 3 shows a flowchart illustrating a second exemplary method of removing a distributed cache object. This embodiment shows in detail about a process of removing an object based on an active status and a status history of a located cache server.
  • the method sets up a status table of cache servers in advance, and stores a time stamp of the last status change of each cache server and a current status of each cache server in the status table.
  • This exemplary embodiment sets up a status table for cache servers.
  • Each entry of the status table is used for recording a time stamp of the last status change of a cache server and a current status of the cache server.
  • a time duration for the current status of the cache server may be determined based on this time stamp.
  • a current status may include an active status or an inactive status, with the inactive status usually indicating that the cache server is down.
  • the method receives a removal request, where the removal request includes an identifier of an object.
  • the method applies consistent Hashing to the identifier of the object to obtain a Hash result value of the identifier.
  • the method locates a corresponding cache server based on the Hash result value and renders the corresponding cache server as a present cache server.
  • the method determines whether the present cache server is in an active status. If affirmative, the method goes to block 306 ; otherwise the method goes to block 309 .
  • the method determines whether an active period of the present cache server is greater than an expiration period of the object. If affirmative, the method goes to block 307 ; otherwise the method goes to block 308 .
  • the method removes the object from the present cache server and ends the present process.
  • the present cache server that is found from the status table is in an active status and has an active period greater than an expiration period of the object, an operation of removing the URL needs to be performed only in the located first cache server. It is because that cache server is presently active and all requests for accessing the object have been sent to that cache server. Even if the object exists in other cache servers, the object is automatically removed as the time duration of the object exceeds the expiration period of the object.
  • the method removes the object from the present cache server, shifts from the present cache server to a next cache server, and renders the next cache server as the present cache server.
  • the process returns to block 305 .
  • the object is removed from the cache server first. Thereafter, upon consideration that the cache server was in an inactive status prior to the active status and a request for accessing the object to be removed may have been transferred to a next cache server (which is next to the present cache server on the consistent Hashing ring) during the time when the present cache server was in an inactive status, the next cache server may have cached that object and is therefore needed to be obtained and rendered as the present cache server for determining corresponding status again. The method returns to block 305 .
  • the method determines whether an inactive period of the present cache server is greater than the expiration period of the object. If affirmative, the method goes to block 310 ; otherwise the method goes to block 311 .
  • the method shifts from the present cache server to a next cache server and renders the next cache server as the present cache server.
  • the method returns to block 305 .
  • a request for accessing the object to be removed may have been transferred to a next cache server (which is next to the present cache server on the consistent Hashing ring) during the time when the present cache server was in an inactive status, and the next cache server may have cached that object.
  • the next cache server is therefore needed to be obtained and rendered as the present cache server for determining corresponding status again. The method returns to block 305 .
  • the cache server will automatically perform a removal operation for the object after the cache server recovers to an active status because the expiration period of the object has been exceeded.
  • the method records the identifier of the object, shifts from the present cache server to a next cache server, and renders the next cache server as the present cache server. The method returns to block 305 .
  • a request for accessing the object to be removed may have been transferred to a next cache server (which is next to the present cache server on the consistent Hashing ring) during the time when the present cache server was in an inactive status, and the next cache server may have cached that object.
  • the next cache server is therefore needed to be obtained and rendered as the present cache server for determining corresponding status again. The method returns to block 305 .
  • the cache server For a cache server having an inactive period less than the expiration period of the object, the cache server needs to record the identifier of the object to be removed so that the cache server may remove the object based on the recorded identifier if the cache server recovers to an active status prior to the expiration period of the object.
  • FIG. 4 shows a diagram illustrating a system structure that implements the exemplary method of removing a distributed caching object.
  • the system structure includes a source data server, N number of cache servers (where N is a positive integer), a dispatcher and a purge agent.
  • the purge agent is a server that is added for implementing the removal of a distributed caching object in the present embodiment while the source data server, the cache servers and the dispatcher implement the existing approach of storing and retrieving data in a distributed cache system.
  • the dispatcher also known as a load balancer “haproxy” receives a request for accessing an object from a user, and dispatches the request to a certain cache server based on the consistent Hashing algorithm.
  • the dispatch process is the same as the existing technology, the dispatch process is not redundantly described herein.
  • the cache server (which can be implemented by loading an open-source cache service program “squid” on an associated server) receives the request dispatched from the dispatcher, and returns the object (which the user wants to access) from therein or obtains and returns the object (which the user wants to access) from the source data server.
  • the purge agent is a server that is added to the exemplary system structure, and uses the same consistent Hashing algorithm of the dispatcher to implement the removal of a caching object.
  • the purge agent may be an independent server, or may be integrated in a certain cache server which performs the removal function.
  • the purge agent may communicate with all cache servers in the system.
  • a request for removing an object from the system is transmitted to the purge agent. For example, when a malicious image is detected and needs to be removed, or when an image of a product needs to be removed because the product is not for sale anymore, a removal request including an identifier of an object to be removed (e.g., a link address of the a malicious image) is sent to the purge agent.
  • an identifier of an object to be removed e.g., a link address of the a malicious image
  • the purge agent may further maintain a status table which includes status information of all cache servers.
  • the status table records two pieces of information of each cache server. One piece of information is a time stamp of the last status change of a cache server (based on the time stamp, a time duration since the last status change of the cache server occurs may be calculated), and the other piece of information is a current status of the cache server. The current status may be used to determine whether the cache server is presently active or down.
  • url_a be an identifier of an object to be removed.
  • a removal process of this embodiment is described with reference to the consistent Hashing ring shown in FIG. 1 .
  • url_a represents a network resource and usually is a link address of the object.
  • the object is first removed from the source data server, and url_a that exists in the cache server is removed subsequently.
  • url_a Upon applying consistent Hashing to url_a, a determination is made to first map to cache server 1 of the consistent Hashing ring for accessing url_a and the status table is checked. Corresponding process is shown in FIG. 5 .
  • the process receives a removal request which includes url_a.
  • the process determines that cache server 1 needs to be dispatched for accessing url_a based on consistent Hashing.
  • the process determines whether the presently dispatched cache server is in an active status and has an active period greater than an expiration period of the object url_a. If affirmative, the process goes to block 504 ; otherwise the process goes to block 505 .
  • the process removes the object url_a from the presently dispatched cache server and ends the present process.
  • the process determines whether the presently dispatched cache server is still down. If affirmative, the process goes to block 506 ; otherwise the process goes to block 508 .
  • the process determines whether a downtime period of the cache server that is currently down is greater than the expiration period of the object url_a. If affirmative, the process goes to block 509 ; otherwise the process goes to block 507 .
  • the access of the object url_a may have been shifted to any one of cache servers 2-4 during the time when cache server 1 was down. Accordingly, a cache server that is next in an order needs to be obtained, and blocks, starting from block 503 , are repeated for that cache server. For cache server 1, since the expiration period of the object url_a will be past once cache server 1 returns back to an active status, cache server 1 will automatically perform the removal of operation for the object url_a.
  • the process stores the present cache server and the object url_a.
  • the process continues to block 509 .
  • the access of the object url_a may have been shifted to any one of cache servers 2-4 during the time when cache server 1 was down. Accordingly, a cache server that is next in an order needs to be obtained, and blocks, starting from block 503 , are repeated for that cache server. Since the downtime period of cache server 1 is less than the expiration period of the object url_a, the object url_a needs to be recorded so that cache server 1 may remove the object url_a based on this record if cache server 1 recovers to an active status prior to the expiration period of the object url_a.
  • the relationship between the present cache server 1 and the object url_a may be stored in a deferred removal list. If cache server 1 recovers to an active status prior to the expiration period of the object url_a, the object url_a may be removed from cache server 1 based on an entry recorded in the deferred removal list.
  • the process removes the object url_a from the present cache server. If the current status of the found cache server 1 is “active” and its active period is determined to be less than the expiration period of the object's url_a based on corresponding time stamp, url_a is removed from cache server 1 first. Thereafter, upon consideration that cache server 1 was in a “down” status prior to the “active” status and a request for accessing url_a may have been shifted to any one of cache servers 2-4 during the time when cache server 1 was in a “down” status, a next cache server needs to be obtained, and blocks, starting from block 503 , are repeated for that cache server.
  • the process determines whether a next cache server may be mapped from the present cache server. If affirmative, the process goes to block 510 ; otherwise, the process is ended.
  • the process maps from the present cache server to the next cache server that is next in an order and returns to block 503 .
  • the exemplary purge agent uses the same consistent Hashing algorithm of the dispatcher and with the help of status change information of cache servers, precisely locate a cache server where the object to be removed exists. Because the object can be removed precisely and completely without requiring removal operations be performed in all cache servers, this embodiment reduces the amount of system resource that will be occupied due to performing the removal operations in all cache servers of the system as compared with existing technology.
  • a distributed cache system include three cache servers, S1, S2 and S3 respectively. Each cache server is identified by a respective IP address which acts as a respective identifier. A designated Hash function hash_function_x is applied to hash the IP addresses of S1, S2 and S3 separately. If respective Hash values so obtained are three integers, namely 1000, 2000 and 3000, these three cache servers are mapped onto the ring at positions as shown in FIG. 6 .
  • a status table showing initial status of these three cache servers be Table 1, in which Last_stamp represents a time stamp at which the last status change of a cache server occurs, and Current status represents the current status of the cache server.
  • respective Last_stamp of S1, S2 and S3 are “0” initially, indicating that time stamps of S1, S2 and S3 are all zero initially.
  • a time stamp may be recorded in a unit of “day”. For example, an initial start-up occurs in Day 1 with time stamp being “0”. The value of the time stamp increments by one in each day.
  • Current_status being “UP” indicates that S1, S2 and S3 are initially in an active status.
  • Current_status being “DOWN” indicates that associated server is down.
  • a user may want to access the object resource url_ 1 at time 1 , for example.
  • the Hash value is mapped onto the ring as shown in FIG. 6 .
  • the first cache server found is S 1. Accordingly, the request for accessing the object resource url_ 1 will be processed by S1. If the user accesses url_ 1 through S1 for the first time, S1 obtains the object resource url_ 1 from a source data server, stores url_ 1 , and returns url_ 1 to the user.
  • a Hash value of 253 for url_ 1 is obtained by applying the Hash function hash_function_x. Starting from a position at which the Hash value of 253 has been mapped and searching in a clockwise direction, the first cache server found is S1. As S1 is found to be down from the status table (Table 2), a next cache server on the ring, S2 (which is currently in an active status), is obtained by searching in a clockwise direction starting from S1. Accordingly, the request for accessing the object resource url_ 1 will be processed by S2. At that time, the object resource url_ 1 is cached in both S1 and S2.
  • url_ 1 Let the object resource url_ 1 be detected as a malicious image at time 4 . url_ 1 is therefore needed to be removed from the distributed cache system.
  • a system administrator may send a removal request to the purge agent using a standard HTTP Post method.
  • the removal request includes url_ 1 as a target to be removed.
  • the purge agent In response to receiving the removal request, the purge agent reads url_ 1 , the target to be removed, and obtains the Hash value of url_ 1 as 253 through the Hash function hash_function_x.
  • the purge agent maps the Hash value of 253 onto the ring as shown in FIG. 6 , and starting from a position at which the Hash value of 253 is mapped, finds the first cache server.
  • the purge agent further examines the status table and finds that Si has been down since time 2 and therefore cannot remove url_ 1 that is stored in S1 at that time.
  • the purge agent adds S1 and corresponding url_ 1 into a deferred removal list, and waits until S1 is resumed to remove url_ 1 .
  • the purge agent subsequently finds S2 by beginning a search from S1 in a clockwise direction along the ring.
  • the purge agent further examines the status table and finds that S2 is currently in an active status. Therefore, the purge agent sends the removal request to S2 which finds and removes the malicious image stored therein (i.e., url_ 1 ) based on the removal request. Since S2 has not been down in the past, the removal operation is completed.
  • the present disclosure further provides exemplary systems and servers of removing a distributed caching object.
  • FIG. 7 shows a block diagram illustrating an exemplary system of removing of a distributed caching object.
  • the system includes multiple cache servers 701 and a removal server 702 .
  • the multiple cache servers 701 are configured to cache objects that are accessed by users.
  • the removal server 702 is configured to receive a removal request.
  • the removal request may include an identifier of an object.
  • the removal server 702 may be further configured to apply consistent Hashing to the identifier of the object to obtain a Hash result value of the identifier.
  • the removal server 702 may locate a corresponding cache server based on the Hash result value and render the corresponding cache server to be a present cache server, and determine whether the present cache server is in an active status and has an active period greater than an expiration period associated with the object.
  • the removal server 702 may remove the object from the present cache server.
  • the removal server 702 is further configured to remove the object from the present cache server, shift from the present cache server to a next cache server in an order, render the next cache server as the present cache server, and return to the act of determining whether the present cache server is in an active status and has an active period greater than the expiration period of the object.
  • the removal server 702 may further be configured to determine whether the active period of the present cache server is greater than the expiration period of the object if the present cache server is in inactive status, shift from the present cache server to a next cache server in an order and render the next cache server as the present cache server if the inactive period is greater than the expiration period, and return to the act of determining whether the present cache server is in an active status and has an active period greater than the expiration period of the object.
  • the removal server 702 may further be configured to record the identifier if the inactive period is not greater than the expiration period, perform the act of shifting from the present cache server to a next cache server, and remove the object based on the recorded identifier after the present cache server is resumed to an active status.
  • the removal server 702 may further be configured to set up a status table of cache servers, and store a time stamp of the last status change of each cache server and a current status of each cache server in the status table.
  • the time stamp is used for determining a time duration about how long corresponding cache server is in the current status.
  • FIG. 8 shows a block diagram illustrating a first removal server 800 .
  • the removal server 800 includes a receiving unit 810 , a computation unit 820 , a locating unit 830 , a determination unit 840 and a removal unit 850 .
  • the receiving unit 810 is configured to receive a removal request, where the removal request includes an identifier of an object.
  • the computation unit 820 is configured to apply consistent Hashing to the identifier of the object to obtain a Hash result value of the identifier.
  • the locating unit 830 is configured to locate a corresponding cache server based on the Hash result value and render the corresponding cache server to be a present cache server.
  • the determination unit 840 is configured to determine whether the present cache server is in an active status and has an active period greater than an expiration period associated with the object.
  • the removal unit 850 is configured to remove the object from the present cache server in response to determining that the present cache server is in an active status and has an active period greater than the expiration period associated with the object.
  • FIG. 9 shows a block diagram illustrating a second removal server 900 .
  • the removal server 900 includes a setup unit 910 , a storage unit 920 , a receiving unit 930 , a computation unit 940 , a locating unit 950 , a determination unit 960 , a removal unit 970 , a shifting unit 980 and a recording unit 950 .
  • the setup unit 910 is configured to set up a status table of cache servers.
  • the storage unit 920 is configured to store a time stamp of the last status change of each cache server and a current status of each cache server in the status table, where the time stamp is used for determining a time duration about how long corresponding cache server is in the current status.
  • the receiving unit 930 is configured to receive a removal request, where the removal request includes an identifier of an object.
  • the computation unit 940 is configured to apply consistent Hashing to the identifier of the object to obtain a Hash result value of the identifier.
  • the locating unit 950 is configured to locate a corresponding cache server based on the Hash result value and render the corresponding cache server as a present cache server.
  • the determination unit 960 is configured to determine whether the present cache server is in an active status and has an active period greater than an expiration period of the object.
  • the removal unit 970 is configured to remove the object from the present cache server in response to determining that the present cache server is in an active status and has an active period greater than the expiration period of the object.
  • the removal unit 970 is further configured to remove the object from the present cache server in response to determining that the active period is less than the expiration period.
  • the shifting unit 980 is configured to shift from the present cache server to a next cache server, render the next cache server as the present cache server, and trigger the determination unit 960 .
  • the determination unit 960 is further configured to determine whether an inactive period of the present cache server is greater than the expiration period of the object if the present cache server is in an inactive status.
  • the shifting unit 980 is further configured to shift from the present cache server to a next cache server, render the next cache server as the present cache server, and trigger the determination unit 960 .
  • the recording unit 990 is configured to record the identifier and trigger the shifting unit 980 if the inactive period is not greater than the expiration period.
  • the removal unit 970 is further configured to remove the object based on the recorded identifier after the present cache server returns to an active status.
  • the exemplary embodiments of the present disclosure receive a removal request which includes an identifier of an object, apply consistent Hashing to the identifier of the object to obtain a Hash result value of the identifier, locate a corresponding cache server based on the Hash result value, render the corresponding cache server to be a present cache server, determine whether the present cache server is in an active status and has an active period greater than an expiration period associated with the object, and remove the object from the present cache server in response to determining that the present cache server is in the active status and has the active period greater than the expiration period associated with the object.
  • the exemplary embodiments of the present disclosure therefore do not need to perform removal operations in all cache servers.
  • the exemplary embodiments precisely locate a cache server that includes the object to be removed and perform a removal operation, thus saving the other cache servers from wasting resources to perform removal operations and hence improving the overall performance of the distributed cache system.
  • the disclosed method and system may be implemented using software with essential universal hardware platform.
  • the technical scheme of the present disclosure or existing technology may be implemented in the form of software products which are stored in a non-volatile storage media, e.g., ROM/RAM, disk, or compact disc.
  • the software includes instructions for a computing device (e.g., a personal computer, a server or a networked device) to execute the method described in the exemplary embodiments or certain parts of the exemplary embodiments in the present disclosure.
  • the various exemplary embodiments are progressively described in the present disclosure. Same or similar portions of the exemplary embodiments can be mutually referenced. Each exemplary embodiment has a different focus than other exemplary embodiments.
  • the exemplary system has been described in a relatively simple manner because of its fundamental correspondence with the exemplary method. Details thereof can be referred to related portions of the exemplary method.
  • the disclosed method and system may be used in an environment or in a configuration of universal or specialized computer system(s). Examples include a personal computer, a server computer, a handheld device or a portable device, a tablet device, a multi-processor system, a microprocessor system, a set-top box, programmable consumer electronics, a network PC, a micro-computer, a macro- computer, and a distributed computing environment including any system or device above.
  • the disclosed method and system can be described in the general context of computer-executable instructions, e.g., program modules.
  • the program modules can include routines, programs, objects, components, data structures, and the like that perform particular functions or implement particular abstract data types.
  • the disclosed method and system can also be practiced in a distributed computing environment where functions are performed by remote processing devices that are linked through a communication network.
  • the program modules may be located in local and/or remote computer storage media, including memory storage devices.
  • FIG. 10 illustrates an exemplary removal server 1000 , such as the server as described above, in more detail.
  • the server 1000 can include, but is not limited to, one or more processors 1010 , a network interface 1020 , memory 1030 , and an input/output interface 1040 .
  • the memory 1030 may include computer-readable media in the form of volatile memory, such as random-access memory (RAM) and/or non-volatile memory, such as read only memory (ROM) or flash RAM.
  • RAM random-access memory
  • ROM read only memory
  • flash RAM flash random-access memory
  • Computer-readable media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data.
  • Examples of computer storage media includes, but is not limited to, phase change memory (PRAM), static random-access memory (SRAM), dynamic random-access memory (DRAM), other types of random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information for access by a computing device.
  • computer-readable media does not include transitory media such as modulated data signals and carrier waves.
  • the memory 1030 may include program units 1050 and program data 1060 .
  • the program units 1050 may include a receiving unit 1070 , a computation unit 1080 , a locating unit 1090 , a determination unit 1100 and a removal unit 1110 . Additionally, in some embodiments, the program units 1050 may further include a setup unit 1120 and a storage unit 1130 . Additionally or alternatively, the program units 1050 may include a shifting unit 1140 and a recording unit 1150 . Details about these program units may be found in the foregoing embodiments described above.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Information Transfer Between Computers (AREA)
  • Computer And Data Communications (AREA)
  • Multi Processors (AREA)
US13/320,509 2010-08-26 2011-08-23 Method, system and server of removing a distributed caching object Active US8769208B2 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US14/266,549 US8838904B2 (en) 2010-08-26 2014-04-30 Method, system and server of removing a distributed caching object
US14/468,774 US8935482B2 (en) 2010-08-26 2014-08-26 Method, system and server of removing a distributed caching object
US14/562,224 US9047224B2 (en) 2010-08-26 2014-12-05 Method, system and server of removing a distributed caching object

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201010268800.3A CN102387169B (zh) 2010-08-26 2010-08-26 分布式缓存的对象删除方法、系统及删除服务器
CN201010268800 2010-08-26
CN201010268800.3 2010-08-26
PCT/US2011/048832 WO2012027387A1 (en) 2010-08-26 2011-08-23 Method, system and server of removing a distributed caching object

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2011/048832 A-371-Of-International WO2012027387A1 (en) 2010-08-26 2011-08-23 Method, system and server of removing a distributed caching object

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/266,549 Continuation US8838904B2 (en) 2010-08-26 2014-04-30 Method, system and server of removing a distributed caching object

Publications (2)

Publication Number Publication Date
US20130145099A1 US20130145099A1 (en) 2013-06-06
US8769208B2 true US8769208B2 (en) 2014-07-01

Family

ID=45723774

Family Applications (4)

Application Number Title Priority Date Filing Date
US13/320,509 Active US8769208B2 (en) 2010-08-26 2011-08-23 Method, system and server of removing a distributed caching object
US14/266,549 Active US8838904B2 (en) 2010-08-26 2014-04-30 Method, system and server of removing a distributed caching object
US14/468,774 Active US8935482B2 (en) 2010-08-26 2014-08-26 Method, system and server of removing a distributed caching object
US14/562,224 Active US9047224B2 (en) 2010-08-26 2014-12-05 Method, system and server of removing a distributed caching object

Family Applications After (3)

Application Number Title Priority Date Filing Date
US14/266,549 Active US8838904B2 (en) 2010-08-26 2014-04-30 Method, system and server of removing a distributed caching object
US14/468,774 Active US8935482B2 (en) 2010-08-26 2014-08-26 Method, system and server of removing a distributed caching object
US14/562,224 Active US9047224B2 (en) 2010-08-26 2014-12-05 Method, system and server of removing a distributed caching object

Country Status (6)

Country Link
US (4) US8769208B2 (zh)
EP (2) EP3312733B1 (zh)
JP (2) JP5890416B2 (zh)
CN (1) CN102387169B (zh)
HK (1) HK1164575A1 (zh)
WO (1) WO2012027387A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9965350B2 (en) 2016-09-30 2018-05-08 International Business Machines Corporation Maintaining cyclic redundancy check context in a synchronous I/O endpoint device cache system

Families Citing this family (60)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102387169B (zh) 2010-08-26 2014-07-23 阿里巴巴集团控股有限公司 分布式缓存的对象删除方法、系统及删除服务器
CN103491124B (zh) * 2012-06-14 2018-08-14 南京中兴软件有限责任公司 一种对彩信数据进行处理的方法及分布式缓存系统
CN102724314B (zh) * 2012-06-20 2015-08-05 深圳市远行科技有限公司 一种基于元数据管理的分布式缓存客户端
JP6102108B2 (ja) * 2012-07-24 2017-03-29 富士通株式会社 情報処理装置、データ提供方法、及びデータ提供プログラム
CN103078946A (zh) * 2013-01-10 2013-05-01 绍兴电力局 一种海量实时数据分布方法及其访问方法
CN103971687B (zh) * 2013-02-01 2016-06-29 腾讯科技（深圳）有限公司 一种语音识别系统中的负载均衡实现方法和装置
US9286047B1 (en) 2013-02-13 2016-03-15 Cisco Technology, Inc. Deployment and upgrade of network devices in a network environment
CN103236989B (zh) * 2013-04-25 2015-12-02 青岛海信传媒网络技术有限公司 一种内容分发网络中的缓存控制方法、设备及系统
CN103281358B (zh) * 2013-05-07 2016-04-20 汉柏科技有限公司 一种基于一致性hash算法存储资源的方法
US9210219B2 (en) 2013-07-15 2015-12-08 Red Hat, Inc. Systems and methods for consistent hashing using multiple hash rings
CN104301345B (zh) * 2013-07-17 2018-04-27 阿里巴巴集团控股有限公司 一种Cache集群中删除数据的方法及系统
US9413842B2 (en) * 2013-09-25 2016-08-09 Verizon Digital Media Services Inc. Instantaneous non-blocking content purging in a distributed platform
US9792578B2 (en) * 2013-10-08 2017-10-17 Google Inc. Managing information about inventory
US9668020B2 (en) 2014-04-07 2017-05-30 The Nielsen Company (Us), Llc Signature retrieval and matching for media monitoring
US10270876B2 (en) * 2014-06-02 2019-04-23 Verizon Digital Media Services Inc. Probability based caching and eviction
CN104052824B (zh) * 2014-07-04 2017-06-23 哈尔滨工业大学深圳研究生院 分布式缓存方法及系统
US10462249B2 (en) * 2014-08-25 2019-10-29 Super Micro Computer, Inc. Globally distributed virtual cache for worldwide real-time data access
US9860316B2 (en) * 2014-09-19 2018-01-02 Facebook, Inc. Routing network traffic based on social information
US10374904B2 (en) 2015-05-15 2019-08-06 Cisco Technology, Inc. Diagnostic network visualization
US9800497B2 (en) 2015-05-27 2017-10-24 Cisco Technology, Inc. Operations, administration and management (OAM) in overlay data center environments
US10033766B2 (en) 2015-06-05 2018-07-24 Cisco Technology, Inc. Policy-driven compliance
US10142353B2 (en) 2015-06-05 2018-11-27 Cisco Technology, Inc. System for monitoring and managing datacenters
US10536357B2 (en) 2015-06-05 2020-01-14 Cisco Technology, Inc. Late data detection in data center
US10089099B2 (en) 2015-06-05 2018-10-02 Cisco Technology, Inc. Automatic software upgrade
US9967158B2 (en) 2015-06-05 2018-05-08 Cisco Technology, Inc. Interactive hierarchical network chord diagram for application dependency mapping
US10171357B2 (en) 2016-05-27 2019-01-01 Cisco Technology, Inc. Techniques for managing software defined networking controller in-band communications in a data center network
US10931629B2 (en) 2016-05-27 2021-02-23 Cisco Technology, Inc. Techniques for managing software defined networking controller in-band communications in a data center network
US10289438B2 (en) 2016-06-16 2019-05-14 Cisco Technology, Inc. Techniques for coordination of application components deployed on distributed virtual machines
US10708183B2 (en) 2016-07-21 2020-07-07 Cisco Technology, Inc. System and method of providing segment routing as a service
CN106528455A (zh) * 2016-10-28 2017-03-22 上海斐讯数据通信技术有限公司 电子终端的多媒体缓存的清理方法、系统及电子终端
US10972388B2 (en) 2016-11-22 2021-04-06 Cisco Technology, Inc. Federated microburst detection
US10708152B2 (en) 2017-03-23 2020-07-07 Cisco Technology, Inc. Predicting application and network performance
US10523512B2 (en) 2017-03-24 2019-12-31 Cisco Technology, Inc. Network agent for generating platform specific network policies
US10764141B2 (en) 2017-03-27 2020-09-01 Cisco Technology, Inc. Network agent for reporting to a network policy system
US10594560B2 (en) 2017-03-27 2020-03-17 Cisco Technology, Inc. Intent driven network policy platform
US10250446B2 (en) 2017-03-27 2019-04-02 Cisco Technology, Inc. Distributed policy store
US10873794B2 (en) 2017-03-28 2020-12-22 Cisco Technology, Inc. Flowlet resolution for application performance monitoring and management
CN108932236B (zh) * 2017-05-22 2021-05-07 北京金山云网络技术有限公司 一种文件管理方法及装置
US11860819B1 (en) * 2017-06-29 2024-01-02 Amazon Technologies, Inc. Auto-generation of partition key
US10680887B2 (en) 2017-07-21 2020-06-09 Cisco Technology, Inc. Remote device status audit and recovery
US10554501B2 (en) 2017-10-23 2020-02-04 Cisco Technology, Inc. Network migration assistant
US10523541B2 (en) 2017-10-25 2019-12-31 Cisco Technology, Inc. Federated network and application data analytics platform
US10594542B2 (en) 2017-10-27 2020-03-17 Cisco Technology, Inc. System and method for network root cause analysis
CN108134817B (zh) * 2017-11-30 2019-04-05 北京白山耘科技有限公司 一种自动调整缓存时长的方法及装置
CN108055302B (zh) * 2017-12-05 2020-10-20 竞技世界（北京）网络技术有限公司 一种图片缓存处理方法、系统和服务器
US11233821B2 (en) 2018-01-04 2022-01-25 Cisco Technology, Inc. Network intrusion counter-intelligence
US11765046B1 (en) 2018-01-11 2023-09-19 Cisco Technology, Inc. Endpoint cluster assignment and query generation
US10574575B2 (en) 2018-01-25 2020-02-25 Cisco Technology, Inc. Network flow stitching using middle box flow stitching
US10798015B2 (en) 2018-01-25 2020-10-06 Cisco Technology, Inc. Discovery of middleboxes using traffic flow stitching
US10999149B2 (en) 2018-01-25 2021-05-04 Cisco Technology, Inc. Automatic configuration discovery based on traffic flow data
US10917438B2 (en) 2018-01-25 2021-02-09 Cisco Technology, Inc. Secure publishing for policy updates
US10826803B2 (en) 2018-01-25 2020-11-03 Cisco Technology, Inc. Mechanism for facilitating efficient policy updates
US10873593B2 (en) 2018-01-25 2020-12-22 Cisco Technology, Inc. Mechanism for identifying differences between network snapshots
US11128700B2 (en) 2018-01-26 2021-09-21 Cisco Technology, Inc. Load balancing configuration based on traffic flow telemetry
US10498696B2 (en) * 2018-01-31 2019-12-03 EMC IP Holding Company LLC Applying a consistent hash to a distributed domain name server cache
CN110300140B (zh) * 2018-03-23 2023-04-18 贵州白山云科技股份有限公司 用于云分发网络中内容更新的方法、刷新客户端及网络节点
CN109167840B (zh) * 2018-10-19 2021-12-07 网宿科技股份有限公司 一种任务推送方法、节点自治服务器及边缘缓存服务器
CN109948098B (zh) * 2019-02-21 2021-07-06 网宿科技股份有限公司 数据过滤方法、缓存信息的记录方法及装置
CN110032671B (zh) * 2019-04-12 2021-06-18 北京百度网讯科技有限公司 用户轨迹信息的处理方法、装置、计算机设备及存储介质
US11218561B1 (en) 2021-03-09 2022-01-04 Wipro Limited Method and system for managing cache data in a network through edge nodes

Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6154811A (en) 1997-04-10 2000-11-28 At&T Corp. Scalable network object caching
US6658487B1 (en) 1996-03-29 2003-12-02 British Telecommunications Public Limited Company Collection of events within a distributed object system
US6999988B2 (en) 2000-07-13 2006-02-14 Lucent Technologies Inc. Method and system for data layout and replacement in distributed streaming caches on the Internet
US7062541B1 (en) 2000-04-27 2006-06-13 International Business Machines Corporation System and method for transferring related data objects in a distributed data storage environment
US20080034165A1 (en) 2003-11-17 2008-02-07 Iyengar Arun K System and method for achieving deferred invalidation consistency
US20080235292A1 (en) 2005-10-03 2008-09-25 Amadeus S.A.S. System and Method to Maintain Coherence of Cache Contents in a Multi-Tier System Aimed at Interfacing Large Databases
US7469256B1 (en) 2004-04-29 2008-12-23 Sap Ag Cached persistent data management through state tracking
US20090083115A1 (en) 2007-09-24 2009-03-26 Pearson Gregory A Interactive networking systems
US20090313438A1 (en) 2008-06-12 2009-12-17 Microsoft Corporation Distributed cache arrangement
US7657548B2 (en) 2002-09-20 2010-02-02 Novell, Inc. Method for dynamically distributing items for changes based on group membership
US20100088398A1 (en) 2007-03-12 2010-04-08 Robert Plamondon Systems and methods for domain name resolution interception caching
US20100180208A1 (en) 2009-01-15 2010-07-15 Kasten Christopher J Server side data cache system
US7802065B1 (en) 2004-05-03 2010-09-21 Crimson Corporation Peer to peer based cache management
US20110191541A1 (en) 2010-01-29 2011-08-04 Lee Edward Lowry Techniques for distributed cache management
US20110196831A1 (en) 2010-02-09 2011-08-11 Yonatan Zunger Pruning of Blob Replicas

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6449695B1 (en) * 1999-05-27 2002-09-10 Microsoft Corporation Data cache using plural lists to indicate sequence of data storage
US6601090B1 (en) * 1999-06-25 2003-07-29 Nortel Networks Limited System and method for servicing internet object accessess from a coupled intranet
JP2003085032A (ja) * 2001-09-10 2003-03-20 Kanazawa Inst Of Technology 自己組織化キャッシュ方法およびその方法を利用可能なキャッシュサーバ
CN1221898C (zh) * 2002-08-13 2005-10-05 国际商业机器公司 刷新网络代理高速缓存服务器对象的系统和方法
US7873782B2 (en) * 2004-11-05 2011-01-18 Data Robotics, Inc. Filesystem-aware block storage system, apparatus, and method
EP1842354B1 (en) * 2005-01-24 2014-11-05 Citrix Systems, Inc. Systems and methods for performing caching of dynamically generated objects in a network
US8504775B2 (en) 2007-03-12 2013-08-06 Citrix Systems, Inc Systems and methods of prefreshening cached objects based on user's current web page
CN101778367B (zh) * 2009-12-29 2012-09-05 北京首信科技股份有限公司 一种计费网关重启恢复工作的方法
CN102387169B (zh) 2010-08-26 2014-07-23 阿里巴巴集团控股有限公司 分布式缓存的对象删除方法、系统及删除服务器

Patent Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6658487B1 (en) 1996-03-29 2003-12-02 British Telecommunications Public Limited Company Collection of events within a distributed object system
US6154811A (en) 1997-04-10 2000-11-28 At&T Corp. Scalable network object caching
US7062541B1 (en) 2000-04-27 2006-06-13 International Business Machines Corporation System and method for transferring related data objects in a distributed data storage environment
US6999988B2 (en) 2000-07-13 2006-02-14 Lucent Technologies Inc. Method and system for data layout and replacement in distributed streaming caches on the Internet
US7657548B2 (en) 2002-09-20 2010-02-02 Novell, Inc. Method for dynamically distributing items for changes based on group membership
US20080034165A1 (en) 2003-11-17 2008-02-07 Iyengar Arun K System and method for achieving deferred invalidation consistency
US7469256B1 (en) 2004-04-29 2008-12-23 Sap Ag Cached persistent data management through state tracking
US7802065B1 (en) 2004-05-03 2010-09-21 Crimson Corporation Peer to peer based cache management
US20080235292A1 (en) 2005-10-03 2008-09-25 Amadeus S.A.S. System and Method to Maintain Coherence of Cache Contents in a Multi-Tier System Aimed at Interfacing Large Databases
US20100088398A1 (en) 2007-03-12 2010-04-08 Robert Plamondon Systems and methods for domain name resolution interception caching
US20090083115A1 (en) 2007-09-24 2009-03-26 Pearson Gregory A Interactive networking systems
US20090313438A1 (en) 2008-06-12 2009-12-17 Microsoft Corporation Distributed cache arrangement
US20100180208A1 (en) 2009-01-15 2010-07-15 Kasten Christopher J Server side data cache system
US20110191541A1 (en) 2010-01-29 2011-08-04 Lee Edward Lowry Techniques for distributed cache management
US20110196831A1 (en) 2010-02-09 2011-08-11 Yonatan Zunger Pruning of Blob Replicas

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
PCT Search Report and written opinion mailed Jan. 10, 2012 for PCT application No. PCT/US11/48832, 9 pages.

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9965350B2 (en) 2016-09-30 2018-05-08 International Business Machines Corporation Maintaining cyclic redundancy check context in a synchronous I/O endpoint device cache system

Also Published As

Publication number Publication date
EP2609521A1 (en) 2013-07-03
JP5890416B2 (ja) 2016-03-22
JP2013536530A (ja) 2013-09-19
JP2016085767A (ja) 2016-05-19
US20140365600A1 (en) 2014-12-11
CN102387169B (zh) 2014-07-23
HK1164575A1 (zh) 2012-09-21
EP3312733A3 (en) 2018-05-02
US20150113227A1 (en) 2015-04-23
US8935482B2 (en) 2015-01-13
JP6280146B2 (ja) 2018-02-14
EP3312733B1 (en) 2019-10-16
US8838904B2 (en) 2014-09-16
US20140237068A1 (en) 2014-08-21
US9047224B2 (en) 2015-06-02
US20130145099A1 (en) 2013-06-06
EP2609521B1 (en) 2018-01-17
WO2012027387A1 (en) 2012-03-01
CN102387169A (zh) 2012-03-21
EP2609521A4 (en) 2014-03-26
EP3312733A2 (en) 2018-04-25

Similar Documents

Publication Publication Date Title
US9047224B2 (en) Method, system and server of removing a distributed caching object
US8689280B2 (en) DNS-based content routing
US8949535B1 (en) Cache updating
CN107153644B (zh) 一种数据同步方法及装置
JP6388339B2 (ja) 分散キャッシングおよびキャッシュ分析
CN111385316B (zh) 资源刷新方法、访问方法及装置
US9495469B2 (en) System and method to identify machine-readable codes
US10979532B2 (en) Resource download method, electronic device, and apparatus
US20170153909A1 (en) Methods and Devices for Acquiring Data Using Virtual Machine and Host Machine
WO2019196825A1 (zh) 基于区块链网络的资源获取方法和系统及存储介质和计算机设备
CN112433921A (zh) 用于动态埋点的方法及设备
US20220078161A1 (en) Method and apparatus for advertisement anti-blocking
CN107220260B (zh) 一种页面显示的方法及装置
KR102042431B1 (ko) 클라우드 환경에서 웹 캐싱을 위한 메타 정보 저장 방법 및 이를 사용한 웹 서버
CN106649792B (zh) 一种页面访问方法及装置
JP6553650B2 (ja) データ処理の方法及びシステム
CN106940660B (zh) 缓存的实现的方法和装置
TWI496014B (zh) Decentralized cache object removal method, system and delete server
CN116248502A (zh) 用于更新浏览器本地的用户相关数据的方法、设备及系统
CN118260286A (zh) 一种数据存储方法及装置

Legal Events

Date Code Title Description
AS Assignment

Owner name: ALIBABA GROUP HOLDING LIMITED, CAYMAN ISLANDS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LIU, GANG;REN, QING;ZHANG, WENSONG;REEL/FRAME:027224/0751

Effective date: 20111110

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551)

Year of fee payment: 4

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 8