CLI config mode is blocked whenever there is a commit going on in another CLI session

CDB and CDB API
1

Hi,

unable to enter into config mode whenever there is a commit which is in progress in another session.
the commit is at " cdb: switch to new running… ok (0.004 s)" and the backend apps takes around 5mins to consume and configure the down layers as part of the commit notification, during this time none of the other sessions are able to get into the config mode or execute show configuration/abort/exit commands if they are already in the config mode.
the commit was performed in config terminal mode.
i tried reproducing this using cdb_subscription/iter_c by putting a sleep in iter function but there it does not block the config mode from other sessions.

once the commit is done, the blocked commands returns successfully.

what could be the reason for this ?

user sessions:
  sessionId=46 2025-04-26 09:36:24 root@10.9.156.247 cli/ssh
       no locks set
       transactions:
          tid=550 db=cs_trans mode=read_write
          tid=549 db=candidate mode=read_write
          tid=367 db=running mode=read

  sessionId=57 2025-04-26 10:56:17 root@10.15.1.81 cli/ssh
       no locks set
       transaction tid=594 has the trans lock on running
 transactions:
          tid=594 db=running mode=read_write
          tid=598 db=cs_trans mode=read_write
          tid=593 db=candidate mode=read_write
          tid=553 db=running mode=read

  sessionId=61 2025-04-26 10:56:38 root@10.15.1.81 cli/ssh
       no locks set
       transactions:
          tid=574 db=running mode=read


system sessions:
  sessionId=1 2025-04-26 08:49:31 system@0.0.0.0 system/system
       no locks set
       transactions:
          tid=603 db=pre_commit_running mode=read

  sessionId=5 2025-04-26 08:49:50 system@0.0.0.0 system/system
       no locks set
       transactions:
          tid=2 db=running mode=read

  sessionId=9 2025-04-26 08:49:50 system@0.0.0.0 system/system
       no locks set
       transactions:
          tid=595 db=running mode=read

  sessionId=10 2025-04-26 08:49:51 system@0.0.0.0 system/system
       no locks set
       no transactions
  sessionId=65 2025-04-26 11:11:34 system@127.0.0.1 system/tcp src/_maapi.c:325
       no locks set
       transactions:
          tid=604 db=candidate mode=read src/_maapi.c:1180
2

After adding the following settings in confd.conf i could reproduce the problem in cdb_subscription/iter_c as well.

<candidate>
      <enabled>true</enabled>
      <implementation>confd</implementation>
      <storage>auto</storage>
      <filename>/var/confd/candidate/candidate.db</filename>
      <confirmedCommit>
        <revertByCommit>true</revertByCommit>
      </confirmedCommit>
    </candidate>

    <running>
      <access>writable-through-candidate</access>
    </running>

is this behavior expected ?