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

Remove mongos dependency on rw_concern_d library

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.4.0-rc2
    • Component/s: None
    • None
    • Sharding NYC

      rw_concern_d is a mongod-specific library but appears to wind up as a dependency in libraries, such as service_entry_point_commonsharding_catalog_manager, and transaction_coordinator, which are not mongod-specific.

      As a result, statically compiling the mongos leads to all symbols in rw_concern_d being included in the binary. This is incorrect because, among other things, it links the JournalFlusher into the mongos and has caused problems when adding new code (TTLMonitor with ServerStatusMetricField instances) to the storage control API (the storage_control library is a dependency of rw_concern_d).

      We should aim to remove the mongos dependency on rw_concern_d.

            Assignee:
            backlog-server-sharding-nyc [DO NOT USE] Backlog - Sharding NYC
            Reporter:
            james.heppenstall@mongodb.com James Heppenstall
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: