Probabilistic data storage owner election and replication protocol

• US 8,560,685 B1
• Filed: 07/20/2011
• Issued: 10/15/2013
• Est. Priority Date: 07/20/2011
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Marifet, Kasem, Deshpande, Mayur Venktesh, Matthews, Jacob Burton, Wogulis, James Lee
• Primary Examiner(s): Armouche, Hadi
• Assistant Examiner(s): Harris, Christopher C
• Application Number:
  US13/187,456
• Time in Patent Office: 818 Days
• Field of Search: None
• US Class Current: 709/224
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 2201/875 Monitoring of systems including the internet
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: H04L 43/04 Processing captured monitoring data, e.g. for logfile generation
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/28 Timers or timing mechanisms used in protocols

Abstract

Configurations providing a probabilistic ownership protocol for managing respective web property IDs (WPID) associated with incoming event tracking data communications are described. A server can determine whether an event tracking data communication with an associated WPID has an owner by checking a master ownership table. The server can register an intent to become an owner of the event tracking data communication if a minimum number of owner(s) is not met. The server then waits for a random period of time. After the random period of time, the server can check the master ownership table to determine whether the event tracking data communication has an owner or enough owners. The server can then register for ownership of the event tracking data communication by modifying the master ownership table if the event tracking data communication does not have an owner or enough owners.

Claims

1. A machine-implemented method for peer-to-peer management of an incoming event tracking data communication, the method comprising:

receiving, by a processor, an event tracking data communication, wherein the event tracking data communication includes event tracking data for tracking an activity associated with a source of the event tracking data communication;

determining, by the processor, whether a tracking account associated with the event tracking data communication has an owner, wherein the owner comprises a real-time server assigned to process incoming event tracking data communications associated with the tracking account;

registering, by the processor, an intent for ownership of the tracking account if it is determined that the tracking account does not have an owner;

accumulating, by the processor, incoming event tracking data communications during a random period of time; and

after the random period of time has elapsed, determining, by the processor, whether the tracking account has an owner, and registering, by the processor, for ownership of the tracking account if it is determined that the tracking account does not have an owner.

2. The method of claim 1, wherein the event tracking data includes web site traffic data included in a Hypertext Transfer Protocol (HTTP) request associated with the web site.

3. The method of claim 1, further comprising:

transmitting the event tracking data communication to a registered owner of the tracking account in response to the tracking account having an owner.

4. The method of claim 1, further comprising:

transmitting the event tracking data communication to one or more owners after the random period of time has elapsed if the tracking account has one or more owners.

5. The method of claim 1, further comprising:

registering for ownership of the tracking account if it is determined that a number of associated owners of the tracking account is below a predetermined number of owners.

6. The method of claim 1, wherein registering for ownership of the tracking account comprises modifying an ownership table.

7. The method of claim 6, further comprising:

notifying one or more real-time servers of the registered ownership of the tracking account by transmitting the modified ownership table.

8. The method of claim 7, wherein notifying one or more real-time servers of the registered ownership comprises a multicast transmission of the modified ownership table.

9. The method of claim 1, wherein determining whether the tracking account has an owner is based on a web property identity.

10. A machine-implemented method for peer-to-peer management of an incoming event tracking data communication, the method comprising:

determining, by a processor, whether a number of owners for a tracking account associated with a first event tracking data communication is less than a predetermined number of owners, wherein the event tracking data communication includes event tracking data for tracking an activity associated with a source of the event tracking data communication, and each owner comprises a real-time server assigned to process incoming event tracking data communications associated with the tracking account;

registering, by the processor, an intent for ownership of the tracking account if the number of owners is less than a predetermined number of owners;

receiving, by the processor, a second event tracking data communication before a first random period of time has elapsed, wherein the tracking account is associated with the second event tracking data communication;

determining, by the processor, a second random period of time to wait from a remaining period of time of the first random period of time; and

after the second random period of time has elapsed, determining, by the processor, whether the tracking account has less than the predetermined number of owners, and registering, by the processor, for ownership of the tracking account if it is determined that the tracking account has less than the predetermined number of owners.

11. The method of claim 10, wherein the event tracking data includes web site traffic data included in a Hypertext Transfer Protocol (HTTP) request associated with the web site.

12. The method of claim 10, wherein the first and second event tracking data communications are associated with a same web property identity.

13. The method of claim 10, further comprising:

transmitting the first and second event tracking data communications to a real-time server if the tracking account has at least the predetermined number of owners, wherein the real-time server is an owner of the website.

14. A machine-readable medium comprising instructions stored therein, which when executed by a machine, cause the machine to perform operations comprising:

determining whether a tracking account associated with an event tracking data communication has a predetermined number of owners, wherein the event tracking data communication includes event tracking data for tracking an activity associated with a source of the event tracking data communication, and each owner comprises a real-time server assigned to process incoming event tracking data communications associated with the tracking account;

registering an intent for ownership of the tracking account if it is determined that the tracking account does not have the predetermined number of owners;

accumulating incoming event tracking data communications during a random period of time; and

after the random period of time has elapsed, determining whether the tracking account has an owner, and registering for ownership of the tracking account if it is determined that the tracking account does not have an owner.

15. The machine-readable medium of claim 14, wherein the event tracking data includes web site traffic data included in a Hypertext Transfer Protocol (HTTP) request associated with the tracking account.

16. The machine-readable medium of claim 14 comprising further instructions stored therein, which when executed by the machine, cause the machine to perform further operations comprising:

transmitting the event tracking data communication to each registered owner if the tracking account has at least one owner after the random period of time has elapsed.

17. The machine-readable medium of claim 14 comprising further instructions stored therein, which when executed by the machine, cause the machine to perform further operations comprising:

notifying one or more real-time servers of an updated ownership of the tracking account after registering for ownership of the tracking account.

18. The machine-readable medium of claim 14, wherein the predetermined number of owners is at least two owners.

19. A system for peer-to-peer management of incoming event tracking data communications, the system comprising:

memory;

one or more processors;

one or more modules stored in memory and configured for execution by the one or more processors, the modules comprising;

a parser module configured to parse web site tracking data included in an event tracking data communication to extract real-time analytics data, wherein the event tracking data communication includes event tracking data for tracking an activity associated with a source of the event tracking data communication, and the source is a web site;

a buffer module configured to accumulate incoming event tracking data communications during a random period of time;

an ownership module configured to, after the random period of time has elapsed, determine whether the extracted real-time analytics data has an associated owner, wherein the associated owner comprises a real-time server assigned to process incoming event tracking data communications associated with the web site; and

a request router module configured to route the web site tracking data.

20. The system of claim 19, wherein the event tracking data includes web site traffic data included in a Hypertext Transfer Protocol (HTTP) request associated with the web site.

21. The system of claim 19, wherein the ownership module is further configured to register an intent for ownership of a tracking account associated the event tracking data communication if a minimum number of owners is not associated with the tracking account.

22. The system of claim 19, wherein the one or more modules stored in memory and configured for execution by the one or more processors further comprise:

a hit accumulator module configured to receive the web site tracking data routed from the request router module.

23. The system of claim 22, wherein the request router module routes the web site tracking data to the hit accumulator module in response to the ownership module determining that the system is an owner of a tracking account associated with the web site tracking data.