# Sticky Session / Session Persistence

**URL:** <https://discourse.haproxy.org/t/sticky-session-session-persistence/1976>\
**Category:** Help!\
**Created:** [January 11, 2018, 8:47am UTC](https://discourse.haproxy.org/t/sticky-session-session-persistence/1976 "2018-01-11T08:47:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DevendraJoshi](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.haproxy.org/devendrajoshi/32/309_2.png) [@DevendraJoshi](https://discourse.haproxy.org/u/DevendraJoshi)\
**Post date:** [January 11, 2018, 8:47am UTC](https://discourse.haproxy.org/t/sticky-session-session-persistence/1976/1 "2018-01-11T08:47:57Z")

</div>

Hi,  
I have two back-end and i am using Round-Robin to load balance.  
I want to configure Haproxy like, If my one back-end\_1 goes down, the traffic of back-end\_1 will keep on same back-end\_1, whether it is down. it should not route on back-end\_2. and show some error for those user who are on back-end\_1.

and back-end\_2 is working and all new traffic will serve by back-end\_2.

can we do that ?

---

<div class="post-metadata">

**Author:** ![AaronWest](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.haproxy.org/aaronwest/32/164_2.png) [@AaronWest](https://discourse.haproxy.org/u/AaronWest)\
**Post date:** [January 11, 2018, 2:50pm UTC](https://discourse.haproxy.org/t/sticky-session-session-persistence/1976/2 "2018-01-11T14:50:12Z")

</div>

What sort of persistence are you using because if using cookie persistence with “option redispacth” disabled I think it should be unable to break persistence and just throw an error to the user:

[https://cbonte.github.io/haproxy-dconv/1.7/configuration.html#4.2-no%20option%20redispatch](https://cbonte.github.io/haproxy-dconv/1.7/configuration.html#4.2-no%20option%20redispatch)