blocks|key|3318900|text|我看到这些术语可以互换使用，但有不同的实现方式：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3318901|3318902|在第一个响应时发送cookie，然后在后续响应中查找它。cookie指定发送到哪个真正的服务器。|ordered-list-item|3318903|3318904|如果您必须根据请求者的IP地址支持无cookie的browsers|3318905|Partition，则很糟糕。|unordered-list-item|3318906|3318907|如果不是静态的，或者如果有许多用户通过相同的代理进入，则不好的。|offset|length|style|BOLD|3318908|如果您验证用户，则根据用户名进行分区(必须是HTTP支持的验证模式才能做到这一点)。|3318909|
|3318910|不需要状态。|3318911|3318912|允许客户端访问任何服务器(将状态发送到客户端，并让客户端将其发回)|3318913|这不是一个棘手的会议，它是一种避免不得不这样做的方法。|3318914|我怀疑sticky可能指cookie的方式，而亲和力可能在某些上下文中指#2和#3，但这不是我看到它的用法(或我自己使用它)。|3318915|entityMap^0|0|0|0|0|0|0|0|S|3|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|19|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|1B|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|1C|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1E|8|@$O|1F|P|1G|Q|R]]|9|@]|A|$]]|$1|S|3|T|5|K|7|1H|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1I|8|@]|9|@]|A|$]]|$1|W|3|X|5|K|7|1J|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1L|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|1M|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|1N|8|@]|9|@]|A|$]]|$1|15|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|16|$]]

I've seen those terms used interchangeably, but there are different ways of implementing it:

<ol>
<li>Send a cookie on the first response and then look for it on subsequent ones. The cookie says which real server to send to. 
Bad if you have to support cookie-less browsers</li>
<li>Partition based on the requester's IP address. 
Bad if it isn't static or if many come in through the same proxy.</li>
<li>If you authenticate users, partition based on user name (it has to be an HTTP supported authentication mode to do this).</li>
<li>Don't require state. 
Let clients hit any server (send state to the client and have them send it back) 
This is not a sticky session, it's a way to avoid having to do it.</li>
</ol>

I would suspect that sticky might refer to the cookie way, and that affinity might refer to #2 and #3 in some contexts, but that's not how I have seen it used (or use it myself)

blocks|key|3318818|text|正如我经常听到的负载均衡场景中使用的术语一样，它们是可以互换的。这两者都意味着，一旦会话启动，同一服务器将为该会话的所有请求提供服务。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3318819|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

As I've always heard the terms used in a load-balancing scenario, they are interchangeable. Both mean that once a session is started, the same server serves all requests for that session.

blocks|key|3318790|text|粘性会话意味着当客户端的请求进入站点时，所有其他请求都会转到初始客户端请求所访问的同一服务器。我认为会话亲和性是粘性会话的同义词。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3318791|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Sticky session means that when a request comes into a site from a client all further requests go to the same server initial client request accessed. I believe that session affinity is a synonym for sticky session.

blocks|key|339174|text|它们是一样的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|339175|这两者都意味着，当进入负载均衡器时，请求将被定向到为第一个请求提供服务的服务器(并拥有会话)。|339176|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

They are the same.

Both mean that when coming in to the load balancer, the request will be directed to the server that served the first request (and has the session).

blocks|key|338207|text|粘性会话是指将特定会话的请求路由到为该会话的第一个请求提供服务的同一物理机。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|338208|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Sticky session means to route the requests of particular session to the same physical machine who served the first request for that session.

blocks|key|339196|text|本文为我澄清了这个问题，并讨论了其他类型的负载均衡器持久性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|339197|Dave's+Thoughts:+Load+balancer+persistence+(sticky+sessions)|offset|length|339198|entityMap|0|LINK|mutability|MUTABLE|url|http://daveonsoftware.blogspot.com/2007/08/load-balancer-persistence-sticky.html^0|0|0|1O|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

This article clarifies the question for me and discusses other types of load balancer persistence.

<a href="http://daveonsoftware.blogspot.com/2007/08/load-balancer-persistence-sticky.html" rel="nofollow">Dave's Thoughts: Load balancer persistence (sticky sessions)</a>

blocks|key|339204|text|它们是同义词。完全没有区别|type|unstyled|depth|inlineStyleRanges|entityRanges|data|339205|会话/会话亲和性：|offset|length|style|BOLD|339206|用户会话与用户请求发送到的服务器之间的亲和性/粘性/联系将被保留。|339207|entityMap^0|0|0|9|0|0|X|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

They are Synonyms.
No Difference At all

Sticky Session / Session Affinity:

Affinity/Stickiness/Contact between user session and, the server to which user request is sent is retained.

blocks|key|339237|text|本文将解释不同之处：https://www.haproxy.com/blog/load-balancing-affinity-persistence-sticky-sessions-what-you-need-to-know/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|339238|此链接的主要部分：|339239|亲和性:这是当我们使用来自应用层下面的层的信息来维护对单个服务器的客户端请求时。在本例中使用客户端的IP地址。IP地址在同一会话期间可能会改变，然后连接可能会切换到不同服务器。|339240|持久性:这是我们使用应用层信息将客户端粘贴到单个服务器上的时候。在这种情况下，负载均衡器在响应中注入一些cookie，并在后续请求中使用相同cookie路由到同一服务器。|339241|sticky+session:+sticky+session是持久化维护的会话|339242|持久化比亲和性的主要优势是它更准确，但有时，持久化是不可行的(当客户端不允许cookie时，如没有cookie的浏览器)，所以我们必须依赖亲和性。|339243|使用持久性，我们的意思是，我们100%25确定用户将被重定向到单个服务器。使用关联性，我们的意思是用户可以被重定向到相同的服务器…|339244|entityMap|0|LINK|mutability|MUTABLE|url|https://www.haproxy.com/blog/load-balancing-affinity-persistence-sticky-sessions-what-you-need-to-know/^0|A|2V|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|12|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|14|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|15|8|@]|9|@]|C|$]]|$1|N|3|O|5|6|7|16|8|@]|9|@]|C|$]]|$1|P|3|-4|5|6|7|17|8|@]|9|@]|C|$]]]|Q|$R|$5|S|T|U|C|$V|W]]]]

difference is explained in this article:
<a href="https://www.haproxy.com/blog/load-balancing-affinity-persistence-sticky-sessions-what-you-need-to-know/" rel="nofollow noreferrer">https://www.haproxy.com/blog/load-balancing-affinity-persistence-sticky-sessions-what-you-need-to-know/</a>
Main part from this link:
Affinity: this is when we use an information from a layer below the application layer to maintain a client request to a single server. Client's IP address is used in this case. IP address may change during same session and then connection may switch to different server.
Persistence: this is when we use Application layer information to stick a client to a single server. In this case, loadbalancer inject some cookie in response and use same cookie in subsequent request to route to same server.
sticky session: a sticky session is a session maintained by persistence
The main advantage of the persistence over affinity is that it’s much more accurate, but sometimes, Persistence is not doable(when client dont allow cookies like cookie less browser), so we must rely on affinity.
Using persistence, we mean that we’re 100% sure that a user will get redirected to a single server.
Using affinity, we mean that the user may be redirected to the same server…

What is the difference between session affinity and sticky session in context of load balancing servers?

Difference between session affinity and sticky session?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

在负载均衡服务器环境中，会话亲和力和粘滞会话有什么区别？

问会话亲和性和粘性会话之间的区别？
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问会话亲和性和粘性会话之间的区别？EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问会话亲和性和粘性会话之间的区别？
EN