hi list.
we are trying to migrate from Cache::Memcached to
Cache::Memcached::Fast and we get 2 issues.
the issue one is:
even I use "Namespace1" as the Cache::Memcached namespace and
"NameSpace2" as the ::Fast namespace, I'm still confused to get
strange results from some keys
like one key, it sh
On Nov 30, 4:53 pm, Fayland Lam wrote:
> hi list.
>
> we are trying to migrate from Cache::Memcached to
> Cache::Memcached::Fast and we get 2 issues.
>
> the issue one is:
> even I use "Namespace1" as the Cache::Memcached namespace and
> "NameSpace2" as the ::Fast namespace, I'm still confused t
Can you post code samples (constructors, queries)? Running memcached
with -vvv may also shed the light.
Fedora 12 updates-testing has this revision available now.
On Thu, Nov 26, 2009 at 10:45 PM, dormando wrote:
> New stable release 1.4.4 is up at http://memcached.org/
>
> Release notes are available at
> http://code.google.com/p/memcached/wiki/ReleaseNotes144
>
> This release is a minor bugfix r
Hello,
I have four memcached machines in a cluster and am using the standard
PHP 5.2.6 PECL client. I was under the impression that each object
should only be stored on one memcached server but I am seeing a key
stored on 2 or 3 different servers. I found an open issue on the PECL
bug page(http:
Its an issue with the PECL release. Not sure if they ever fixed it but
the PHP PECL lib had problems with consistently picking the same
memcached instance to set/get the object from. Resulting in the same
key being on more then 1 instance.
On Mon, Nov 30, 2009 at 10:57 AM, redmike wrote:
> Hello,
Comment #6 on issue 82 by mailsort: run multiple instances of memcached on
one server host
http://code.google.com/p/memcached/issues/detail?id=82
I have 6 memcache servers running on my vps with different ports since
1.4.0. This
is not a defect but your solution is elegant.
--
You receiv
