December 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3828) RemoteQueryDslConditionsFilestoreTest and HotRodQueryFileSystemTest must cleanup the filesystem index before starting

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3828?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-3828: ------------------------------------- This applies to other query and remote query tests too. > RemoteQueryDslConditionsFilestoreTest and HotRodQueryFileSystemTest must cleanup the filesystem index before starting > --------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-3828 > URL: https://issues.jboss.org/browse/ISPN-3828 > Project: Infinispan > Issue Type: Bug > Components: Querying, Test Suite > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3327) Server init.d script should be customized for Infinispan

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3327?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3327: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 983781|https://bugzilla.redhat.com/show_bug.cgi?id=983781] from ASSIGNED to POST > Server init.d script should be customized for Infinispan > -------------------------------------------------------- > > Key: ISPN-3327 > URL: https://issues.jboss.org/browse/ISPN-3327 > Project: Infinispan > Issue Type: Bug > Reporter: NadirX > Assignee: Tristan Tarrant > Labels: 620 > Fix For: 6.0.0.Alpha4 > > > The current init.d script included in Infinispan Server should be appropriately renamed and verified -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3830) Conditional Operation can fail erroneously during ST

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3830?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-3830: ------------------------------------ This is related to my fix for ISPN-3422. > Conditional Operation can fail erroneously during ST > ---------------------------------------------------- > > Key: ISPN-3830 > URL: https://issues.jboss.org/browse/ISPN-3830 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Reporter: William Burns > Assignee: Dan Berindei > > Currently the retry logic for commands is to only throw a OutdatedTopologyException when a command is successful. > This however can have the following issue. > k1 owned by N1, N2 > # N3 updates k1 sending conditional command to N1 > # N1 receives command and starts running it (passes topology block) > # ST occurs causing N1 to no longer be an owner and removes k1 from it's data container. > # N1 runs optional command and it fails and thus doesn't throw OutdatedTopologyException > # N3 gets response that command failed, but it could have worked had it gone to a real owner. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3822) Server configuration should allow disabling statistics

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3822?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-3822: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Server configuration should allow disabling statistics > ------------------------------------------------------ > > Key: ISPN-3822 > URL: https://issues.jboss.org/browse/ISPN-3822 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 6.0.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.1.0.Final > > > Statistics collection has an adverse performance impact. > Add a statistics boolean attribute to both caches and containers. For backwards compatibility, maintain stats enabled by default. For the 7.x stream we should disable them by default instead. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3830) Conditional Operation can fail erroneously during ST

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3830?page=com.atlassian.jira.plugin.... ] Dan Berindei reassigned ISPN-3830: ---------------------------------- Assignee: Dan Berindei (was: Mircea Markus) > Conditional Operation can fail erroneously during ST > ---------------------------------------------------- > > Key: ISPN-3830 > URL: https://issues.jboss.org/browse/ISPN-3830 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Reporter: William Burns > Assignee: Dan Berindei > > Currently the retry logic for commands is to only throw a OutdatedTopologyException when a command is successful. > This however can have the following issue. > k1 owned by N1, N2 > # N3 updates k1 sending conditional command to N1 > # N1 receives command and starts running it (passes topology block) > # ST occurs causing N1 to no longer be an owner and removes k1 from it's data container. > # N1 runs optional command and it fails and thus doesn't throw OutdatedTopologyException > # N3 gets response that command failed, but it could have worked had it gone to a real owner. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3827) JON server plugin is NOT imported into JON properly

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3827?page=com.atlassian.jira.plugin.... ] Work on ISPN-3827 started by William Burns. > JON server plugin is NOT imported into JON properly > --------------------------------------------------- > > Key: ISPN-3827 > URL: https://issues.jboss.org/browse/ISPN-3827 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 6.0.0.Final > Reporter: Tomas Sykora > Assignee: William Burns > Labels: 620 > > See linked bugzilla. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3829) Null value read with RR can be replaced by cache loader value

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3829?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-3829: ------------------------------------- ISPN-3797 will fix this in a better fashion. However we may have to fix this for a version Infinispan 6 > Null value read with RR can be replaced by cache loader value > ------------------------------------------------------------- > > Key: ISPN-3829 > URL: https://issues.jboss.org/browse/ISPN-3829 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.0.Final > Reporter: William Burns > Assignee: Mircea Markus > > Currently the CacheLoaderInterceptor does the following check to determine if it should check the loader for a value > {code} > if (e == null || e.isNull() || e.getValue() == null) { > {code} > Unfortunately this means it checks the loader when a null value is in the entry when using RR. This can cause an issue if another transaction commits that key and puts a value that results in that value being inserted into the loader. > This also is a performance issue for RR, since it has to check the loader over and over for a given key even if it was found null the first time. > Initial thought is to do something like setSkipRemoteGet and that could actually be used for a dual purpose possibly. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3830) Conditional Operation can fail erroneously during ST

by William Burns (JIRA)

William Burns created ISPN-3830: ----------------------------------- Summary: Conditional Operation can fail erroneously during ST Key: ISPN-3830 URL: https://issues.jboss.org/browse/ISPN-3830 Project: Infinispan Issue Type: Bug Components: State transfer Reporter: William Burns Assignee: Mircea Markus Currently the retry logic for commands is to only throw a OutdatedTopologyException when a command is successful. This however can have the following issue. k1 owned by N1, N2 # N3 updates k1 sending conditional command to N1 # N1 receives command and starts running it (passes topology block) # ST occurs causing N1 to no longer be an owner and removes k1 from it's data container. # N1 runs optional command and it fails and thus doesn't throw OutdatedTopologyException # N3 gets response that command failed, but it could have worked had it gone to a real owner. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3327) Server init.d script should be customized for Infinispan

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3327?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3327: ---------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan-server/pull/125, https://github.com/infinispan/infinispan/pull/2279 (was: https://github.com/infinispan/infinispan-server/pull/125) > Server init.d script should be customized for Infinispan > -------------------------------------------------------- > > Key: ISPN-3327 > URL: https://issues.jboss.org/browse/ISPN-3327 > Project: Infinispan > Issue Type: Bug > Reporter: NadirX > Assignee: Tristan Tarrant > Labels: 620 > Fix For: 6.0.0.Alpha4 > > > The current init.d script included in Infinispan Server should be appropriately renamed and verified -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3827) JON server plugin is NOT imported into JON properly

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-3827?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-3827: -------------------------------- Assignee: William Burns (was: Mircea Markus) > JON server plugin is NOT imported into JON properly > --------------------------------------------------- > > Key: ISPN-3827 > URL: https://issues.jboss.org/browse/ISPN-3827 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 6.0.0.Final > Reporter: Tomas Sykora > Assignee: William Burns > Labels: 620 > > See linked bugzilla. -- 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

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2013