Hi, The bookmark encodes the "order" property of the last result from each shard range, and a query with a bookmark parameter is simply retrieving matches that come after those order values. If the database changes between queries (documents added, changed or removed) such that the overall ordering of search results also changes, it is normal to see search results repeated (a database change added an item to a previous page, pushing every later change further down the list) or missing (a database change removed an item from a previous page, moving everyone "up").
B. > On 20 Sep 2022, at 01:23, Luca Morandini <[email protected]> wrote: > > Hi, > > I added a text search index to a 4-node, Kubernetes-deployed, > clustered database and started querying it. > > The queries work, but I noticed that a variable (say, 1%-8%) > proportion of the documents ids returned in batches through pagination > (using bookmarks) was already returned by previous pages. The > duplicated IDs change somewhat at every run, hence ithe phenomenon > seems to be random. > > I did not use stale in the requests, just the query, a limit set to > 200, and the bookmark returned by the previous pagination response. > > There are no errors in the log of either CocuhDB or Clouseau. > > Could someone shed some light on this? > > Cheers, > > Luca Morandini
