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

Cluster upgrade from 2.6.9 to 3.0.3 error: no such cmd: _getUserCacheGeneration

XMLWordPrintableJSON

    • Type: Icon: Question Question
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.0.3
    • Component/s: Admin, Sharding
    • Labels:
      None

      We have followed upgrade procedure for sharded cluster from 2.6 to 3.0. After successful upgrading of cluster's meta data, we have upgraded one of our mongos processes and started frequently (few per minute) seeing the following errors:

      2015-05-26T10:50:44.622+0200 I NETWORK [UserCacheInvalidator] scoped connection to mongo1:27019,mongo2:27019,mongo3:27019 not being returned to the pool
      2015-05-26T10:50:44.622+0200 W ACCESS [UserCacheInvalidator] An error occurred while fetching current user cache generation to check if user cache needs invalidation: Location13053 help failed: { ok: 0.0, errmsg: "no such cmd: _getUserCacheGeneration", code: 59, bad cmd:

      { _getUserCacheGeneration: "1", help: 1 }

      }

      Are those erros something we should worry about? Can we proceed with the upgrade?

        1. mongos_startup_log
          106 kB

            Assignee:
            Unassigned Unassigned
            Reporter:
            marcin.lipiec@nokaut.pl Marcin Lipiec
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: