[JBoss JIRA] Created: (ISPN-811) Memcached unknown command causes a lost line in command pipeline
by Galder Zamarreño (JIRA)
Memcached unknown command causes a lost line in command pipeline
----------------------------------------------------------------
Key: ISPN-811
URL: https://jira.jboss.org/browse/ISPN-811
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 4.2.0.CR2, 4.1.0.Final
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 4.2.0.CR3, 4.2.0.Final
>From Michal:
"memcached server consumes one more line of input than it has to when unknown command occurs.
input:
"bogus\r\ndelete a\r\n"
expected output:
ERROR
NOT_FOUND
actual output:
ERROR
input:
"bogus\r\ndelete a\r\ndelete a\r\n"
expected output:
ERROR
NOT_FOUND
NOT_FOUND
actual output:
ERROR
NOT_FOUND
input: "bogus \r\ndelete a\r\ndelete a\r" (space after bogus) behaves as expected
check MemcachedDecoder.scala, line 45
readLine consumes next line even when it was already done by readElement"
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (ISPN-788) In Memcached, flush_all noreply doesn't work
by Galder Zamarreño (JIRA)
In Memcached, flush_all noreply doesn't work
--------------------------------------------
Key: ISPN-788
URL: https://jira.jboss.org/browse/ISPN-788
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 4.2.0.BETA1, 4.1.0.Final
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Priority: Minor
Fix For: 4.2.0.CR1, 4.2.0.Final
As per comments from Michal:
"sending "flush_all noreply\r\n" to memcached server module causes
SERVER_ERROR org.infinispan.server.core.ServerException: java.lang.NumberFormatException: For input string: "noreply""
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (ISPN-804) There should be a clustering mode for local
by Changgeng Li (JIRA)
There should be a clustering mode for local
-------------------------------------------
Key: ISPN-804
URL: https://jira.jboss.org/browse/ISPN-804
Project: Infinispan
Issue Type: Feature Request
Components: Configuration
Affects Versions: 4.2.0.CR1
Reporter: Changgeng Li
Assignee: Manik Surtani
Fix For: 4.2.0.CR3
If we have a cluster.xml where the clustering mode is replication mode for the default configuration, there's no way to override a specific cache to be in local mode. This is not convenient and require us either to separate the cache definition in two cluster.xml or to make the local mode as default and change all the other caches to replication mode.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (ISPN-794) Memcached server should treat flags as unsigned 32bit integers
by Galder Zamarreño (JIRA)
Memcached server should treat flags as unsigned 32bit integers
--------------------------------------------------------------
Key: ISPN-794
URL: https://jira.jboss.org/browse/ISPN-794
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 4.2.0.CR1, 4.1.0.Final
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Priority: Minor
Fix For: 4.2.0.CR2, 4.2.0.Final
As indicated by Michal:
""flags" argument used with memcached storage commands is described as 16 or 32 bit unsigned integer.
if I understand it correctly 16bits is recommended for clients for compatibility with older memcached implementations, but current memcached implementation should support 32bits.
original memcached implementation allows range: 0 .. 4294967295 (actually also some negative numbers, but that's a bug I guess: http://code.google.com/p/memcached/issues/detail?id=168)
we allow range: -2147483648 .. 2147483647"
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (ISPN-793) Memcached server should throw error when stats comes with args
by Galder Zamarreño (JIRA)
Memcached server should throw error when stats comes with args
--------------------------------------------------------------
Key: ISPN-793
URL: https://jira.jboss.org/browse/ISPN-793
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 4.2.0.BETA1, 4.1.0.Final
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Priority: Minor
Fix For: 4.2.0.CR2, 4.2.0.Final
Memcached protocol says https://github.com/memcached/memcached/blob/master/doc/protocol.txt:
"stats <args>\r\n
Depending on <args>, various internal data is sent by the server. The
kinds of arguments and the data sent are not documented in this vesion
of the protocol, and are subject to change for the convenience of
memcache developers."
Hence, we don't support <args> passed to stats. So, on one side, http://community.jboss.org/docs/DOC-14644
needs to be updated in order to indicate the fact that this is not supported.
And the other hand, if someone passes <args>, we should throw an server error (or client error rather?)
indicating that <args> is not supported. For sure, the entire line needs to be read.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (ISPN-785) In Memcached, numbers surpassing limits should produce friendlier error messages
by Galder Zamarreño (JIRA)
In Memcached, numbers surpassing limits should produce friendlier error messages
--------------------------------------------------------------------------------
Key: ISPN-785
URL: https://jira.jboss.org/browse/ISPN-785
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 4.2.0.BETA1, 4.1.0.Final
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Priority: Minor
Fix For: 4.2.0.CR1, 4.2.0.Final
The upper limit on item size is now given by max Integer size: 2147483647, because we parse the number as Integer.
when I try to allocate space for an item 2147483648 bytes big, it says
SERVER_ERROR org.infinispan.server.core.ServerException: java.lang.NumberFormatException: For input string: "2147483648"
which is kinda user unfriendly...
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month