Skip to content

Load balancer appcookie configuration deprecated in HAproxy #3253

Description

@DagSonsteboSB
ISSUE TYPE
  • Improvement Request
COMPONENT NAME
  • ACS 4.11.x VR load balancing with AppCookie stickiness
CLOUDSTACK VERSION
  • ACS 4.11.x
CONFIGURATION
  • Advanced zone, guest isolated network with LB configuration on public IP
OS / ENVIRONMENT
  • N/A
SUMMARY
STEPS TO REPRODUCE
  • Create new LB rule with AppCookie stickiness
  • Observe haproxy logs on VR stating:
    03:59:09 r-1667-VM haproxy[40552]: [ALERT] 090/035909 (40552) : parsing [/etc/haproxy/haproxy.cfg:38] : 'appsession' is not supported anymore, please check the documentation.
EXPECTED RESULTS
  • N/A
ACTUAL RESULTS
  • Error as above

Activity

added this to the 4.13.0.0 milestone on May 27, 2019

yadvr commented on Jul 3, 2019

@yadvr
Member

The appcookie feature was primary driven by the netscalar implementation (if I recall correctly). Per the haproxy docs As of version 1.6, appsessions was removed. It is more flexible and more convenient to use stick-tables instead, and stick-tables support multi-master replication and data conservation across reloads, which appsessions did not.. We can explore if an upgrade path is possible.

The LB feature needs some overall cleanup and fixing, other than the tcp round-robin (most preferred use-case), SSL off loading etc don't work, as they were primarily netscalar driven in the past. cc @PaulAngus

modified the milestones: 4.13.0.0, 4.14.0.0 on Jul 3, 2019
modified the milestones: 4.15.0.0, 4.16.0.0 on Oct 29, 2020
modified the milestones: 4.16.0.0, unplanned on Jul 27, 2021

DaanHoogland commented on May 2, 2025

@DaanHoogland
Contributor

closing this as unplanned, please reopen if applicable

weizhouapache commented on May 26, 2026

@weizhouapache
Member

we faced an issue with appsession today

Image

therefore I reopened this issue.
appsession should be removed from cloudstack source code (java, UI, etc) and documentation.

github-actions commented on Oct 4, 2026

@github-actions

This issue is stale because it has been open for 120 days with no activity. It may be removed by administrators of this project at any time. Remove the stale label or comment to request for removal of it to prevent this.

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions