US 11,960,363 B2
Write optimized, distributed, scalable indexing store
Apurv Gupta, Bangalore (IN); Akshat Agarwal, Delhi (IN); Manvendra Singh Tomar, Bengaluru (IN); and Anshu Avinash, Bengaluru (IN)
Assigned to Cohesity, Inc., San Jose, CA (US)
Filed by Cohesity, Inc., San Jose, CA (US)
Filed on Sep. 14, 2020, as Appl. No. 17/020,254.
Claims priority of provisional application 62/904,561, filed on Sep. 23, 2019.
Prior Publication US 2021/0089407 A1, Mar. 25, 2021
Int. Cl. G06F 11/14 (2006.01); G06F 11/07 (2006.01)
CPC G06F 11/1464 (2013.01) [G06F 11/0772 (2013.01); G06F 11/1435 (2013.01); G06F 11/1451 (2013.01); G06F 11/1469 (2013.01)] 22 Claims
OG exemplary drawing
 
1. A method, comprising:
receiving a batch of a plurality of different indexing updates of a data repository associated with a secondary storage system configured to perform a backup of a primary storage system;
sending at least a first portion of the batch of the plurality of different indexing updates for storage, wherein the batch of the plurality of different indexing updates is associated with a session identifier, wherein the at least the first portion of the batch of the plurality of different indexing updates are stored in an intermediate store for temporary storage, wherein a metadata store manager commits the first portion of the batch of the plurality of different indexing updates from the intermediate store to a first data bucket of a metadata store in response to an occurrence of at least one commitment factor, wherein the at least one commitment factor is associated with a particular fraction of the intermediate store being full;
receiving a second portion of the batch of the plurality of different indexing updates;
sending the second portion of the batch of the plurality of different indexing updates for storage and a request to commit the second portion of the batch of the plurality of different indexing updates, wherein the metadata store manager determines that that the session identifier associated with the batch of the plurality of different indexing updates is invalid;
receiving from the metadata store manager an indication that the session identifier associated with the batch of the plurality of different indexing updates is invalid;
establishing a new communication session with the metadata store manager, wherein the new communication session is associated with a new session identifier; and
sending to the metadata store manager a request to commit the first portion and the second portion of the batch of the plurality of different indexing updates, wherein in response, the metadata store manager commits in a second data bucket of the metadata store the first portion and the second portion of the batch of the plurality of different indexing updates.