Closed Bug 598800 Opened 14 years ago Closed 13 years ago

Server needs to do proportional allocation to nodes

Categories

(Cloud Services :: Server: Registration, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: telliott, Assigned: telliott)

References

Details

(Keywords: push-needed, Whiteboard: [qa-])

Attachments

(2 files)

With the introduction of different-capacity servers, we need to assign to nodes based on a proportion of expected maximum.
I think this is actually easier than I expected. Instead of ordering by actives, we order by actives/max_capacity.

If this turns out to be too inefficient (shouldn't be with only a couple hundred rows), we can have the nightly actives update add % to a new column and order by that.

This doesn't address how we get max_capacity into available_nodes (and mandates that max_capacity is now NOT NULL). We probably need to add it to the master config file for each node.
This requires the changes in 599133 or things will break horribly
Attachment #488268 - Flags: review?(mconnor)
Depends on: 599133
Attachment #488268 - Flags: review?(mconnor) → review+
In http://hg.mozilla.org/services/reg-server/rev/45868518b54a
Status: NEW → RESOLVED
Closed: 14 years ago
Keywords: push-needed
Resolution: --- → FIXED
Whiteboard: [qa-]
Also need to do this to sreg
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
changes the select over to the reg version. Also appears to have removed a bunch of spaces.
Attachment #520900 - Flags: review?(jrconlin)
Comment on attachment 520900 [details] [diff] [review]
Uses the reg algorithm to assign nodes

Wow. loads of whitespace diffs.
Attachment #520900 - Flags: review?(jrconlin) → review+
Why this is REOPENED ?
Status: REOPENED → RESOLVED
Closed: 14 years ago13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: