4:57 a.m.
Galder Zamarreño created ISPN-2015:
--------------------------------------
Summary: Upgrade to Netty 3.4.2 when ready
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
9:06 a.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2015:
----------------------------------------
Try the following snapshot and see if the testsuite works fine:
https://oss.sonatype.org/content/repositories/snapshots/io/netty/netty/3....
If it does, pass it on to QE to compare perf.
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
2:44 a.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2015:
----------------------------------------
Ok, I've made some changes to get rid of the custom replaying decoder and now the
testsuite works. The branch can be found in:
https://github.com/galderz/infinispan/tree/t_2015_5
I've added a repository for the Sonatype snapshots. This will be picked by QE to run
the tests above and see if we see improvements. This upgrade should in theory solve the
issue that resulted in coding the workaround for ISPN-1383.
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
12:09 p.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2015:
----------------------------------------
3.4.2 is out now - http://repo2.maven.org/maven2/io/netty/netty/3.4.2.Final/
I'll update the branch asap.
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
12:44 p.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Norman Maurer commented on ISPN-2015:
-------------------------------------
Let mr know if it work out .
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
12:44 p.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Norman Maurer edited comment on ISPN-2015 at 4/27/12 1:44 PM:
--------------------------------------------------------------
Let me know if it work out .
was (Author: normanmaurer):
Let mr know if it work out .
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
3:35 a.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Tristan Tarrant commented on ISPN-2015:
---------------------------------------
Since EAP will use Netty 3.4.2, we need to at least test that the upgrade works in
Infinispan 5.1.x as well
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
3:52 a.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2015:
----------------------------------------
Branch updated with 3.4.2.Final. Testsuite looks good once the custom replaying decoder
has been removed both in 5.1.x and master.
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
4:36 a.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Manik Surtani updated ISPN-2015:
--------------------------------
Fix Version/s: 5.1.5.redhat
Affects Version/s: 5.1.3.FINAL
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Affects Versions: 5.1.3.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.5.redhat, 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
1:50 p.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Norman Maurer commented on ISPN-2015:
-------------------------------------
@Galder so the memory consumation looks ok without your decoder ?
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Affects Versions: 5.1.3.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.x, 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
3:26 a.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2015:
----------------------------------------
@Norman, don't know yet. I've only run our functional testsuite. We have some
stress tests that QE runs that will test that.
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Affects Versions: 5.1.3.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.x, 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
4:58 a.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Norman Maurer commented on ISPN-2015:
-------------------------------------
@Galder, ah ok I see
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Affects Versions: 5.1.3.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.x, 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
5:33 a.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2015:
----------------------------------------
@Norman, I've run some performance tests locally (see
https://docs.jboss.org/author/x/FQY5), and Netty 3.4.2 shows a performance drop of around
5-10% approx. Bear in mind that my tests are not as client heavy as the ones QE runs (the
snapshot I sent you are from those) and they do not run for that long. You can run my
Grinder tests locally using the instructions in the wiki.
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Affects Versions: 5.1.3.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.x, 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
5:44 a.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Norman Maurer commented on ISPN-2015:
-------------------------------------
@Galder, I will try to investigate futher tomorrow (I hope I find the time)
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Affects Versions: 5.1.3.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.x, 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
3:19 a.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Norman Maurer commented on ISPN-2015:
-------------------------------------
@Galder I took some time today to benchmark and I must say that I can not see a
performance drop. I even had some performance gain with 3.4.2.Final here ( but its really
small). Maybe it depends on the cpu count ?
I tested with two infinispan distributions.
1) git reset --hard de4d48b7c0c4d91e2886e4130cf589e66d7888de (which is exactly one commit
before upgrade to netty 3.4.2.Final)
2) git checkout t_2015_m
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Affects Versions: 5.1.3.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.x, 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
3:19 a.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2015:
----------------------------------------
@Norman, which server did you test exactly? Still Memcached? And what kind of loads did
you apply?
Btw, I was testing JDG, which is the data grid server, which deploys the memcached, hotrod
and rest endpoints. You can build it from https://github.com/infinispan/jdg. Shouldn't
be a difference.
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Affects Versions: 5.1.3.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.x, 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
3:25 a.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Norman Maurer commented on ISPN-2015:
-------------------------------------
I was just using "startHotRodAgent.sh" as it is documented in the wiki. Building
the distribution with "mvn clean package assembly:assembly".
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Affects Versions: 5.1.3.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.x, 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
4:05 a.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2015:
----------------------------------------
Ok, can you try startMemcachedAgent.sh and start the Memcached server (-r memcached)?
What load are you using? By default this is 400 ops per thread, with 100 threads.
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Affects Versions: 5.1.3.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.x, 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
3:03 a.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Norman Maurer commented on ISPN-2015:
-------------------------------------
@Galder netty 3.4.4.Final is out. You want to test with this if you plan to upgrade
anyway
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Affects Versions: 5.1.3.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.x, 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
3:43 a.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Tristan Tarrant commented on ISPN-2015:
---------------------------------------
The Netty 3.4.4.Final build requires Java 7 to build, so I guess JDG 6.0.0 will be
released with 3.2.6.Final instead.
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Affects Versions: 5.1.3.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.x, 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
3:47 a.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Norman Maurer commented on ISPN-2015:
-------------------------------------
@Tristan Java7 is only need to build netty but its usable with Java 5+. This is because we
enable/disable features/optimizations based on the Java version at runtime. So no need to
worry.
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Affects Versions: 5.1.3.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.x, 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
3:53 a.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Tristan Tarrant commented on ISPN-2015:
---------------------------------------
Norman, productized packages are built in a specific environment. I cannot import a
binary.
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Affects Versions: 5.1.3.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.x, 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
4:50 a.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2015:
----------------------------------------
I'm holding off sending a pull req for this yet since we've found some exceptions
while testing 3.4.4:
{code}10:43:05,805 ERROR [org.infinispan.server.hotrod.HotRodDecoder]
(HotRodClientMaster-30) ISPN005009: Unexpected error before any request parameters read:
java.lang.UnsupportedOperationException
at java.util.AbstractList.add(AbstractList.java:131) [rt.jar:1.6.0_30]
at java.util.AbstractList.add(AbstractList.java:91) [rt.jar:1.6.0_30]
at
org.jboss.netty.buffer.CompositeChannelBuffer.discardReadBytes(CompositeChannelBuffer.java:640)
[netty-3.4.4.Final.jar:]
at
org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:487)
[netty-3.4.4.Final.jar:]
at
org.infinispan.server.core.AbstractProtocolDecoder.messageReceived(AbstractProtocolDecoder.scala:369)
[infinispan-server-core-5.1.5.ER8-redhat-1.jar:5.1.5.ER8-redhat-1]
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)
[netty-3.4.4.Final.jar:]
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)
[netty-3.4.4.Final.jar:]
at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:94)
[netty-3.4.4.Final.jar:]
at
org.jboss.netty.channel.socket.nio.AbstractNioWorker.processSelectedKeys(AbstractNioWorker.java:372)
[netty-3.4.4.Final.jar:]
at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:246)
[netty-3.4.4.Final.jar:]
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:38)
[netty-3.4.4.Final.jar:]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[rt.jar:1.6.0_30]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[rt.jar:1.6.0_30]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]{code}
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Affects Versions: 5.1.3.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.x, 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
6:38 a.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Norman Maurer commented on ISPN-2015:
-------------------------------------
@Galder I fixed this and deployed a snapshot which contains the fix. Could you please try
this out and let me know if it works ?
You can find the snapshot here:
https://oss.sonatype.org/content/repositories/snapshots/io/netty/netty/3....
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Affects Versions: 5.1.3.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.x, 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
11:41 a.m.
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-2015:
-----------------------------------
Fix Version/s: 5.1.5.FINAL
(was: 5.1.5.CR1)
Upgrade to Netty 3.4.2 when ready
---------------------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Affects Versions: 5.1.3.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.5.FINAL, 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
9:24 a.m.
New subject: [JBoss JIRA] (ISPN-2015) Upgrade to Netty 3.4.5
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-2015:
-----------------------------------
Summary: Upgrade to Netty 3.4.5 (was: Upgrade to Netty 3.4.2 when ready)
Upgrade to Netty 3.4.5
----------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Affects Versions: 5.1.3.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.5.FINAL, 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
9:24 a.m.
New subject: [JBoss JIRA] (ISPN-2015) Upgrade to Netty 3.4.5
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-2015:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/1123
Upgrade to Netty 3.4.5
----------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Affects Versions: 5.1.3.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.5.FINAL, 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
10:24 a.m.
New subject: [JBoss JIRA] (ISPN-2015) Upgrade to Netty 3.4.5
[
https://issues.jboss.org/browse/ISPN-2015?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2015:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
Upgrade to Netty 3.4.5
----------------------
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Affects Versions: 5.1.3.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.5.FINAL, 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this
version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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
4357
days inactive
4383
days old
infinispan-issues@lists.jboss.org
27 comments
5 participants
participants (5)
-
Galder Zamarreño (JIRA) -
Manik Surtani (JIRA)
-
Mircea Markus (JIRA)
-
Norman Maurer (JIRA)
-
Tristan Tarrant (JIRA)