Updates:
Status: Fixed
Comment #1 on issue 79 by trond.norbye: Buffer overrun in prefix stats
http://code.google.com/p/memcached/issues/detail?id=79
Pushed
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
Yo
On Aug 19, 10:36 pm, Jay Paroline wrote:
> Actually if anyone can provide hints about existing memcached
> replication solutions, especially for php, that would make me very
> happy. We have some keys that are very expensive to regenerate when
> they fall out of memcached, so losing a bucket due
Actually if anyone can provide hints about existing memcached
replication solutions, especially for php, that would make me very
happy. We have some keys that are very expensive to regenerate when
they fall out of memcached, so losing a bucket due to server failure,
maintenance, etc. is very painf
On Aug 19, 4:00 pm, Syed Ali wrote:
> Hi Guys
>
> I thinks its a bit overwhelming to receive notifications of each commit.
>
> Would it be possible to turn 'em off?
While I hope it can remain annoying enough to warrant a change, I
think today is a bit unusual as we're trying to close up some
I'm just fine with them being on there.
It gives much more visibility into the things being done to the code base.
I vote for leaving them turned on..
On Thu, Aug 20, 2009 at 7:00 AM, Syed Ali wrote:
>
> Hi Guys
>
> I thinks its a bit overwhelming to receive notifications of each commit.
>
> Wo
Status: Accepted
Owner: trond.norbye
Labels: Type-Defect Priority-Medium
New issue 79 by dsallings: Buffer overrun in prefix stats
http://code.google.com/p/memcached/issues/detail?id=79
This was causing build failures on OpenBSD, but nowhere else. Apparently
there actually was a wolf.
--
You
Hi Guys
I thinks its a bit overwhelming to receive notifications of each commit.
Would it be possible to turn 'em off?
Syed
Ps: we can still subscribe to individual alerts and defects if needed
--
--
-Syed Ali
Comment #1 on issue 77 by dsallings: Spurious failures on the OpenBSD
builder
http://code.google.com/p/memcached/issues/detail?id=77
The second part was a real problem, moving to a separate bug.
--
You received this message because you are listed in the owner
or CC fields of this issue, or
Updates:
Status: WontFix
Comment #5 on issue 58 by trond.norbye: Use specialized clock thread
http://code.google.com/p/memcached/issues/detail?id=58
Nah.. the timers is only used by the thread accepting new clients so it's
not a big problem...
--
You received this message because yo
Updates:
Status: Fixed
Cc: dsallings trond.norbye
Comment #1 on issue 78 by ingenthr: DTrace probes return types could be
better documented
http://code.google.com/p/memcached/issues/detail?id=78
Proposed fix in
http://github.com/ingenthr/memcached/commit/1519ce0c007a55106f0e6
Status: Accepted
Owner: ingenthr
Labels: Type-Defect Priority-Medium
New issue 78 by ingenthr: DTrace probes return types could be better
documented
http://code.google.com/p/memcached/issues/detail?id=78
DTrace probes return unsigned int, and DTrace itself sees everything as
uint64_t meaning
Status: New
Owner: dsallings
Labels: Type-Defect Priority-Medium
New issue 77 by dsallings: Spurious failures on the OpenBSD builder
http://code.google.com/p/memcached/issues/detail?id=77
This one's pretty common:
assertion "read(sock, &response, sizeof(response)) == sizeof(response)"
failed:
Updates:
Status: Fixed
Comment #1 on issue 64 by dsallings: OpenBSD warns of misused string
functions
http://code.google.com/p/memcached/issues/detail?id=64
All of these are cleaned up.
--
You received this message because you are listed in the owner
or CC fields of this issue, or b
Updates:
Status: Fixed
Comment #1 on issue 53 by dsallings: manpage uses hyphen as a minus sign
http://code.google.com/p/memcached/issues/detail?id=53
Pushed this through.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starre
Updates:
Status: Fixed
Comment #3 on issue 42 by dsallings: Stats slabs should include the number
of requested bytes
http://code.google.com/p/memcached/issues/detail?id=42
This was good, though it does have the caveat of having a test that's
dependent on
the item size, so is somew
Updates:
Status: Fixed
Comment #2 on issue 65 by dsallings: test_issue_44 fails on my machine with
memcached running
http://code.google.com/p/memcached/issues/detail?id=65
This has been fixed.
--
You received this message because you are listed in the owner
or CC fields of this issu
Updates:
Status: Fixed
Comment #3 on issue 63 by dsallings: confusing errors when failing to bind
to a port
http://code.google.com/p/memcached/issues/detail?id=63
This wasn't as bad as it used to be, but the vperror fix was pushed.
--
You received this message because you are listed
Updates:
Status: Fixed
Comment #4 on issue 75 by dsallings: Unnecessary stats locks around flushes.
http://code.google.com/p/memcached/issues/detail?id=75
Pushed.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this is
Comment #3 on issue 75 by dsallings: Unnecessary stats locks around flushes.
http://code.google.com/p/memcached/issues/detail?id=75
Pushed.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue
Updates:
Status: Fixed
Comment #2 on issue 71 by dsallings: Statistics not updated when flush is
issued in binary mode
http://code.google.com/p/memcached/issues/detail?id=71
Pushed.
--
You received this message because you are listed in the owner
or CC fields of this issue, or becau
Hi all,
Since a number of memcached contributors and client authors were in one
place at the Drizzle conference this week in Seattle we had a short
discussion about the release roadmap for stable and development
branches. I captured much of the discussion and it's posted on the wiki:
http:/
Maybe you should look into Memcached replication
Josef Finsel wrote:
Karsten,
It's not really possible nor should you worry about it. If this is
really an issue, then the way you're using memcached is probably not
correct.
If the memcached client is set correctly, it will distribute the ke
Karsten,
It's not really possible nor should you worry about it. If this is really an
issue, then the way you're using memcached is probably not correct.
If the memcached client is set correctly, it will distribute the keys across
both servers.
-Josef
On Wed, Aug 19, 2009 at 11:05 AM, Karsten
wr
Hi guys,
I'm a newbie to memcached server and need your help.
I'm currently working on a script, or trying to start working ;),
that should copy all keys (all cached object) to an other memcached
server.
The situation is as follows:
I have two memcached server. Some users may login on a website
24 matches
Mail list logo