Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 266374 - dev-php5/pecl-memcache-3.0.4 has broken memcache.session_redundancy
Summary: dev-php5/pecl-memcache-3.0.4 has broken memcache.session_redundancy
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: PHP Bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-16 13:08 UTC by Deniss Gaplevsky
Modified: 2010-04-12 15:47 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Deniss Gaplevsky 2009-04-16 13:08:49 UTC
after upgrade to dev-php5/pecl-memcache-3.0.4 session_redundancy stop work.
Looks like data is read from both servers but writes comes to only one in case of two memcached used.
http://pecl.php.net/bugs/bug.php?id=16061

Reproducible: Always

Steps to Reproduce:
1. take 2 memcached servers
2. set memcache.session_redundancy=2
3. set session.save_handler = memcache
4. set session.save_path="tcp://host1:11211,tcp://host2:11211"



Actual Results:  
only one memcached server is used to write

Expected Results:  
same data should be written to both memcached servers
Comment 1 Deniss Gaplevsky 2009-10-26 10:37:15 UTC
looks like pecl-memcache-3.0.3 has no such problem.
please add pecl-memcache-3.0.3 to portage as stable 
Comment 2 Matti Bickel (RETIRED) gentoo-dev 2010-04-12 15:47:53 UTC
Well, from the upstream bug it seems there's a workaround at least?

I don't have two memcached servers around to test, so i can't reproduce it.
But as the "stable" version is 2.2.5 (both for us and for upstream) is see no reason to mark another version stable.

Now, if you can confirm this issue exists in 2.2.5, too, this would be another thing. For 3.0.4 please push the issue upstream.

If they get back to you, please reopen this bug (I'm trying to monitor UPSTREAM bugs, but can't guarantee I'll catch it). Also please reopen if you can reproduce this with 2.2.5

Thanks a lot for your report. Sorry I couldn't do more for you.