Project

General

Profile

Story #4650

Allow MN to bias resolve to the authoritative MN

Added by Bruce Wilson over 10 years ago. Updated almost 7 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
d1_cn_common
Target version:
-
Start date:
Due date:
% Done:

0%

Story Points:
Sprint:

Description

In the MN workshop (IDCC, Feb 2014) and in a MN forum discussion, several MN's asked if the resolve could be biased so that the authoritative MN was the somehow biased, so that users would be more likely to retrieve the data from the authoritative MN. A suggestion that met with a very positive response was to ensure that CN.resolve() returns the authoritative MN as the first item in the list. My understanding is that the order in the CN.resolve() results is indeterminate.

History

#1 Updated by Matthew Jones over 10 years ago

Although it is currently indeterminate, we have plans to use the ordering as a mechanism to help with load-balancing. We had originally discussed using an algorithm that considers which nodes are up as well as available network connectivity and server load to order the resolve() list. So, I wouldn't want to necessarily commit to always listing the authoritative MN first given these plans.

#2 Updated by Dave Vieglais almost 7 years ago

  • Assignee set to Rob Nahf

#3 Updated by Dave Vieglais almost 7 years ago

  • Sprint set to CCI-2.3.8

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)