canmove, Confirmed users
1,173
edits
Services/NodeAssignment: Difference between revisions
Jump to navigation
Jump to search
→DB Fields
(→APIs) |
|||
| Line 52: | Line 52: | ||
<br>'''Weight''' - Although it is not a direct reflection of users, it will be incremented by 1 for each user added. Services should set their weights according to how much impact they want each additional user to have to the algorithm | <br>'''Weight''' - Although it is not a direct reflection of users, it will be incremented by 1 for each user added. Services should set their weights according to how much impact they want each additional user to have to the algorithm | ||
<br>'''Capacity''' - The theoretical maximum weight to be associated with the node | <br>'''Capacity''' - The theoretical maximum weight to be associated with the node | ||
Down - a binary value indicating whether a node is down. The node service makes this available via api, but it is expected that the service itself will be regularly checking the value. Users will not be assigned to a node that has been marked as down. | <br'''Down''' - a binary value indicating whether a node is down. The node service makes this available via api, but it is expected that the service itself will be regularly checking the value. Users will not be assigned to a node that has been marked as down. | ||
<br>'''Backoff''' - a value in seconds that should be added to responses from services that support backoff. As with the down flag, services are responsble for accessing the data here and pushing it to their machines. | <br>'''Backoff''' - a value in seconds that should be added to responses from services that support backoff. As with the down flag, services are responsble for accessing the data here and pushing it to their machines. | ||
==Assignment Weighting== | ==Assignment Weighting== | ||