Salesforce Com, Inc.

Salesforce, Inc.

Atish Agrawal

Jameison Bear Martin

James E Mace

Techniques are disclosed relating to providing and using probabilistic data structures to at least reduce requests between database nodes. In various embodiments, a first database node processes a database transaction that involves writing a set of database records to an in-memory cache of the first database node. As part of processing the database transaction, the first database node may insert, in a set of probabilistic data structures, a set of database keys that correspond to the set of database records. The first database node may send, to a second database node, the set of probabilistic data structures to enable the second database node to determine whether to request, from the first database node, a database record associated with a database key.

Reducing requests using probabilistic data structures

Techniques are disclosed relating to orchestrating locking between database nodes of a database system. A database node can determine that an execution of a database transaction at the database node involves acquiring a lock. The database node acquires, from a separate lease manager node, a lease object that permits the database node to create the lock for the database transaction. As a part of provisioning that lease object to the database node, the lease manager node ensures that a lease object for creating locks that conflict with the lock is not held by another database node. The database node creates the lock for the database transaction based on the acquired lease object. As a part of creating that lock, the database node ensures that the lock does not conflict with a lock held by another database transaction executing at the database node.

Distributed database locking

Systems and methods are provided for a shared memory between a database system and a storage catalog server, which stores system catalog overrides and locks for at least a first workflow. The current system catalog overrides include at least a portion of the system catalog overrides and locks that are retrieved by the shared memory from the storage catalog server at a predetermined point in time. The database system performs a check of at least one of index validity and tenant validity for a second workflow or other database operation by checking a state of the corresponding tenant or index in the current system catalog overrides. The system catalog overrides suppress visibility of the respective system catalog changes when the database system determines that at least one of the index and the tenant is invalid based on the current system catalog overrides for the first workflow.

Growing community of inventors

Seattle, WA, United States of America

Atish Agrawal