Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ignore delete events for non-existent entries #1403

Merged
merged 1 commit into from
Aug 22, 2016
Merged

Ignore delete events for non-existent entries #1403

merged 1 commit into from
Aug 22, 2016

Commits on Aug 18, 2016

  1. Ignore delete events for non-existent entries 

    In networkdb we should ignore delete events for entries which doesn't
exist in the db. This is always true because if the entry did not exist
then the entry has been removed way earlier and got purged after the
reap timer and this notification is very stale.

Also there were duplicate delete notifications being sent to the
clients. One when the actual delete event was received from gossip and
later when the entry was getting reaped. The second notification is
unnecessary and may cause issues with the clients if they are not
coded for idempotency.

Signed-off-by: Jana Radhakrishnan <[email protected]>
    @mrjana
    mrjana committed Aug 18, 2016
    Configuration menu
    Copy the full SHA
    dd3b131 View commit details
    Browse the repository at this point in the history