Actions
Bug #1852
closed
fail to register prefix if multiple producers start together
Start date:
08/12/2014
Due date:
% Done:
100%
Estimated time:
Description
Steps to reproduce:
nfd-startndnpingserver /A & ndnpingserver /B & ndnpingserver /C &
Expected: three ndnpingserver instances start normally
Actual: with high probability, two instances terminate with
ERROR: Failed to register prefix in local hub's daemon
REASON: Face not found
Suggested fix: When RibManager finds the FaceId in rib/register command is non-existent, don't reject the command right away; instead, wait 1 second so that FaceTable has a chance to be up-to-date on newly created faces.
Updated by Junxiao Shi over 9 years ago
- Blocked by Task #1832: Implement FaceTable class to monitor and track active faces added
Updated by Alex Afanasyev over 9 years ago
- Priority changed from Normal to High
Please review http://gerrit.named-data.net/#/c/1131/1
I think the current approach is not correct and prone to errors, since valid face ID in NFD is not immediately seen by NRD. Delaying registration action is not correct. I would simply ignore invalid faces in RIB (not a big deal) and deal with invalid faces in different way (will create a separate issue for that).
Updated by Alex Afanasyev over 9 years ago
- Status changed from New to Code review
- Assignee changed from Vince Lehman to Alex Afanasyev
Updated by Junxiao Shi over 9 years ago
- Target version changed from v0.3 to v0.2
- % Done changed from 0 to 100
Updated by Alex Afanasyev over 9 years ago
- Blocked by deleted (Task #1832: Implement FaceTable class to monitor and track active faces)
Updated by Alex Afanasyev over 9 years ago
- Status changed from Code review to Closed
Actions