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

Test glibc without relying on sharding_auth and sharding_auth_audit

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Build
    • 0

      We have two sharding_auth* BFs where a glibc bug (strongly suspected but unconfirmed) resulted in a crash.

      It would be better if we could have targeted coverage for those cases rather than relying on sharding_auth / sharding_auth_audit. The plan is to delete sharding_auth / sharding_auth_audit and currently we are unable to do so due to the incidental (unintentional) coverage provided by them (see analysis in SERVER-93653 for more info).

      If we think this work is unnecessary, feel free to close.

      See comments for BFs.

            Assignee:
            Unassigned Unassigned
            Reporter:
            vishnu.kaushik@mongodb.com Vishnu Kaushik
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: