gt;> frequent issue... we are playing with a small process that does the warmup
>> of new nodes quicker.
>>
>> Since we have more than one copy of the data, we do a warmup process. Our
>> cache nodes are MUCH MUCH smaller... so this approach might not be
>> reasonabl
han one copy of the data, we do a warmup process. Our
> cache nodes are MUCH MUCH smaller... so this approach might not be
> reasonable for your use-case.
>
> This is how our process works, when a new node is restarted or any other
> situation that involves an empty memcached process
First off, thanks for the amazing work @dormando & others!
*Context:*
*I work at Grafana Labs, and we are very interested in trying out extstore
for some very large (>50TB) caches. We plan to split this 50TB cache into
about 35 different nodes, each with 1.5TB of NVMe & a smal
To add another datapoint here, we at Grafana Labs use memcached extensively
in our cloud and this fix made a massive impact on our cache effectiveness:
https://user-images.githubusercontent.com/373762/204228886-7c5a759a-927c-46fb-ae55-3e0b4056ebae.png
Thank you very much to you both
seemed to previously be a blocker for development (#3
> (comment)
> <https://github.com/libmemcached/libmemcached/issues/3#issuecomment-526861248>).
> However, there is still no CI setup and tests aren't passing locally with
> the latest memcached server version (e.g. #12
> &l
We are using version 1.6.6 of memcached with extstore enabled and we are
observing records being evicted but evictions stat reports 0.
slab_reassign_evictions_nomem stat does show items being evicted. How do we
avoid losing records due to slab_reassign_evictions_nomem ? Also, is there
a reason
Hi,
We are a UK-based travel site looking for some help/checking of our
memcached setup. We rely on memcached quite a bit and make a large number
of calls, so small improvements could help us a fair bit.
Appreciate any pointers.
Thanks
Dan
--
---
You received this message because you
Thanks Dormando. I will update the doc and add another section for meta
protocol.
On Sun, Mar 8, 2020 at 9:33 PM dormando wrote:
> Hey,
>
> So first part: https://github.com/memcached/memcached/wiki/ReleaseNotes160
>
> We won't be adding further features to the binary pr
Hi Dormando and memcached community,
I work in Google Cloud Platform and we want to propose an open standard for
memcached node auto-discovery protocol that's independent of Cloud
providers and can work with on-premise infrastructure as well.
Auto-discovery protocol will allow engineering teams
?
Is there a stats output that shows compaction is running?
Thanks
--Theo
--
---
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...@google
You can use "lru_crawler metadump all" as well.
RN :https://github.com/memcached/memcached/wiki/ReleaseNotes1431
On Monday, November 4, 2019 at 2:12:26 AM UTC-8, Rahul Roshan wrote:
>
> Hi Team,
>
> I have a requirement to get all entries stored in memcache whos
You can do something like this:
https://stackoverflow.com/questions/19560150/get-all-keys-set-in-memcached
On Mon, Nov 4, 2019 at 2:12 AM Rahul Roshan
wrote:
> Hi Team,
>
> I have a requirement to get all entries stored in memcache whose keys are
> starting with a known prefi
Is Memcached HIPAA eligible/Compliant service. We have frequent asks from
customers on similar lines. Any help is much appreciated.
--
**The content of this e-mail is confidential and is intended solely for the
use of the individual or entity to whom it is addressed. If you have
received
It sounds like this is not the memcached server, but the client. Maybe you
can seek help from a libmemcached forum? Not sure how actively it's
maintained or used. You can always use a profiling tool like perf to find
out what's going on (http://www.brendangregg.com/perf.html). A similar bug
rtunate downside
> is that you can only dump one page per slab, according to this.
> > I bet you could get fancy and dump the entire process memory and dig
> through it yourself... That could be fun.
> >
> > On Fri, Mar 22, 2019 at 11:27 AM nagashe via memcached <
>
after the fact?
We are running 1.4.20 (i know its a few years old). I tried to figure out
by searching on google, some people recommended `stats cachedump
`
(https://stackoverflow.com/questions/2558706/how-can-i-get-the-expire-time-for-the-particular-item-in-memcached).
I wanted to check here
,
Eamonn
On Sun, Mar 17, 2019 at 4:16 PM dormando wrote:
> Yo,
>
> Fwiw, I use mc-crusher as the "official" benchmark:
> https://github.com/memcached/mc-crusher tho I need to update the README
> slightly. will do that in a bit.
>
> I also test on hardware uninterru
t and 64bit hashes and then
>> have to do compile time testing to figure out which to use. It's also
>> heavily x86 optimized so we might have to default something else for ARM.
>>
>> Sorry, not debated on the list, just in my own head :) It's not quite as
>> straight
mething else for ARM.
>
> Sorry, not debated on the list, just in my own head :) It's not quite as
> straightforward as just dropping it in. If you're willing to get all the
> conditions tested go nuts! :)
>
> -Dormando
>
> On Sat, 16 Mar 2019, eamonn.nugent via memcached wro
Hi there,
I started using memcached in prod a week or two ago, and am loving it. I
wanted to give back, and took a look through the issues board, but most of
them looked solved. So, in my usual "it's never fast enough" style, I went
and profiled its performance, and had some fun.
Af
We potentially have a need for fetching remaining time left before a key
expires from memcached. I see that mcrouter's metaget function could meet
our needs, but it is not implemented in open source memcached. Are there
plans to add metaget function to open source memcached?
--
---
You
github repo so people can register
> interest there; it shouldn't be too hard to do once some other stuff has
> settled down.
>
> On Mon, 3 Jul 2017, 'Mario Niebla' via memcached wrote:
>
> > Has anyone ever gotten the '-L' (large page support) to work in Linux?
> >
Has anyone ever gotten the '-L' (large page support) to work in Linux?
I know my amazon 2017.03 AMI kernel supports huge-pages.
In theory, I have set up my box 512 huge pages at 2MB each so I can start
memcached with a 1GB cache size.
I've verified this by doing `cat /proc/meminfo |grep
The patch was a little overzealous:
https://github.com/memcached/memcached/pull/255
It would probably need to be scaled back a bit or reworked to be more
logically contained. I have unfortunately lost motivation to work on it
because the issue I was trying to solve is so rare for us. I may look
I have opened a pull request with a preliminary implementation for a
settings command: https://github.com/memcached/memcached/pull/255
I took a few liberties, so let me know if anything is out of line.
On Wednesday, January 25, 2017 at 1:52:24 PM UTC-8, Dormando wrote:
>
> Yeah gimme
I'm actually working on a patch to possibly do this, there's another thread
from a couple weeks ago on this.
On Friday, February 3, 2017 at 3:24:11 AM UTC-8, Spybdai Shao wrote:
>
> Hi guys,
>
> I am wondering,
> Is there a way to reload memcached service to use the lates
and binprot + the req_per_event option to see how bad
> this is measurably.
>
> On Wed, 25 Jan 2017, 'Scott Mansfield' via memcached wrote:
>
> > The client is the EVCache client jar: https://github.com/netflix/evcache
> > When a user calls the batch get function on the client,
The reqs_per_event setting was causing a client that was doing large
batch-gets (of a few hundred keys) to see some timeouts. Since memcached
will delay responding fully until other connections are serviced and our
client will wait until the batch is done, we see some client-side timeouts
t all of the alternative hardware ideas people have tried for
> memcached have had practicality issues. Either cost, complexity, or
> communication with the main CPU tend to kill it.
>
> It's fun to toy with and at some point someone will make something usable,
> I hope. The MS cha
nctionalities that can improve
> performance. Any suggestions are welcome.
>
> Thanks & Regards
> Ravi G
>
> From: Scott Mansfield [mailto:smansfi...@netflix.com]
> Sent: Tuesday, January 24, 2017 7:40 AM
> To: memcached <memcached@googlegroups.com>
>
,
though there are some that are ad-hoc changeable through some stats
commands. I was going to see if I could patch memcached to be able to
change the reqs_per_event setting at runtime, but before doing so I wanted
to check to see if that's something that would be amenable. I also didn't
want to do
ovec structures ahead of time, doing the
> hashing/lookup in parallel and filling the results before sending the
> response.
>
> With binprot each get/response are independently packaged so it's a bit
> easier, although the protocol bloat makes it less useful at high rates.
>
> P
--
---
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 more options, visit https://groups.google.com/d/optout.
minute instead of the intended time
>
> On Dec 5, 2016, at 3:02 PM, 'Sunny Side Up' via memcached <
> memc...@googlegroups.com > wrote:
>
> Hi,
>
> Can anyone help me with this question:
>
>
> http://stackoverflow.com/questions/40964315/stop-memcache-from-removing-data
iate some pointers as memcache is new to me.
--
---
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 more options, visit
processes on your system dying,
you're much better off either decreasing your memory use, or increasing
your available memory.
-j
On 7/26/2016 2:29 AM, MemcachedUser wrote:
Looks like memcached was killed by the kernel because it was consuming
too much memory (came across this in the kernel log
t; after the request is served and the child process is closing, causes an
> instability (was it an illegal close or a segfault). In addition, copying
> the pool to each client does not seem to be reasonable.
>
> The solution in use now is to use 'memcached' instead of
> 'memcach
he01','memcache02', 'memcache03',
> 'memcache04']
>
> Next:
> memcache_servers => ['new-memcache01','memcache02', 'memcache03']
>
> and so on.
>
> Any thoughts?
>
>
> --
>
> ---
> You received this message because you are subscribed to the Google G
of this type of change be accepted into
the main memcached source tree? It would help to know so we can best
organize the code in a way to most easily merge future memcached
changes--in case we have to maintain a permanent fork of memcached.
Thanks
Vu
--
---
You received this message because
RHEL/CentOS 5: Fails to compile, logger.c needs to include stdio.h.
After fixing, builds & tests fine
RHEL/CentOS 6: Same as CentOS 5.
RHEL/CentOS 7: Clean
OSX: It looks like every version of memcached (as far back as I was
willing to test) has the test problem I reported before.
> wrote:
>
>
> On Fri, 17 Jun 2016, Dagobert Michelsen wrote:
>
> > Hi Dormando,
> >
> > Am 17.06.2016 um 10:39 schrieb dormando <dorma...@rydia.net>:
> > > https://github.com/memcached/memcached/pull/127 is now "done", as
> much a
random thoughts to dormando's:
>
> 1) If your memcached thread count is set correctly, each thread of a
> single memcached instance will end up with, effectively, its very own
> processor core (assuming a server dedicated to memcached). If you have
> multiple instances, you can also get
A couple more random thoughts to dormando's:
1) If your memcached thread count is set correctly, each thread of a single
memcached instance will end up with, effectively, its very own processor
core (assuming a server dedicated to memcached). If you have multiple
instances, you can also get
It should. Here's the parsing code:
https://github.com/memcached/memcached/blob/master/memcached.c#L5179
getopt will return in order of the original command line (I believe) so you
should be overriding and using UDP. You can always check by looking at open
sockets on your system.
On Wednesday
If you listen to 127.0.0.1 then only connections from the same server will
work. Are you trying to connect from the same server that memcached is
running on? If not, just leave the option out.
On Wednesday, March 23, 2016 at 3:54:01 PM UTC-7, vent...@gmail.com wrote:
>
> Hello!
>
>
memcached will allocate additional pages as long as the total memory
allocated is less than the value specified by the -m ("max memory to use
for items in megabytes”) startup option. If no more pages can be allocated
within this limit, it will evict objects from the end of the slab’s LRU to
i
led, 99.95% okay.
(will test RHEL6 and RHEL7 in a bit)
-j
On Thu, Nov 19, 2015 at 2:50 AM, dormando <dorma...@rydia.net> wrote:
> Hey,
>
> https://github.com/memcached/memcached - I've dumped what I hope are all
> of the commits for 1.4.25 into master. If you're listening, would
<dorma...@rydia.net> wrote:
> Yo,
>
> https://github.com/dormando/memcached/commits/slab_rebal_next - would you
> mind playing around with the branch here? You can see the start options in
> the test.
>
> This is a dead simple modification (a restoration of a feature that was
&
memcached 1.4.13 on
my path (who knows how...) Using the actual one that I've built works.
Sorry for the confusion... can't believe I didn't realize that before. I'm
testing against the compiled one now to see how it behaves.
On Monday, August 3, 2015 at 1:15:06 AM UTC-7, Dormando wrote
Comment #1 on issue 414 by dorma...@rydia.net: memcached 1.4.24 segfaults
https://code.google.com/p/memcached/issues/detail?id=414
crap, I wish I saw this sooner.
What is your items.c:1183?
It looks like:
if (it-prev) {
it-prev-next = it;
}
^ middle line.
I'd love
Updates:
Status: Invalid
Comment #1 on issue 413 by dorma...@rydia.net: Using
Library Enyim.Caching.dll, Data is not stored in memcached
https://code.google.com/p/memcached/issues/detail?id=413
please don't use the bug tracker for support. I don't know why offhand that
doesn't work
Updates:
Status: Fixed
Comment #33 on issue 375 by dorma...@rydia.net: Accept4 on FreeBSD 10 -
sockets stuck in CLOSE
https://code.google.com/p/memcached/issues/detail?id=375
fixed, even though it was an upstream problem :)
--
You received this message because this project
Updates:
Status: Invalid
Comment #1 on issue 407 by dorma...@rydia.net: Test whitespace.t is failing
on Solaris i386
https://code.google.com/p/memcached/issues/detail?id=407
why're there cores in there? what's the stacktrace in the core and which
test failed?
I'm going to mark
Updates:
Status: Fixed
Comment #2 on issue 416 by dorma...@rydia.net: 1.4.24 fails to build with
-Werror
https://code.google.com/p/memcached/issues/detail?id=416
weird. wonder why the clang fix didn't get that one... it's the same.
I've fixed this in the 'next' branch, thanks
Updates:
Status: Invalid
Comment #2 on issue 353 by dorma...@rydia.net: 1.4.17: -Werror
and comparison between signed and unsigned integer expressions
https://code.google.com/p/memcached/issues/detail?id=353
going to close this... I see -Werror on in my own builds and it's doing
Updates:
Status: Invalid
Comment #1 on issue 406 by dorma...@rydia.net: Failing test
lru-maintainer.t on Solaris i386 and amd64
https://code.google.com/p/memcached/issues/detail?id=406
I can't tell why this would fail? why is gethostbyname erroring?
What's in that corefile
Updates:
Status: Invalid
Comment #2 on issue 343 by dorma...@rydia.net: memcached-1.4.15 build fails
with Intel compiler icc due to missing -std=gnu99 option
https://code.google.com/p/memcached/issues/detail?id=343
closing this due to age and lack of ability to follow up. if someone
Comment #1 on issue 418 by dorma...@rydia.net: Build fail on Debian sparc
https://code.google.com/p/memcached/issues/detail?id=418
I need more information. can you get a backtrace? do the perl tests pass?
prove -v t/binary.t might be helpful. that looks like it failed on the
binary_replaceq
Updates:
Status: Invalid
Comment #2 on issue 410 by dorma...@rydia.net: set result sometimes false
https://code.google.com/p/memcached/issues/detail?id=410
How large are these items? If the bottom items are locked for some reason
(being uploaded to, or modified), store will return out
Updates:
Status: Invalid
Comment #1 on issue 408 by dorma...@rydia.net: build memcached fail in
windows 7 cygwin
https://code.google.com/p/memcached/issues/detail?id=408
sorry, we don't directly support windows :(
--
You received this message because this project is configured
Comment #7 on issue 409 by charles@metamarkets.com: build fail in
opensuse 11.4 by clang 3.6.0
https://code.google.com/p/memcached/issues/detail?id=409
work around for OSX:
CC=gcc-5 ./configure
Specifying the CC binary to be a non-clang binary worked for me. I have gcc
installed via
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 418 by guillaum...@gmail.com: Build fail on Debian sparc
https://code.google.com/p/memcached/issues/detail?id=418
What steps will reproduce the problem?
1. build memcached with Sun Fire T2000 under Debian
What
Comment #2 on issue 398 by guillaum...@gmail.com: make test failed
https://code.google.com/p/memcached/issues/detail?id=398
Just realized that i've opened another bug for the same issue:
https://code.google.com/p/memcached/issues/detail?id=417
--
You received this message because this project
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 417 by guillaum...@gmail.com: t/lru-crawler.t sometimes fail
https://code.google.com/p/memcached/issues/detail?id=417
What steps will reproduce the problem?
1. build memcached
2. run make test
What is the expected output
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 416 by steve.wi...@gmail.com: 1.4.24 fails to build with -Werror
https://code.google.com/p/memcached/issues/detail?id=416
What steps will reproduce the problem?
1. Try to compile
What is the expected output? What do you see
Comment #1 on issue 416 by steve.wi...@gmail.com: 1.4.24 fails to build
with -Werror
https://code.google.com/p/memcached/issues/detail?id=416
Here's the full log
Attachments:
memcached-1.4.24.log 30.8 KB
--
You received this message because this project is configured to send all
Comment #1 on issue 392 by zaika...@gmail.com: memleaks
https://code.google.com/p/memcached/issues/detail?id=392
Since I am interested in contributing, would it be possible for me to look
into this task?
--
You received this message because this project is configured to send all
issue
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 415 by sumac...@gmail.com: Error while make - OSX 10.10.3
https://code.google.com/p/memcached/issues/detail?id=415
What steps will reproduce the problem?
1. execute make
What is the expected output? What do you see instead
Comment #6 on issue 409 by wendal1...@gmail.com: build fail in opensuse
11.4 by clang 3.6.0
https://code.google.com/p/memcached/issues/detail?id=409
I just delete this line
--
You received this message because this project is configured to send all
issue notifications to this address
Comment #5 on issue 409 by houxiufeng1...@gmail.com: build fail in opensuse
11.4 by clang 3.6.0
https://code.google.com/p/memcached/issues/detail?id=409
I got the this error when I install memcached(1.4.24) in mac osx(10.9.5),
any advices to fix this problem?
--
You received this message
Comment #4 on issue 409 by zhangnia...@gmail.com: build fail in opensuse
11.4 by clang 3.6.0
https://code.google.com/p/memcached/issues/detail?id=409
I am getting the same error when make on Mac OX.
--
You received this message because this project is configured to send all
issue
Comment #1 on issue 412 by fabien.d...@gmail.com: A compile warning
https://code.google.com/p/memcached/issues/detail?id=412
Having the same issue in CentOS 5.11.
What steps will reproduce the problem?
1. Start with a blank CentOS 5.11 machine
2. Install the following packages in order
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 414 by ant...@corp.badoo.com: memcached 1.4.24 segfaults
https://code.google.com/p/memcached/issues/detail?id=414
What steps will reproduce the problem?
1.
SLES 11.3 with slightly patched 3.16 kernel
Linux memcached9 3.16.3
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 413 by arbind.s...@v2solutions.com: Using
Library Enyim.Caching.dll, Data is not stored in memcached
https://code.google.com/p/memcached/issues/detail?id=413
Configuration in Web.config
sectionGroup name=enyim.com
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 412 by sheung@gmail.com: A compile warning
https://code.google.com/p/memcached/issues/detail?id=412
What steps will reproduce the problem?
1. I package a memcached.rpm on rhel5;
2. The default option of gcc is warnings
Comment #3 on issue 409 by emn...@gmail.com: build fail in opensuse 11.4 by
clang 3.6.0
https://code.google.com/p/memcached/issues/detail?id=409
me too.
with clang 3.6.1
memcached 1.4.24
--
You received this message because this project is configured to send all
issue notifications
Comment #1 on issue 398 by jna...@gmail.com: make test failed
https://code.google.com/p/memcached/issues/detail?id=398
I hit the same make test' problem on Ubuntu 14.04.2 LTS (GNU/Linux
3.13.0-48-generic x86_64)
and memcached-1.4.24
t/lru-crawler.t .. 93/221 Timeout.. killing
Comment #1 on issue 409 by y...@yomstar.com: build fail in opensuse 11.4 by
clang 3.6.0
https://code.google.com/p/memcached/issues/detail?id=409
I am also getting this exact error on Mac OX
--
You received this message because this project is configured to send all
issue notifications
Comment #2 on issue 409 by yoanntro...@etrainu.com: build fail in opensuse
11.4 by clang 3.6.0
https://code.google.com/p/memcached/issues/detail?id=409
I am also getting this exact error when run make on Mac Ox
--
You received this message because this project is configured to send all
Comment #1 on issue 410 by goche...@gmail.com: set result sometimes false
https://code.google.com/p/memcached/issues/detail?id=410
When I use Memcache Version: 1.4.22 still have that issue but sometimes
0 detect on 5 insert not happen again.
--
You received this message because
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 410 by goche...@gmail.com: set result sometimes false
https://code.google.com/p/memcached/issues/detail?id=410
What steps will reproduce the problem?
1. Just set memcached with key length 20
2. key = P0211234501_01234567
3
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 409 by wendal1...@gmail.com: build fail in opensuse 11.4 by clang
3.6.0
https://code.google.com/p/memcached/issues/detail?id=409
What steps will reproduce the problem?
1. download latest memcached
2. run CC=clang
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 408 by wendal1...@gmail.com: build memcached fail in windows 7
cygwin
https://code.google.com/p/memcached/issues/detail?id=408
What steps will reproduce the problem?
1. download 1.4.24 to /tmp/memcached-1.4.24
2. run
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 407 by honkma...@googlemail.com: Test whitespace.t is failing on
Solaris i386
https://code.google.com/p/memcached/issues/detail?id=407
What steps will reproduce the problem?
1. Build memcached from GitHub master on Solaris
Comment #11 on issue 404 by dorma...@rydia.net: memcached 1.4.23 fails test
binary_prependq on Solaris 10 Sparc 64 Bit
https://code.google.com/p/memcached/issues/detail?id=404
please open other issues for those things. you can have the thing e-mail me
I guess? don't want it to spam
Comment #12 on issue 404 by honkma...@googlemail.com: memcached 1.4.23
fails test binary_prependq on Solaris 10 Sparc 64 Bit
https://code.google.com/p/memcached/issues/detail?id=404
Sure, I added your email to the list of notifiers. Just let me know if you
need adjusted settings.
--
You
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 406 by honkma...@googlemail.com: Failing test lru-maintainer.t on
Solaris i386 and amd64
https://code.google.com/p/memcached/issues/detail?id=406
What steps will reproduce the problem?
1. Build memcached from GitHub master
Comment #8 on issue 404 by dorma...@rydia.net: memcached 1.4.23 fails test
binary_prependq on Solaris 10 Sparc 64 Bit
https://code.google.com/p/memcached/issues/detail?id=404
Another push to master for a workaround in the test. Solaris seems to not
handle the background juggler's sleeps
Comment #13 on issue 403 by arne.cl...@gmail.com: Memcached 1.4.23 crashes
on stats command
https://code.google.com/p/memcached/issues/detail?id=403
Well it does have a point because that assert does not really make much
sense as a byte is always 256.
--
You received this message
Comment #12 on issue 403 by markhag...@gmail.com: Memcached 1.4.23 crashes
on stats command
https://code.google.com/p/memcached/issues/detail?id=403
This fixes it for me, all tests now pass. Great stuff, I shall go ahead
and test this release hard on a real machine now.
--
You received
Comment #14 on issue 403 by arne.cl...@gmail.com: Memcached 1.4.23 crashes
on stats command
https://code.google.com/p/memcached/issues/detail?id=403
Removed the asserts - compiles - stats do now work again.
--
You received this message because this project is configured to send all
issue
Comment #6 on issue 404 by honkma...@googlemail.com: memcached 1.4.23 fails
test binary_prependq on Solaris 10 Sparc 64 Bit
https://code.google.com/p/memcached/issues/detail?id=404
BTW, what happened to the buildfarm?
https://code.google.com/p/memcached/wiki/BuildFarm
The waterfall display
Comment #15 on issue 403 by dpmc...@gmail.com: Memcached 1.4.23 crashes on
stats command
https://code.google.com/p/memcached/issues/detail?id=403
Stats works for me now as well on the box that was unresponsive, once the
patch is applied. Thanks!
--
You received this message because
Comment #5 on issue 404 by honkma...@googlemail.com: memcached 1.4.23 fails
test binary_prependq on Solaris 10 Sparc 64 Bit
https://code.google.com/p/memcached/issues/detail?id=404
I also just patched in the latest commit f086 to the tarball.
The test suite now passes on sparcv9 cleanly
Comment #4 on issue 404 by dpmc...@gmail.com: memcached 1.4.23 fails test
binary_prependq on Solaris 10 Sparc 64 Bit
https://code.google.com/p/memcached/issues/detail?id=404
I ran the same build/test/package steps that triggered the above, pulling
the one (369845f086) patch from git
Comment #9 on issue 403 by dorma...@rydia.net: Memcached 1.4.23 crashes on
stats command
https://code.google.com/p/memcached/issues/detail?id=403
Seems like everything using LARGEST_ID and POWER_LARGEST were comparing
via already, so upping LARGEST_ID by one should cover all of the other
Updates:
Status: Accepted
Comment #3 on issue 404 by dorma...@rydia.net: memcached 1.4.23 fails test
binary_prependq on Solaris 10 Sparc 64 Bit
https://code.google.com/p/memcached/issues/detail?id=404
Can you folks please try https://github.com/memcached/memcached (master
branch
Comment #10 on issue 403 by arne.cl...@gmail.com: Memcached 1.4.23 crashes
on stats command
https://code.google.com/p/memcached/issues/detail?id=403
Does not compile with clang:
items.c:274:28: error: comparison of constant 256 with expression of
type 'uint8_t' (aka 'unsigned char
Comment #11 on issue 403 by dorma...@rydia.net: Memcached 1.4.23 crashes on
stats command
https://code.google.com/p/memcached/issues/detail?id=403
seriously, clang? I have to go swap all of the 's and ='s? :/
Well if you're still reading and aren't building with clang I'd like to
know
Comment #2 on issue 404 by dpmc...@gmail.com: memcached 1.4.23 fails test
binary_prependq on Solaris 10 Sparc 64 Bit
https://code.google.com/p/memcached/issues/detail?id=404
I'm seeing this on Arch Linux as well.
This is similar to an earlier issue I have seen in that I think it might
1 - 100 of 1290 matches
Mail list logo
