The setting OceanUtilizeCPUs is valid for the whole cluster! This means: Any server within the data center must be equals reagrding the amount of CPUs.
The correct solution would be one setting per server. Solution: Use a own collection for this and provide a value for every server. But: If we get more settings like this (per machine instead of per data center settings), we should provide a propper solution for this. Maybe ConfigurationDB should provide a function for this e.g. ReadGlobal() and Read4Server() etc.
The setting OceanUtilizeCPUs is valid for the whole cluster! This means: Any server within the data center must be equals reagrding the amount of CPUs.
The correct solution would be one setting per server. Solution: Use a own collection for this and provide a value for every server. But: If we get more settings like this (per machine instead of per data center settings), we should provide a propper solution for this. Maybe ConfigurationDB should provide a function for this e.g. ReadGlobal() and Read4Server() etc.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The setting OceanUtilizeCPUs is valid for the whole cluster! This means: Any server within the data center must be equals reagrding the amount of CPUs.
The correct solution would be one setting per server. Solution: Use a own collection for this and provide a value for every server. But: If we get more settings like this (per machine instead of per data center settings), we should provide a propper solution for this. Maybe ConfigurationDB should provide a function for this e.g. ReadGlobal() and Read4Server() etc.
changed the description