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

Investigate whether secondary filtering metadata should handle rollbacks of config.cache.chunks

    XMLWordPrintable

    Details

    • Type: Question
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Sharding
    • Labels:
      None

      Description

      When a secondary rolls back changes to config.cache, it keeps its in memory filtering metadata. That means that it could potentially have a filtering metadata version higher than what it actually has. I went through a few scenarios and it looks like it might not invalidate the promises with causal consistency or snapshot reads. A more detailed investigation should be made to decide whether we need to handle rollbacks and document in this ticket if we determined why it is safe to keep it that way.

        Attachments

          Activity

            People

            Assignee:
            renctan Randolph Tan
            Reporter:
            renctan Randolph Tan
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: