[SERVER-85231] ReplicationStateTransition lock Created: 16/Jan/24  Updated: 25/Jan/24  Resolved: 25/Jan/24

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.4.10
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Sanjay Sanghera Assignee: Chris Kelly
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Hi, please can you advise on why I am seeing the following lock even though I am not using replication?

 

  "locks": {
    "ReplicationStateTransition": {
      "acquireCount":

{         "w": 1235       }

 

ReplicationStateTransition accounts for 20% of the locks I am seeing on the database, is there anyway this can be switched off?



 Comments   
Comment by Chris Kelly [ 25/Jan/24 ]

Hi!

Thanks for your report! I understand it's a bit odd to see this when not running a replica set or sharded cluster deployment. However:

  • Lock usage is not indicative of an issue on its own
  • The ReplicationStateTransition (RSTL) is a precursor to acquiring the global lock, which is used by a number of other components (regardless of topology)

As such, I am going to close this ticket since this is working as designed. 

Generated at Thu Feb 08 06:57:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.