Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-100779

Cluster parameters for catalog cache sizing

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This is part 3 of multi-part work derived from SERVER-82707. This work is optional, based on product's opinion on whether it is required to be done.

      Once we can dynamically resize the cache at run time using the server parameters, we will optionally like to have cluster parameters for easier management. We will also need to consider preserving the ability to set a node to have a different sized cache than the rest of the cluster.

      Some of this work is based on the work of intern Andres, who accomplished some of this as a mini-project in SERVER-84243. The catalog cache, in the meanwhile, has been split into multiple caches (SERVER-84243), and hence, this work needs to be brought onto the current state of the master. The work done by Andres has a limitation that this ticket will need to address: The parameterization is done through the cluster parameters, which would trigger onUpdate callback frequently on the routers, I believe every 30 seconds. This will result in a lock taken to set the parameters, even when the parameters have not changed. We will need to fix that here.

            Assignee:
            Unassigned Unassigned
            Reporter:
            sulabh.mahajan@mongodb.com Sulabh Mahajan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              None
              None
              None
              None