Pool6 removal should cascade to the session tables #100

Closed
ydahhrk opened this Issue Jun 25, 2014 · 1 comment

Comments

Projects
None yet
2 participants
@ydahhrk
Member

ydahhrk commented Jun 25, 2014

I've been checking issue #97.

Looks like we forgot an element in the wishlist of issue #65:

  • When a IPv6 prefix is destroyed (from the IPv6 pool), its session entries should be destroyed as well (which might or might not destroy their BIB entries).

This is not really a bug; these remaining session entries currently lie in the database not doing anything until the expiration timers destroy them, but it would be nice to remove them early for the sake of consistency and performance.

Issue #97 depends on this; the flushes should probably also cascade to the BIB and session tables.

@ydahhrk ydahhrk added this to the 3.2.0 milestone Jun 25, 2014

@ydahhrk ydahhrk added the Performance label Jun 25, 2014

@ydahhrk ydahhrk referenced this issue Jun 25, 2014

Merged

Feature/flush #97

@ydahhrk

This comment has been minimized.

Show comment
Hide comment
@ydahhrk

ydahhrk Sep 4, 2014

Member

Added and collapsed to the master branch; closing.

Member

ydahhrk commented Sep 4, 2014

Added and collapsed to the master branch; closing.

@ydahhrk ydahhrk closed this Sep 4, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment