Go/Ocean
Go/Ocean
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

OceanUtilizeCPUs: One setting for the whole cluster #17

New Issue
Closed
opened 2014-06-06 08:15:40 +00:00 by thorsten · 1 comment
thorsten commented 2014-06-06 08:15:40 +00:00 (Migrated from devops.tsommer.org)
Copy Link

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.
thorsten commented 2022-04-23 15:34:02 +00:00 (Migrated from devops.tsommer.org)
Copy Link

changed the description

changed the description
thorsten (Migrated from devops.tsommer.org) closed this issue 2022-04-23 15:34:02 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
bug

   
change

   
check

   
Comp::Backend

   
Comp::Database

   
Comp::ICCC

   
Comp::Logging

   
Comp::Sessions

   
Comp::System

   
Comp::Users

   
enhancement

   
note

   
outdated

Outdated since Ocean is no longer maintained

  
question

   
Ready2Test

   
security

   
todo

   
wontfix
No Label
bug
change
check
Comp::Backend
Comp::Database
Comp::ICCC
Comp::Logging
Comp::Sessions
Comp::System
Comp::Users
enhancement
note
outdated
question
Ready2Test
security
todo
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Go/Ocean#17
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?