blocks|key|555988|text|您需要设置memcache以在其中一个服务器上运行，并让所有服务器为会话使用相同的memcache实例。否则，如果它们各自运行自己的memcache实例，您将遇到与前面相同的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|555989|除了相应地配置memcache并告诉PHP使用它作为会话处理程序之外，您不应该对代码进行任何更改。|555990|~|555991|为了澄清我在这里给出的建议，如果将所有三个服务器分组到一个池中，那么只要每个PHP实例以相同的顺序引用这些服务器，就不会有任何问题。memcache使用客户端散列，因此可以保证在同一台服务器上读取/写入相同的密钥。当然，如果您以任何方式更改该列表，则会话将变得无效。|offset|length|555992|memcache开发人员甚至不建议您使用memcache来存储会话数据，因为它不是持久的，因此，如果您必须重新启动memcache+(或者发生了什么事情)，那么您的所有用户都将被注销。|555993|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.oracle.com/cd/E17952_01/refman-5.0-en/ha-memcached-using-hashtypes.html^0|0|0|0|24|5|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$H|X|I|Y|1|Z]]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

You would need to set up memcache to run on one of the servers and have all of the servers use that same memcache instance for the sessions. Otherwise, if they each run their own memcache instance, you'll have the same problem as before.

Other than configuring memcache accordingly and telling PHP to use it as your session handler, you shouldn't have to make any changes to your code.

~

To clarify the advice I gave here, if you group all three servers into a single pool, you won't have any problems as long as every PHP instance references those servers in the same order. memcache uses <a href="http://docs.oracle.com/cd/E17952_01/refman-5.0-en/ha-memcached-using-hashtypes.html" rel="nofollow">client side hashing</a>, so you will be guaranteed that the same key is read / written on the same server. Of course, if you alter that list in any way, then sessions will become invalidated.

The memcache developers actually don't even recommend that you use memcache for storing session data because it isn't persistent, and thus if you have to restart memcache (or something happens), then all of your users will be logged out.

blocks|key|1754037|text|两个主要的memcache+PECL扩展都有会话处理程序。这两种方法都要求您在使用前安装PECL模块。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1754038|模缓存+PECL扩展会话处理程序在php.ini中启用了以下功能：|offset|length|1754039|session.save_handler+=+"memcache"
session.save_path+=+"tcp://memcacheServerAddressHere:11211?persistent=1&weight=2&timeout=2&retry_interval=10"|code-block|syntax|javascript|1754040|梅卡奇+PECL扩展会话处理程序在php.ini中启用了以下功能：|1754041|session.save_handler+=+"memcached"
session.save_path+=+"memcacheServerAddressHere:11211"|1754042|注意，Memcache扩展似乎允许对Memcache环境进行更多的配置。|1754043|entityMap|0|LINK|mutability|MUTABLE|url|http://php.net/manual/en/book.memcache.php|1|http://php.net/manual/en/book.memcached.php^0|0|0|3|0|0|0|0|3|1|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@$D|12|E|13|1|14]]|A|$]]|$1|F|3|G|5|H|7|15|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|16|8|@]|9|@$D|17|E|18|1|19]]|A|$]]|$1|M|3|N|5|H|7|1A|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|1B|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]|Y|$5|T|U|V|A|$W|Z]]]]

Both of the major memcache PHP PECL extensions have session handlers. Either will require you to install a PECL module before use.

The <a href="http://php.net/manual/en/book.memcache.php" rel="noreferrer">Memcache</a> PECL extension session handler is enabled with the following in php.ini:

<pre><code>session.save_handler = "memcache"
session.save_path = "tcp://memcacheServerAddressHere:11211?persistent=1&amp;weight=2&amp;timeout=2&amp;retry_interval=10"
</code></pre>

The <a href="http://php.net/manual/en/book.memcached.php" rel="noreferrer">Memcached</a> PECL extension session handler is enabled with the following in php.ini:

<pre><code>session.save_handler = "memcached"
session.save_path = "memcacheServerAddressHere:11211"
</code></pre>

Note that the Memcache extension appears to allow more configuration of the Memcache environment.

blocks|key|1754048|text|你要小心做这个。需要注意的一件事是不要将会话信息与其他非会话数据一起托管。当缓存只包含您自己站点的数据时，清除缓存并不是最大的事情，但是您不想将人们的会话与其一起删除。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1754049|只要您在memcache中使用相同的密钥，每次都应该访问同一台服务器。所以这个问题应该解决了。|1754050|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|$]]

You want to be careful about doing this. One thing to be careful about is to not host session info with other non-session data. It isn't the biggest deal to clear your cache when it only contains your own site's data but you do not want to wipe out people's sessions along with it.

As long as your are using the same key with memcache you should hit the same server every time. So that issue should go away.

blocks|key|556119|text|问题有两部分：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|556120|如何处理发送到不同服务器的请求？|556121|这取决于您的负载平衡器/反向代理。让客户端固定在一台服务器上是很常见的，通常是通过IP地址或代理设置的透明cookie。但是，如果您有一个分布式会话存储，则不需要为了会话而具有客户端的粘性，这就给我们带来了memcache。|556122|如何将memcache用于多台服务器上的会话存储？|556123|memcache有一个适当的共享-无分布式架构，所以大部分的智能都在客户端。因此，您应该继续使用memcache会话存储，但不要指向一个服务器，而是将其指向它们的所有。这是关于在医生里的。在您的php.ini中，您应该将session.save_path设置为memcached服务器列表，例如server1:11211,+server2:11211。|offset|length|style|CODE|556124|请注意，PHP中有两个不同的memcache客户端库，称为memcache和memcached，它们对此属性具有不同的语法。|556125|由于memcache的工作方式，您不关心会话数据存储在哪里--它是为您处理的。|556126|正如NathanD所指出的，memcache是易失性的，在重新启动时会丢失数据，当您有多个服务器时，这意味着如果重新启动某个用户(但不是所有用户)将被注销。如果一台服务器完全死亡，您的会话存储将保持工作状态。会话数据位于死服务器上的用户将被启动，但他们可以在不存在该服务器的情况下重新登录并继续进行。|556127|entityMap|0|LINK|mutability|MUTABLE|url|http://www.php.net/manual/en/memcached.sessions.php^0|0|0|0|0|43|S|2G|4|0|0|T|8|12|9|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|14|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|15|8|@$J|16|K|17|L|M]]|9|@$J|18|K|19|1|1A]]|A|$]]|$1|N|3|O|5|6|7|1B|8|@$J|1C|K|1D|L|M]|$J|1E|K|1F|L|M]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1G|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1H|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10]]]]

