4 ms·
This can shift complexity to elsewhere in your stack. A couple points to add. Be mindful of the specific routing hardware you're using: Announcing and withdra
by transitorykris 12y ago
This can shift complexity to elsewhere in your stack. A couple points to add.
Be mindful of the specific routing hardware you're using:
Announcing and withdrawing prefixes can cause the router to select new next hops (i.e. servers). This is mostly a problem with TCP and other connection oriented protocols (or even connectionless if you're expecting a client to be sticky to a server).
You may also lose the ability to do un-equal cost load balancing.
- yelloblac 12y agoI think that's an important catch, flow breaking can happen dependent on what hardware you're using and how you swap in next-hops. It definitely requires a deep understanding of how flows are hashed.
- phil21 12y agoAgreed. Also many applications for this you might just not care if a flow gets broken. Really depends on your use case. Persistent hashing is key if you care about it though, I honestly don't know which routers do this off the top of my head :)