Integrating change tracking of storage objects of a distributed object storage database into a distributed storage system

A storage node comprising:

• one or more processing resources;
• and
• a non-transitory computer-readable medium coupled to the processing resource, having stored therein instructions, which when executed by the one or more processing resources cause the one or more processing resources to:
• manage storage objects and continuously track changes of the storage objects in a distributed object storage database that includes one or more chapter databases with the distributed object storage database supporting a primary lookup index and a secondary lookup index for each chapter database that includes pending work items to be sorted by a peer identity in order to locate a record;
• generate a chapter database header for each chapter database to provide a summary of pending work items to be performed;
• recording an array of multiple directives into a header of a chapter database to describe pending work items from a bucket to one or more peer buckets to allow continual collective tracking of an overall replication state from the bucket to one or more peer buckets;
• sorting the pending work items in the header based on urgency of performing each pending work item and a recovery point objective (RPO) for each peer bucket to prioritize urgent pending work items;
• and
• update the chapter database header when work items are updated for the chapter database.

A non-transitory computer-readable storage medium embodying a set of instructions, which when executed by one or more processing resources of a distributed storage system cause the one or more processing resources to:

• manage storage objects and continuously track changes of the storage objects in a distributed object storage database that includes one or more chapter databases with the distributed object storage database supporting a primary lookup index and a secondary lookup index for each chapter database that includes pending work items to be sorted by a peer identity in order to locate a record;
• recording an array of multiple directives into a header of a chapter database to describe pending work items from a bucket to one or more peer buckets to allow continual collective tracking of an overall replication state from the bucket to one or more peer buckets;
• and
• sorting the pending work items in the header based on urgency of performing each pending work item and a recovery point objective (RPO) for each peer bucket to prioritize urgent pending work items.