Database operation impact on parallel installing plugin or unrelated update sets.

[siva krishna M2]

ServiceNow creates a record with name "Update-Mutex" in sys_mutex table to lock the instance to restrict doing other plugin installations/update set retrieval/ update set implementation

If Admin user deletes this record and start doing another plugin installation or update set installation. What will be the impact on database operations?

Why there is no restriction in deletion of the record "Update-Mutex" in sys_mutex table if one plugin installation or update set installation is going on sys_progress_worker table?

[Maik Skoddow]

Hi @siva krishna M2 

If you're manipulating records in one of the most critical ServiceNow tables, what do you expect?

There is a reason why only one plugin installation is allowed at a certain time. It's a heavy process which might load many thousands of records into the system. And therefore this should be influenced by another running plugin installation.

Maik

[siva krishna M2]

Yes, Maik understood.

My question is why delete access for this  "Update-Mutex" record in sys_mutex table is provided to the admin. why this record is not placed as in read only protected mode. I want to know if there is any particular reason for providing delete access to admin so that i can understand in which scenarios we can install update sets or plugins parallely?

My second question is why there is sequential update on newly added dictionary fields which has default values/Boolean values to the existing records in the database of the table. Is there any way to make them update parallelly to the database while committing update sets if two newly created dictionary fields are independent to each other?