January 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2707) Trace log in EntryWrappingInterceptor sorely slows down ST

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-2707?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-2707: ------------------------------ Summary: Trace log in EntryWrappingInterceptor sorely slows down ST (was: Trace log in EntryWrappingInterceptor hardly slows down ST) > Trace log in EntryWrappingInterceptor sorely slows down ST > ---------------------------------------------------------- > > Key: ISPN-2707 > URL: https://issues.jboss.org/browse/ISPN-2707 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 5.2.0.CR1 > Reporter: Radim Vansa > Assignee: Mircea Markus > Priority: Critical > Fix For: 5.2.0.CR2 > > > In {{EntryWrappingInterceptor.visitInvalidateL1Command}} there is a trace log which does not check if the trace is enabled - with invalidate command with a lot of keys (such as in case of ST) this would construct for each of these keys really long strings (with all the keys...), and then throw it off. > Moreover, the InvalidateL1Command is still built even if I don't have L1 enabled, but that's another issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2707) Trace log in EntryWrappingInterceptor hardly slows down ST

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2707?page=com.atlassian.jira.plugin.... ] Mircea Markus resolved ISPN-2707. --------------------------------- Resolution: Done > Trace log in EntryWrappingInterceptor hardly slows down ST > ---------------------------------------------------------- > > Key: ISPN-2707 > URL: https://issues.jboss.org/browse/ISPN-2707 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 5.2.0.CR1 > Reporter: Radim Vansa > Assignee: Mircea Markus > Priority: Critical > Fix For: 5.2.0.CR2 > > > In {{EntryWrappingInterceptor.visitInvalidateL1Command}} there is a trace log which does not check if the trace is enabled - with invalidate command with a lot of keys (such as in case of ST) this would construct for each of these keys really long strings (with all the keys...), and then throw it off. > Moreover, the InvalidateL1Command is still built even if I don't have L1 enabled, but that's another issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2707) Trace log in EntryWrappingInterceptor hardly slows down ST

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2707?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2707: -------------------------------- Fix Version/s: 5.2.0.CR2 > Trace log in EntryWrappingInterceptor hardly slows down ST > ---------------------------------------------------------- > > Key: ISPN-2707 > URL: https://issues.jboss.org/browse/ISPN-2707 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 5.2.0.CR1 > Reporter: Radim Vansa > Assignee: Mircea Markus > Priority: Critical > Fix For: 5.2.0.CR2 > > > In {{EntryWrappingInterceptor.visitInvalidateL1Command}} there is a trace log which does not check if the trace is enabled - with invalidate command with a lot of keys (such as in case of ST) this would construct for each of these keys really long strings (with all the keys...), and then throw it off. > Moreover, the InvalidateL1Command is still built even if I don't have L1 enabled, but that's another issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2632) Uneven request balancing after node crash

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2632?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-2632: ---------------------------------------- @Michal, one final question: I see 5 driver threads in each client. I assume each of these threads is using its own RemoteCacheManager instance? > Uneven request balancing after node crash > ----------------------------------------- > > Key: ISPN-2632 > URL: https://issues.jboss.org/browse/ISPN-2632 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.CR1 > Reporter: Michal Linhard > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 5.2.0.CR2, 5.2.0.Final > > > This is a new manifestation of ISPN-1995, but in this case this happens after killing only one node: the hot rod requests aren't very well balanced. > these runs still manifest also ISPN-2550 and it may be cause of this bug. > The uneven balancing of requests can be seen here: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2707) Trace log in EntryWrappingInterceptor hardly slows down ST

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-2707?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-2707: ------------------------------ Summary: Trace log in EntryWrappingInterceptor hardly slows down ST (was: Trace log in EntryWrappingInterceptor could deteriorate performance) > Trace log in EntryWrappingInterceptor hardly slows down ST > ---------------------------------------------------------- > > Key: ISPN-2707 > URL: https://issues.jboss.org/browse/ISPN-2707 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 5.2.0.CR1 > Reporter: Radim Vansa > Assignee: Mircea Markus > > In {{EntryWrappingInterceptor.visitInvalidateL1Command}} there is a trace log which does not check if the trace is enabled - with invalidate command with a lot of keys (such as in case of ST) this would construct for each of these keys really long strings (with all the keys...), and then throw it off. > Moreover, the InvalidateL1Command is still built even if I don't have L1 enabled, but that's another issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2632) Uneven request balancing after node crash

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2632?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-2632: ---------------------------------------- If so, I wonder if the issue can be replicated with just 1 driver thread per client, so 10 clients. This would make debugging through the client logs easier. > Uneven request balancing after node crash > ----------------------------------------- > > Key: ISPN-2632 > URL: https://issues.jboss.org/browse/ISPN-2632 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.CR1 > Reporter: Michal Linhard > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 5.2.0.CR2, 5.2.0.Final > > > This is a new manifestation of ISPN-1995, but in this case this happens after killing only one node: the hot rod requests aren't very well balanced. > these runs still manifest also ISPN-2550 and it may be cause of this bug. > The uneven balancing of requests can be seen here: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2707) Trace log in EntryWrappingInterceptor hardly slows down ST

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-2707?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-2707: ------------------------------ Priority: Critical (was: Major) > Trace log in EntryWrappingInterceptor hardly slows down ST > ---------------------------------------------------------- > > Key: ISPN-2707 > URL: https://issues.jboss.org/browse/ISPN-2707 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 5.2.0.CR1 > Reporter: Radim Vansa > Assignee: Mircea Markus > Priority: Critical > > In {{EntryWrappingInterceptor.visitInvalidateL1Command}} there is a trace log which does not check if the trace is enabled - with invalidate command with a lot of keys (such as in case of ST) this would construct for each of these keys really long strings (with all the keys...), and then throw it off. > Moreover, the InvalidateL1Command is still built even if I don't have L1 enabled, but that's another issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2632) Uneven request balancing after node crash

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2632?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-2632: ---------------------------------------- Actually, ISPN-2670 is about the server module's test client, so not really relevant here. It's worth testing with other protocol versions, 1.1 and 1.0, to see if this problem is specific to protocol version 1.2. @Michal, in terms of uneven request balancing, do you know if the request unbalancing happens for all clients? Or if only some of those suffer? > Uneven request balancing after node crash > ----------------------------------------- > > Key: ISPN-2632 > URL: https://issues.jboss.org/browse/ISPN-2632 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.CR1 > Reporter: Michal Linhard > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 5.2.0.CR2, 5.2.0.Final > > > This is a new manifestation of ISPN-1995, but in this case this happens after killing only one node: the hot rod requests aren't very well balanced. > these runs still manifest also ISPN-2550 and it may be cause of this bug. > The uneven balancing of requests can be seen here: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2632) Uneven request balancing after node crash

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2632?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-2632: ---------------------------------------- @Michal, in the mean time you could try running the clients with infinispan.client.hotrod.protocol_version=1.1 ? The default protocol is 1.2 (even if RemoteCacheManager says otherwise...) > Uneven request balancing after node crash > ----------------------------------------- > > Key: ISPN-2632 > URL: https://issues.jboss.org/browse/ISPN-2632 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.CR1 > Reporter: Michal Linhard > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 5.2.0.CR2, 5.2.0.Final > > > This is a new manifestation of ISPN-1995, but in this case this happens after killing only one node: the hot rod requests aren't very well balanced. > these runs still manifest also ISPN-2550 and it may be cause of this bug. > The uneven balancing of requests can be seen here: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2670) Update HotRod test client in server module to work with protocol version 1.2

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2670?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2670: ----------------------------------- Fix Version/s: 5.2.0.CR2 > Update HotRod test client in server module to work with protocol version 1.2 > ---------------------------------------------------------------------------- > > Key: ISPN-2670 > URL: https://issues.jboss.org/browse/ISPN-2670 > Project: Infinispan > Issue Type: Task > Components: Remote protocols, Test Suite > Affects Versions: 5.2.0.Beta6 > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Fix For: 5.2.0.CR2, 5.2.0.Final > > > The HotRod server test suite doesn't cover protocol version 1.2, and the test client doesn't actually work with this version. > I created a new test based on HotRodMultiNodeTest and when I changed the version to 12, the first ping operation failed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2013