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

config.chunks change to config.cache.chunks creates a collection long name after upgrade

    XMLWordPrintable

    Details

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

      Description

      After upgrading from 3.4 to 3.6 I get many of these errors for different sharded collections:

      I SHARDING [ShardServerCatalogCacheLoader-4] InvalidNamespace: Failed to update the persisted chunk metadata for collection 'easypalletideas-uorzoqjxdxhndfy_stackpat_40594.easypalletideas-uorzoqjxdxhndfy_stackpat_40594_counters_hourly' from '0|0||000000000000000000000000' to '1|0||5adc9e47ed72f1e7708a691d' due to 'fully qualified namespace config.cache.chunks.easypalletideas-uorzoqjxdxhndfy_stackpat_40594.easypalletideas-uorzoqjxdxhndfy_stackpat_40594_counters_hourly is too long (max is 120 bytes)'. Will be retried.
      

      This did not happen before the upgrade.

      I suspect the issue is the change in SERVER-31644 is making the collection name too long despite the original collection being within limits.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-sharding Backlog - Sharding Team
              Reporter:
              Rybak Shay
              Participants:
              Votes:
              4 Vote for this issue
              Watchers:
              25 Start watching this issue

                Dates

                Created:
                Updated: