Feature #108: Fixed-size object IDs
objid_t: load balancing infrastructure should use objid_t
Once the basic objid_t scaffolding is available (#170), the impacts on the LB infrastructure and strategies should be audited. Specifically, the load balancing database, ldb calls on the message send and delivery paths might only have an objid_t available at that point in the code. For eg look at
idx2LDobjid(). Hence, the benefits of managing all the LDB using objid_t should be evaluated / discussed. Implementation decisions should be made accordingly.
One observation is that the presence of an inversion function to obtain array index from objid_t may provide the extra data that user code has to provide to some LB strategies.
#10 Updated by Eric Mikida 4 months ago
- Status changed from Merged to In Progress
- Assignee changed from Kavitha Chandrasekar to Eric Mikida
- Priority changed from Normal to Low
- Target version changed from 6.9.0 to Unscheduled
Reopening and reassigning this because the patch maybe didn't fully address the issue. It uses a combination of 64bit ID, and Location manager ID. Worth evaluating whether we can do better.