Is there an issue with the description in the document regarding the solution to the "continue parameter is too old to display a consistent list result" problem?

[promid]

argo-cd/docs/operator-manual/high_availability.md

Line 119 in 52e94fd

may throw an error that the `continue parameter is too old to display a consistent list result`. Setting a higher

The doc states:

`ARGOCD_CLUSTER_CACHE_LIST_PAGE_BUFFER_SIZE` - environment variable controlling the number of pages the controller
  buffers in memory when performing a list operation against the K8s api server while syncing the cluster cache. This
  is useful when the cluster contains a large number of resources and cluster sync times exceed the default etcd
  compaction interval timeout. In this scenario, when attempting to sync the cluster cache, the application controller
  may throw an error that the `continue parameter is too old to display a consistent list result`. Setting a higher
  value for this environment variable configures the controller with a larger buffer in which to store pre-fetched
  pages which are processed asynchronously, increasing the likelihood that all pages have been pulled before the etcd
  compaction interval timeout expires.

However, to resolve the continue parameter is too old to display a consistent list result error, it may be more appropriate to increase the ARGOCD_CLUSTER_CACHE_LIST_PAGE_SIZE instead of the ARGOCD_CLUSTER_CACHE_LIST_PAGE_BUFFER_SIZE. When a resource has many instances in etcd, the list request is divided into multiple requests with the continue parameter. If there is too much data, older resourceVersion objects may get compacted by etcd, leading to the continue parameter is too old to display a consistent list result error.

Please help confirm this. Thanks.