1.2.6 to 1.2.8 or 1.4.0?

[Jay Paroline]

Hello,
We've been having some intermittent memcached connection issues and I
noticed that we are a couple of releases behind. Our current version
is 1.2.6.

Before I nag our admin about upgrading, is there any reason why it
might be more wise to go to 1.2.8 rather than make the leap to 1.4.0?

FWIW the clients we use are PHP primarily and a couple of lower
traffic Java apps. Should 1.4.0 work with any clients that were
working with 1.2.6?

Thanks!

Jay

[Matt Ingenthron]

Jay Paroline wrote:
> Hello,
> We've been having some intermittent memcached connection issues and I
> noticed that we are a couple of releases behind. Our current version
> is 1.2.6.
>
> Before I nag our admin about upgrading, is there any reason why it
> might be more wise to go to 1.2.8 rather than make the leap to 1.4.0?
>

1.4.0 is in production in some large sites (as was 1.3) and it does have
some miles on it. Whether you make the move to 1.4 or not is very
subjective to environment, etc. but I'd say if you're going to make the
move going to 1.4.0 gives you a few more client options, and that side
of things likely iterates faster. I'm personally a fan of more options.

I have to say, I don't think going to 1.2.8 or 1.4.0 has anything which
will help with connection issues... but then I don't really know what
your issues are.

> FWIW the clients we use are PHP primarily and a couple of lower
> traffic Java apps. Should 1.4.0 work with any clients that were
> working with 1.2.6?
>

Yes, 1.4.0 should support all of your clients which are working with
1.2.6. As aforementioned, there are clients which give you features
only available with 1.4.0, but the 1.4.0 server is backward compatible
with existing clients.

Hope that helps,

- Matt

[Adam Lee]

We upgraded to 1.4 in production recently and it's been great.  No problems whatsoever and it's a bit faster (thanks to threading and concurrency fixes).

--
awl

[Jay Paroline]

Thanks, that's exactly what I was hoping to hear. :) Well, except for
the part where it might not resolve our connection issues.
But all I'm getting from the PHP extension's failure callback is a
notice that the connection failed, with no debug info. STAT uptime
shows that it hasn't been crashing/restarting or anything like that
and some of the connection errors have been on the same host that the
PHP was running on, so I don't think it's a network issue (also: no
DNS is involved)... Anyway I'll still have them upgrade us to 1.4.0
before begging for help. :)

Jay