There are two parts to the question:
<h1>How to deal with requests going to different servers?</h1>
This is down to your load balancer/reverse-proxy. It's common to make clients stick to one server, usually by IP address or a transparent cookie set by the proxy. However, it's not necessary to have client stickiness for the sake of sessions if you have a distributed session store, which brings us to memcache.
<h1>How to use memcache for session storage on multiple servers?</h1>
memcache has a proper shared-nothing distributed architecture, so most of the intelligence is at the client end. So what you should do is go ahead and use the memcache session storage, but instead of pointing at one server, point it at ALL of them. This is covered <a href="http://www.php.net/manual/en/memcached.sessions.php" rel="noreferrer">in the docs</a>. In your php.ini you should set session.save_path to the list of memcached servers, for example <code>server1:11211, server2:11211</code>.
Be aware that there are two distinct memcache client libraries available in PHP called <code>memcache</code> and <code>memcached</code> and they have different syntax for this property.
Because of the way that memcache works, you don't care where your session data is stored - it's taken care of for you.
As NathanD points out, memcache is volatile and loses data on a restart, and when you have multiple servers this would mean that some (but not all) of your users would be logged out if one was restarted. If one server dies completely your session storage will stay working. Users whose session data was on the dead server will be kicked off, but they can log back in and carry on without that server being present.

blocks|key|2109295|text|最好使用梅卡切特b作为memcache本身的持久存储，甚至使用我强烈推荐的更智能的redis+(在您的情况下)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2109296|entityMap|0|LINK|mutability|MUTABLE|url|http://memcachedb.org/^0|4|5|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

it is better to use <a href="http://memcachedb.org/" rel="nofollow">memcachedb</a> as a persistent storage for memcache itself or even to use the more smarter redis which I highly recommend in your case

blocks|key|2109302|text|还可以将会话写入SQL+DB。这还将为您提供跨服务器的持久会话。参见下面的教程：http://culttt.com/2013/02/04/how-to-save-php-sessions-to-a-database/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2109303|如果您坚持在memcached中运行会话(为了获得更好的性能，但更低的一致性)，您可以在几个地方重写他的代码。|2109304|entityMap|0|LINK|mutability|MUTABLE|url|http://culttt.com/2013/02/04/how-to-save-php-sessions-to-a-database/^0|14|1W|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

You can also write your sessions to a SQL DB. This will also give you persistent sessions across servers. See the tutorial below: <a href="http://culttt.com/2013/02/04/how-to-save-php-sessions-to-a-database/" rel="nofollow">http://culttt.com/2013/02/04/how-to-save-php-sessions-to-a-database/</a> 

If you insist on running the sessions in memcached (in order to have better performance, but lower consistency) you can simply rewrite his code in a couple of places

blocks|key|1754240|text|您也可以同步基于文件的会话。我在两个负载均衡的服务器上做的。在Ubuntu和许多其他Linuxes上，会话存储在/var/lib/php5中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1754241|我遵循这里是超级用户步骤，将PHP文件夹从另一个服务器上挂载。|1754242|entityMap|0|LINK|mutability|MUTABLE|url|https://superuser.com/questions/300662/how-to-mount-a-folder-from-a-linux-machine-on-another-linux-machine/300703#300703^0|1K|D|0|3|7|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@]|D|@$9|T|A|U|1|V]]|E|$]]|$1|H|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

You can sync file-based sessions too. I do it on my two load-balanced servers.
On Ubuntu and a bunch of other Linuxes, sessions are stored in <code>/var/lib/php5</code>.

I followed the steps <a href="https://superuser.com/questions/300662/how-to-mount-a-folder-from-a-linux-machine-on-another-linux-machine/300703#300703">over here on Superuser</a>, mounting the PHP session folder from one server on the other.

I currently have a huge problem. Two days ago my site running on one server was too much, so I purchased two more and had them clustered (rsync and load balanced).

I then start noticing that a user would hit server-1 and then on the next request hit server3 but that their session was still on server1 instead of server3 and they were no longer logged in. 

I was recommended to use memcache for session stores. 

My script already uses <code>$_SESSION</code>. 

<ul>
<li>Can we get memcache installed and enable session handler support and set <code>session.save_handler = "memcache"</code> to force php to use memcache? </li>
<li>Is there any application programming that needs to be done to use memcache? </li>
<li>Will this solve my session between server issue? </li>
<li>Are the session stores stored on all the servers when they are created or is one like a master memcache server? </li>
</ul>

I'm using the codeiginiter framework

Using memcache as a session store?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我现在有个大问题。两天前，我的站点在一台服务器上运行得太多了，所以我又购买了两台，并让它们集群(rsync和load balanced)。然后，我开始注意到，用户将访问服务器-1，然后在下一个请求中访问server3，但是他们的会话仍然在server1上而不是server3上，并且他们不再登录。建议我将memcache...

问使用memcache作为会话存储？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用memcache作为会话存储？EN