[infinispan-issues] [JBoss JIRA] (ISPN-2005) Memcached server throwing UnknownOperationException with many clients
Galder Zamarreño (JIRA)
jira-events at lists.jboss.org
Wed Apr 25 12:51:17 EDT 2012
[ https://issues.jboss.org/browse/ISPN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12687714#comment-12687714 ]
Galder Zamarreño commented on ISPN-2005:
----------------------------------------
I've just tried with the Python Memcached client with 300 threads and showed no problems whatsoever. This really smells like an issue in Spymemcached which is both present in 2.7 and 2.8.1. I'll submit an issue in Spymemcached asap.
> Memcached server throwing UnknownOperationException with many clients
> ---------------------------------------------------------------------
>
> Key: ISPN-2005
> URL: https://issues.jboss.org/browse/ISPN-2005
> Project: Infinispan
> Issue Type: Bug
> Components: Cache Server
> Affects Versions: 5.1.3.FINAL
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 5.1.4.FINAL
>
>
> With native memcached out of the box, I can execute such a test without any problems:
> 1000 clients (threads), 400 operations per thread, 34% writes
> However, running Infinispan Memcached distribution with 1000 worker threads results in exceptions such as:
> {code}2012-04-23 16:46:59,893 ERROR (MemcachedServerWorker-1-957) [org.infinispan.server.memcached.MemcachedDecoder] ISPN005003: Exception reported
> org.infinispan.server.core.UnknownOperationException: Unknown operation:
> at org.infinispan.server.memcached.RequestResolver$.toRequest(MemcachedDecoder.scala:659)
> at org.infinispan.server.memcached.MemcachedDecoder.readHeader(MemcachedDecoder.scala:73)
> at org.infinispan.server.core.AbstractProtocolDecoder.decodeHeader(AbstractProtocolDecoder.scala:92)
> at org.infinispan.server.core.AbstractProtocolDecoder.decode(AbstractProtocolDecoder.scala:69)
> at org.infinispan.server.core.AbstractProtocolDecoder.decode(AbstractProtocolDecoder.scala:45)
> at org.infinispan.server.core.transport.CustomReplayingDecoder.callDecode(CustomReplayingDecoder.java:250)
> at org.infinispan.server.core.transport.CustomReplayingDecoder.messageReceived(CustomReplayingDecoder.java:223)
> at org.infinispan.server.core.AbstractProtocolDecoder.messageReceived(AbstractProtocolDecoder.scala:360)
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274)
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261)
> at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:351)
> at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:282)
> at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:202)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:680){code}
> Client shows:
> {code}2012-04-23 16:46:28.742 INFO net.spy.memcached.MemcachedConnection: Reconnecting due to exception on {QA sa=/127.0.0.1:11211, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0}
> java.net.SocketException: Connection reset by peer
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:567)
> at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:369)
> at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:242)
> at net.spy.memcached.MemcachedConnection.run(MemcachedConnection.java:833){code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list