Was this helpful?
Insufficient Slave Quota
This entry is logged during dispatcher creation if there is insufficient remaining SlaveQuota to satisfy the creation of the dispatcher and allow it to reserve its full quota of slave slots. The DispatcherMgr maintains a total of the maximum number of slaves that are allowed to exist in the SPO. Each time a new dispatcher is created, it attempts to reserve its full quota of slaves that it could ever create. If the total number of slaves would exceed the number of SlaveQuota remaining, the creation of the new dispatcher will fail.
This event appears in the log with the following format:
Timestamp   DISPATCHER NOT CREATED - INSUFFICIENT SLAVE QUOTA
             ImageFile: ImageFile
              CmdFlags: CmdFlags
             MaxSlaves: MaxSlaves
Timestamp
Identifies the event timestamp. It has the following format:
yyyy/mo/dd_hh:mi:ss.fff
yyyy
Identifies a four-digit year value
mo
Identifies a two-digit month value
dd
Identifies a two-digit day value
hh
Identifies a two-digit military hour value
mi
Identifies a two-digit minute value
ss
Identifies a two-digit second value
fff
Identifies a three-digit millisecond value
ImageFile
Identifies the OpenROAD image file that the SPO will pass to the ASO slave when it is started. If the ImageFile value starts with the character "{", then it will be treated by the ASO slave as an application signature name. The ASO slave must access the JSON configuration file to obtain the real ImageFile and CmdFlags. Otherwise, it is treated as an OpenROAD image file name.
CmdFlags
Indicates the OpenROAD command flags that the SPO will pass to the ASO slave. If the ImageFile value starts with the character "{", then this value is ignored. Otherwise, it is treated as the OpenROAD command flags that will be used to initialize the ASO slave OpenROAD runtime.
MaxSlaves
Indicates the number of slaves that were attempted to be reserved during the creation of a new dispatcher
Last modified date: 12/20/2023