After upgratde to 5.0.6 too many admin commands running in ns: admin.$cmd

I am running a 3 shard PSS cluster version 5.0.6

I just see a lot of admin comands in currentOp() taking a very long time

Something like this below.

Is this something to be concerned about ? What are these queries ?

----Current Mongosh Log ID:	622ae448844696eb9cccc338
Connecting to:		mongodb://mcfg4.netcore.co.in:27015/?directConnection=true&appName=mongosh+1.1.9
Using MongoDB:		5.0.6
Using Mongosh:		1.1.9

For mongosh info see: https://docs.mongodb.com/mongodb-shell/

{
  inprog: [
    {
      shard: 'a',
      type: 'op',
      host: 'ba4.netcore.co.in:27017',
      desc: 'conn99',
      connectionId: 99,
      client_s: '172.31.41.213:51310',
      clientMetadata: {
        driver: { name: 'NetworkInterfaceTL', version: '5.0.6' },
        os: {
          type: 'Linux',
          name: 'CentOS Linux release 7.6.1810 (Core) ',
          architecture: 'x86_64',
          version: 'Kernel 3.10.0-957.10.1.el7.x86_64'
        }
      },
      active: true,
      currentOpTime: '2022-03-11T11:27:25.848+05:30',
      effectiveUsers: [ { user: '__system', db: 'local' } ],
      threaded: true,
      opid: 'a:1501619726',
      secs_running: Long("3"),
      microsecs_running: Long("3287664"),
      op: 'command',
      ns: 'admin.$cmd',
      command: {
        isMaster: 1,
        maxAwaitTimeMS: Long("10000"),
        topologyVersion: {
          processId: ObjectId("621f2dad1e6a85c123e77b39"),
          counter: Long("9")
        },
        internalClient: { minWireVersion: 13, maxWireVersion: 13 },
        maxTimeMSOpOnly: Long("20000"),
        '$db': 'admin'
      },
      numYields: 0,
      waitingForLatch: {
        timestamp: ISODate("2022-03-11T05:57:22.661Z"),
        captureName: 'AnonymousLockable'
      },
      locks: {},
      waitingForLock: false,
      lockStats: {},
      waitingForFlowControl: false,
      flowControlStats: {}
    },
    {
      shard: 'a',
      type: 'op',
      host: 'ba4.netcore.co.in:27017',
      desc: 'conn11',
      connectionId: 11,
      client_s: '172.31.23.195:51530',
      clientMetadata: {
        driver: { name: 'NetworkInterfaceTL', version: '5.0.6' },
        os: {
          type: 'Linux',
          name: 'CentOS Linux release 7.6.1810 (Core) ',
          architecture: 'x86_64',
          version: 'Kernel 3.10.0-957.10.1.el7.x86_64'
        }
      },
      active: true,
      currentOpTime: '2022-03-11T11:27:25.848+05:30',
      effectiveUsers: [ { user: '__system', db: 'local' } ],
      threaded: true,
      opid: 'a:1501612129',
      secs_running: Long("6"),
      microsecs_running: Long("6071629"),
      op: 'command',
      ns: 'admin.$cmd',
      command: {
        isMaster: 1,
        maxAwaitTimeMS: Long("10000"),
        topologyVersion: {
          processId: ObjectId("621f2dad1e6a85c123e77b39"),
          counter: Long("9")
        },
        internalClient: { minWireVersion: 13, maxWireVersion: 13 },
        maxTimeMSOpOnly: Long("20000"),
        '$db': 'admin'
      },
      numYields: 0,
      waitingForLatch: {
        timestamp: ISODate("2022-03-11T05:57:19.877Z"),
        captureName: 'AnonymousLockable'
      },
      locks: {},
      waitingForLock: false,
      lockStats: {},

Dear,
i have the same question. my version is 5.0.4 shard cluster.
what command about isMaster will run several seconds?
db.isMaster() runs very fast.