Hi,
I have same problem, but starting memcached with -I is causing a
different issue. Can you please help?
Memcached server version: memcached-1.4.5 on Linux 64Bit
spy memcached client version: memcached-2.5
I have two Memcached Servers and they are started with following
command
sudo memcached -d -m 10240 -u root -I 5120 -u root -l [host] -p 11311
I am using 10 instances of the memcached client.
Error Log:
2010-11-10 16:42:17.929 ERROR
net.spy.memcached.protocol.binary.StoreOperationImpl: Error: Too
large.
2010-11-10 16:42:17.931 INFO net.spy.memcached.MemcachedConnection:
Reconnection due to exception handling a memcached operation on {QA
sa=/10.60.291.81:11211, #Rops=1, #Wops=0, #iq=0,
toprop=net.spy.memcached.protocol.binary.storeoperationi...@54a9a793,
topWop=null, toWrite=0, interested=1}. This may be due to an
authentication failure.
OperationException: SERVER: Too large.
at
net.spy.memcached.protocol.BaseOperationImpl.handleError(BaseOperationImpl.java:
123)
at
net.spy.memcached.protocol.binary.OperationImpl.finishedPayload(OperationImpl.java:
147)
at
net.spy.memcached.protocol.binary.OperationImpl.readFromBuffer(OperationImpl.java:
133)
at
net.spy.memcached.MemcachedConnection.handleReads(MemcachedConnection.java:
401)
at
net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:
333)
at
net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:
219)
at net.spy.memcached.MemcachedClient.run(MemcachedClient.java:
1591)
2010-11-10 16:42:17.932 WARN net.spy.memcached.MemcachedConnection:
Closing, and reopening {QA sa=/10.60.291.81:11211, #Rops=1, #Wops=0,
#iq=0,
toprop=net.spy.memcached.protocol.binary.storeoperationi...@54a9a793,
topWop=null, toWrite=0, interested=1}, attempt 0.
2010-11-10 16:42:17.933 WARN
net.spy.memcached.protocol.binary.BinaryMemcachedNodeImpl: Discarding
partially completed op:
net.spy.memcached.protocol.binary.storeoperationi...@54a9a793
2010-11-10 16:42:17.974 ERROR
net.spy.memcached.protocol.binary.StoreOperationImpl: Error: Too
large.
2010-11-10 16:42:17.983 INFO net.spy.memcached.MemcachedConnection:
Reconnection due to exception handling a memcached operation on {QA
sa=/10.70.181.63:11311, #Rops=1, #Wops=1, #iq=0,
toprop=net.spy.memcached.protocol.binary.storeoperationi...@7a36ae66,
topwop=net.spy.memcached.protocol.binary.storeoperationi...@7a36ae66,
toWrite=1368, interested=5}. This may be due to an authentication
failure.
OperationException: SERVER: Too large.
Thanks
Abhilash
On Oct 19, 1:37 pm, Sakuntala <[email protected]> wrote:
> Peter and Dustin,
>
> Thanks a ton for your replies. The info did help me.
>
> -Sakuntala.
>
> On Oct 15, 12:58 pm, Dustin <[email protected]> wrote:
>
> > On Oct 15, 9:56 am, "Peter J. Holzer" <[email protected]> wrote:
>
> > > Yes, it's a hard limit (but you can recompile memcached if you want a
> > > higher limit). But most client libraries can compress the
> > > objects before storing it. If you have enabled compression in spy
> > > memcached client (which might be the default) it is possible that you
> > > can store items much larger than 1MB if they compress well.
>
> > If you don't want to recompile it, you can just use -I at runtime.
>
> > -I Override the size of each slab page. Adjusts max item
> > size
> > (default: 1mb, min: 1k, max: 128m)
