Actions
Bug #4513
closed
Need to use a fixed session name for ChronoSync sockets
Start date:
02/20/2018
Due date:
% Done:
100%
Estimated time:
Description
On the testbed it was observed that ChronoSync was trying to send large size data packets.
This is because whenever NLSR restarts it starts publishing on a new user prefix (Name and Coordinate LSA prefixes) since ChronoSync appends a new session name. Other NLSR (ChronoSync) still keeps track of the old NLSR and the State increases leading to the crashes as we saw on testbed.
When NSync was used NLSR fixed the session name. When switch to ChronoSync was made, this was over looked.
Updated by Ashlesh Gawande almost 7 years ago
- Related to Bug #4140: ChronoSync sendSyncData can result in trying to send content exceeding the size of the packet added
Updated by Ashlesh Gawande almost 7 years ago
- Related to Task #2400: Determine the necessary changes to use current Chronosync as dependency added
Updated by Ashlesh Gawande over 6 years ago
- Status changed from In Progress to Closed
Actions