On 2012-03-28 00:51:41 -0700, StormByte wrote: > I've manually ran memcached with -vvv to see what actually happens > because with older version my code worked good and it does not work > now (not hitting cache never). > So I discovered the problem: By default, in my class, I setup the > expire time in 20736000 which is 5 days in seconds.
20736000 seconds are 240 days.
This is interpreted as an absolute time, so you set the expiry date to
1970-08-29.
> With that value, I always see -nuked by expire in output despite it is
> recently created!
Not surprising.
> I discovered that lowering the value, it works indeed, for example
> 9000 seconds and it then works:
> > FOUND KEY AccountData:3
> >28 sending key AccountData:3
> >28 END
>
> So does it lowered its limits in expire option (or indide memcached
> code?)
I don't think so. The limit for relative times has always been 30 days.
> Any hint to have greater expire times?
Calculate the offset correctly. For expiry times of more than 30 days,
calculate the absolute time.
hp
--
_ | Peter J. Holzer | Deprecating human carelessness and
|_|_) | Sysadmin WSR | ignorance has no successful track record.
| | | h...@hjp.at |
__/ | http://www.hjp.at/ | -- Bill Code on a...@irtf.org
signature.asc
Description: Digital signature
