Assertion Failed for Items > 1MB

116 views
Skip to first unread message

nkranes

unread,
Jan 12, 2010, 8:52:23 AM1/12/10
to memcached
I am using the Windows version of memcached 1.2.5 in production
without issue. I am attempting to upgrade to 1.4.4 (from
http://labs.northscale.com/memcached-packages/) to take advantage of
the configurable item size limitation. Whenever I try to store an
item > 1MB I get the following error:

Assertion failed: it->nbytes < (1024 * 1024), file items.c, line 284

The line of code in items.c is:
assert(it->nbytes < (1024 * 1024)); /* 1MB max size */

So how could this possibly work? I can remove that assertion, but was
curious to see if anyone knew why it was there considering the item
limit *should* now be configurable.

Thanks!

Dustin

unread,
Jan 12, 2010, 12:40:59 PM1/12/10
to memcached

On Jan 12, 5:52 am, nkranes <nkra...@gmail.com> wrote:
> I am using the Windows version of memcached 1.2.5 in production
> without issue.  I am attempting to upgrade to 1.4.4 (fromhttp://labs.northscale.com/memcached-packages/) to take advantage of

> the configurable item size limitation.  Whenever I try to store an
> item > 1MB I get the following error:
>
> Assertion failed: it->nbytes < (1024 * 1024), file items.c, line 284
>
> The line of code in items.c is:
> assert(it->nbytes < (1024 * 1024));  /* 1MB max size */
>
> So how could this possibly work?  I can remove that assertion, but was
> curious to see if anyone knew why it was there considering the item
> limit *should* now be configurable.

That's kind of funny. Apparently we added the option but didn't try
it in a debug build.

We'll get a test written for it.

In the meantime, it *should* be safe to remove that assertion.

nkranes

unread,
Jan 12, 2010, 12:48:05 PM1/12/10
to memcached
OK. When do you suspect you'll have an updated build that I can
grab? Compiling this is proving to be more time consuming than I had
hoped.

Thanks much for your attention to this.

Patrick Galbraith

unread,
Jan 12, 2010, 2:48:25 PM1/12/10
to memc...@googlegroups.com
Hi there!

I built a new binary that you can try out if you like at :

http://downloads.northscale.com/memcached-win32-1.4.4-53-g0b7694c.zip

We're in the process of testing this right now, but if you want to give
it a shot, please feel free!

--Patrick

nkranes

unread,
Jan 12, 2010, 3:03:46 PM1/12/10
to memcached
I'm getting an Access Denied error.

Patrick Galbraith

unread,
Jan 12, 2010, 3:42:29 PM1/12/10
to memc...@googlegroups.com
Hi there!

It was working, but for some reason where we host the files has some
sort of error. I'm working on remedying this,

Thanks!

--Patrick

Patrick Galbraith

unread,
Jan 12, 2010, 5:35:47 PM1/12/10
to memc...@googlegroups.com
Hi there again!

The updated, tested binary is
http://downloads.northscale.com/memcached-win32-1.4.4-54-g136cb6e.zip

regards,

Patrick

Marc Bollinger

unread,
Feb 8, 2010, 12:58:28 PM2/8/10
to memc...@googlegroups.com
Just curious, Northscale guys: how stable would you consider the build
on your website currently (e.g. are you using it in production, or
would you recommend using it in production)?

Thanks!

- Marc

Matt Ingenthron

unread,
Feb 9, 2010, 4:10:16 AM2/9/10
to memc...@googlegroups.com
Hi Marc,

Marc Bollinger wrote:
> Just curious, Northscale guys: how stable would you consider the build
> on your website currently (e.g. are you using it in production, or
> would you recommend using it in production)?
>

There will be a release which we consider thoroughly tested and ready
for any production environment. As far as whether the build which is
there is ready for your production environment, that varies.

Except for an issue that appears to be related to dynamic linking
restrictions on Microsoft's Azure, we aren't aware of any outstanding
issues. We haven't encountered any stability or functional issues, and
haven't had any reports of any yet.

There are a number of people with it deployed in developer environments,
more on desktops, and we've not heard of any issues there. I'm pretty
sure there's at least one deployment someone considers "production",
though that designation may be applied to very different deployments.

In the mean time, if you have any feedback, we'd love to hear about it.

Thanks!

- Matt

Brandon...@elementk.com

unread,
Feb 9, 2010, 7:16:43 AM2/9/10
to memc...@googlegroups.com
I have been using it for development use for over a month now and I have
not experienced any problems whatsoever. We don't use it in our production
environment, however, so I can't say how stable it is for production use.

I hope that helps.


Brandon Ramirez | Office: 585.214.5013 | Fax: 585.295.4848
Software Engineer II | Element K | www.elementk.com


From: Matt Ingenthron <inge...@cep.net>

To: memc...@googlegroups.com

Date: 02/09/2010 04:11 AM

Subject: Re: Assertion Failed for Items > 1MB

Sent by: memc...@googlegroups.com

Marc Bollinger

unread,
Feb 9, 2010, 12:57:19 PM2/9/10
to memc...@googlegroups.com
Awesome, thanks for the usage info! We're going to do some testing then, and
start integrating it into some not-as-essential clusters. Matt, we'll
let you know
if we run into any stability or such issues, and thanks to your team for putting
together the release!

- Marc

Reply all
Reply to author
Forward
0 new messages