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

getShardVersion command should alert the user in some way if the max bson size was exceeeded

    • Sharding EMEA
    • Fully Compatible
    • Sharding EMEA 2023-04-03, Sharding EMEA 2023-04-17

      The cluster getShardVersion command and the shard getShardVersion command will append all chunks + all global indexes if fullMetadata is set to true. However, if the list of chunks and indexes exceeds the max bson size, the user could get a partial list or nothing at all.

      In the cluster command, if the list of chunks is going to exceed the max bson size, we will not return any chunks whereas for indexes, we will append a partial list of indexes. The shard command has the same behavior as the cluster command for indexes , but doesn't check the bson size for chunks.

      In the cases where the BSON size is exceeded and we are returning partial or empty responses to the user, we should indicate to the user in some way that the returned metadata is incomplete.

            allison.easton@mongodb.com Allison Easton
            allison.easton@mongodb.com Allison Easton
            0 Vote for this issue
            3 Start watching this issue