System, method and computer program product for monitoring data activity utilizing a shared data store

• US 9,237,080 B2
• Filed: 04/18/2013
• Issued: 01/12/2016
• Est. Priority Date: 02/24/2010
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Yancey, Scott, Hansma, Scott
• Primary Examiner(s): Pollack, Melvin H
• Application Number:
  US13/865,879
• Publication Number:
  US 20130254387A1
• Time in Patent Office: 999 Days
• Field of Search: 709/224
• US Class Current: 1/1
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3438 monitoring of user actions tracking the activity of the user H04L67/535
• CPC Class Codes: G06F 12/0813 with a network or matrix configuration
• CPC Class Codes: G06F 15/173 using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake
• CPC Class Codes: G06F 16/219 Managing data history or versioning querying versioned data G06F16/2474; querying temporal data G06F16/2477
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 2212/60 Details of cache memory
• CPC Class Codes: G06F 2212/62 Details of cache specific to multiprocessor cache arrangements
• CPC Class Codes: H04L 43/067 using time frame reporting
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/0876 Network utilisation, e.g. volume of load or congestion level
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

In accordance with embodiments, there are provided mechanisms and methods for monitoring data activity utilizing a shared data store. These mechanisms and methods for monitoring data activity utilizing a shared data store can enable enhanced data monitoring, more efficient data storage, improved system resource utilization, etc.

Claims

1. A computer program product, comprising a non-transitory computer usable medium having a computer readable program code embodied therein, the computer readable program code adapted to be executed by a computer to perform a method comprising:

monitoring, by a system, a plurality of requests received across multiple servers of the system;

maintaining, by the system in a shared data store of the system, a count of a number of the plurality of requests that are outstanding across the multiple servers of the system; and

limiting, by the system, additional requests issued across the multiple servers of the system, based on the count of the number plurality of the requests that are outstanding across the multiple servers of the system.

2. The computer program product of claim 1, wherein the plurality of requests are received by the multiple servers of the system from a particular user of the system.

3. The computer program product of claim 2, wherein the monitoring, maintaining, and the limiting are performed separately for each user of the system.

4. The computer program product of claim 1, wherein the plurality of requests that are outstanding are those that are not completed by the multiple servers of the system.

5. The computer program product of claim 1, wherein the shared data store of the system is a distributed memory cache shared by the multiple servers of the system.

6. The computer program product of claim 1, wherein the count of the number of the plurality of requests that are outstanding across the multiple servers of the system is maintained in the shared data store is association with a hash indicating each of the multiple servers.

7. The computer program product of claim 6, wherein the multiple servers indicated by the hash are operational for processing the plurality of requests.

8. The computer program product of claim 7, further comprising altering the hash in response to one of the multiple servers ceasing operation such that the altered hash does not indicate the one of the multiple servers that has ceased operation.

9. The computer program product of claim 8, further comprising resetting the count of the number of the plurality of requests that are outstanding across the multiple servers to zero in response to the altering of the hash.

10. The computer program product of claim 1, wherein limiting, by the system, additional requests issued across the multiple servers of the system, based on the count of the number plurality of the requests that are outstanding across the multiple servers of the system includes:

identifying a predetermined threshold,

determining whether the count of the number plurality of the requests that are outstanding across the multiple servers of the system exceeds the threshold,

denying the additional requests from being processed by the multiple servers of the system in response to determining that the count of the number plurality of the requests that are outstanding across the multiple servers of the system exceeds the threshold, and

allowing the additional requests to be processed by the multiple servers of the system in response to determining that the count of the number plurality of the requests that are outstanding across the multiple servers of the system does not exceed the threshold.

11. The computer program product of claim 1, wherein limiting, by the system, additional requests issued across the multiple servers of the system, based on the count of the number plurality of the requests that are outstanding across the multiple servers of the system includes:

identifying a predetermined threshold,

determining whether the count of the number plurality of the requests that are outstanding across the multiple servers of the system exceeds the threshold,

queuing the additional requests to be processed by the multiple servers of the system in response to determining that the count of the number plurality of the requests that are outstanding across the multiple servers of the system exceeds the threshold, and

allowing the additional requests to be processed by the multiple servers of the system in response to determining that the count of the number plurality of the requests that are outstanding across the multiple servers of the system does not exceed the threshold.

12. A method, comprising:

monitoring, by a system, a plurality of requests received across multiple servers of the system;

maintaining, by the system in a shared data store of the system, a count of a number of the plurality of requests that are outstanding across the multiple servers of the system; and

limiting, by the system, additional requests issued across the multiple servers of the system, based on the count of the number plurality of the requests that are outstanding across the multiple servers of the system.

13. An apparatus, comprising:

a processor of a system for;

monitoring, by the system, a plurality of requests received across multiple servers of the system;

maintaining, by the system in a shared data store of the system, a count of a number of the plurality of requests that are outstanding across the multiple servers of the system; and

limiting, by the system, additional requests issued across the multiple servers of the system, based on the count of the number plurality of the requests that are outstanding across the multiple servers of the system.