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

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.6.4
    • Component/s: Sharding
    • Labels:
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • Sharding 2018-05-21, Sharding 2018-06-04, Sharding 2018-06-18, Sharding 2018-07-02, Sharding 2018-07-16, Sharding 2018-07-30, Sharding 2018-08-13, Sharding EMEA 2021-06-14, Sharding EMEA 2021-06-28, Sharding EMEA 2021-07-12
    • 0

      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.

            Assignee:
            backlog-server-catalog-and-routing [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            Rybak Shay
            Votes:
            4 Vote for this issue
            Watchers:
            32 Start watching this issue

              Created:
              Updated: