Killed by SIGPIPE using Memcached::libmemcached

script It will show something like: Hit: 1660. Miss: 340. Total: 2000 -- Bill Moseley [EMAIL PROTECTED] Sent from my iMutt

Detecting failed memcached servers

not really related to the method above. Thanks, -- Bill Moseley [EMAIL PROTECTED] Sent from my iMutt

Re: Detecting failed memcached servers

On Thu, Dec 11, 2008 at 05:15:58PM +0100, Henrik Schröder wrote: On Thu, Dec 11, 2008 at 15:44, Bill Moseley mose...@hank.org wrote: Assuming we have a good reason for using the cache in the first place, then a failed server isn't doing us any good in the server list. So, the question

Re: facebook memcached

the application design that uses *hundreds* of gets in parallel. Is that per web request? I typically have just a few fetches per request, and they don't happen in parallel -- in my code there isn't one place that knows about everything that needs to be fetched at at once. -- Bill Moseley mose

updating expires on read

to set a very long expires on the item and a short expires on the cache item that tracks the real expires time? IIRC, memcached will toss out expired items first, then items w/o an expires time when memory is needed. Are there stats that will show the difference? Thanks, -- Bill Moseley mose

Read expires?

is not needed? Thanks, -- Bill Moseley mose...@hank.org

Re: undefined reference to `__sync_fetch_and_add_4

:yes * Debug enabled: no * Warnings as failure: no -- Bill Moseley mose...@hank.org

Repopulating cache after cache miss.

occur. My concern is that the client may make multiple requests for additional parts at the same time triggering multiple (duplicate) re-fetches and saves. Anyone have a similar situation? Would you recommend use an atomic add with a short timeout as a lock? Thanks, -- Bill Moseley mose

Session store

and highly available, yet fast and scalable session store for a high traffic site. Combine the two clusters into a single cluster and use Mysql and replication? Memcachedb? -- Bill Moseley mose...@hank.org

libmemcache: memcached_behavior_number_of_replicas working?

at poor-man's HA with these two features. Looking at how pulling the plug on one server won't result in get or set failures, and not an increased amount of time (say waiting for a failed server to respond). -- Bill Moseley mose...@hank.org

Re: libmemcache: memcached_behavior_number_of_replicas working?

= key 441 = found in mem1 = key 178 = found in mem1 One thing I always find odd is if I don't have Memcached running I get: set failed SYSTEM ERROR Success' Does that mean a successful system error? ;) -- Bill Moseley mose...@hank.org

Re: libmemcache: memcached_behavior_number_of_replicas working?

. This allows distributing read load to multiple servers with the expense of more write traffic. -- Bill Moseley mose...@hank.org

Timeouts (and out of memory)

chance the timeouts are somehow related? -- Bill Moseley mose...@hank.org -- --- You received this message because you are subscribed to the Google Groups memcached group. To unsubscribe from this group and stop receiving emails from it, send an email to memcached+unsubscr...@googlegroups.com

Re: SERVER_ERROR out of memory storing object

either under dev. But, I have a lot more testing to do. The timeouts on production are a much bigger concern at this time. Thanks, -- Bill Moseley mose...@hank.org -- --- You received this message because you are subscribed to the Google Groups memcached group. To unsubscribe from

Re: Timeouts (and out of memory)

in this poll call: if ((number_of= poll(fds, 1, server-root-connect_timeout)) == -1) That is returning zero and connect_timeout is 4000ms. But, that's a much more rare type of timeout. On Tue, Oct 1, 2013 at 3:41 PM, Bill Moseley mose...@hank.org wrote: Just a quick follow up on this timeout

Re: Evictions before expires.

9 STAT items:40:evicted 69 STAT items:40:evicted_nonzero 69 STAT items:40:evicted_time 3446 STAT items:41:number 25 STAT items:41:age 12029015 STAT items:41:evicted 5911 STAT items:41:evicted_nonzero 5911 STAT items:41:evicted_time 3592 STAT items:42:number 42 STAT items:42:age 12028792 STAT it

Re: Evictions before expires.

lass 3, which > has 5 pages assigned. Meanwhile slab class 2 has 5000 pages and never > evicts. > > 1.4.4 isn't supported, so if you continue to have trouble I highly > recommend trying the new code (and start options) first. > > -Dormando > > On Wed, 9 Dec 2015, Bill Moseley

Client timeout recommendations?

connection. We use libmemcached and have the MEMCACHED_BEHAVIOR_POLL_TIMEOUT set to 4 seconds. The web code didn't have a circuit breaker so you can imagine how well that went. Short of the whacky setup, just wondering what client timeout are commonly used. -- Bill Moseley mose..

evicted_time

. VERSION 1.4.25 -- Bill Moseley mose...@hank.org -- --- You received this message because you are subscribed to the Google Groups "memcached" group. To unsubscribe from this group and stop receiving emails from it, send an email to memcached+unsubscr...@googlegroups.com. For mo

Re: evicted_time

ng -I and do the chunking into parts (and maybe gzipping) in the client before storing. So, we store one or more 1mb items and then the remainder in another chunk based on its size. If we use new large item support all of the split-up parts of the item we are storing end up in the same chunk. Does that mean

Re: evicted_time

page so that the page can be reclaimed? Or do all items in a given page first need to expire before it can be reclaimed? On Fri, Nov 11, 2016 at 10:44 PM, Bill Moseley <mose...@hank.org> wrote: > > > On Thu, Oct 13, 2016 at 11:32 PM, dormando <dorma...@rydia.net>

Re: evicted_time

emcached as a general cache so our value sizes and set frequency varies quite a bit. I suspect being able to reallocate slab space would be helpful in our case. We also have a need to store some larger (>1MB) items, too. (for example, -I 4m) Thanks, > > On Sun, 25 Sep 2016,