January 2013 - infinispan-issues - Jboss List Archives

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

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2670?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2670: -------------------------------- Fix Version/s: (was: 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.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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2647) ReplaceCommand does not perform any modifications if the entry was not yet transfered during rehashing

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2647?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2647: -------------------------------- Fix Version/s: 5.2.0.Final (was: 5.2.0.CR2) > ReplaceCommand does not perform any modifications if the entry was not yet transfered during rehashing > ------------------------------------------------------------------------------------------------------ > > Key: ISPN-2647 > URL: https://issues.jboss.org/browse/ISPN-2647 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 5.2.0.Beta5 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 5.2.0.Final > > > The local data container does not have the entry yet so the ReplaceCommand fails. See BaseDistStateTransferConsistencyTest.testReplace() and BaseReplStateTransferConsistencyTest.testReplace(). -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2733) Issue with the release script (bin/release.py)

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2733: ----------------------------------- Summary: Issue with the release script (bin/release.py) Key: ISPN-2733 URL: https://issues.jboss.org/browse/ISPN-2733 Project: Infinispan Issue Type: Bug Affects Versions: 5.2.0.CR1 Reporter: Mircea Markus Assignee: Tristan Tarrant Priority: Critical Fix For: 5.2.0.Final I get the following exception when running the release script: {quote} [INFO] Step 6: Uploading Artifacts Traceback (most recent call last): File "./bin/release.py", line 367, in <module> release() File "./bin/release.py", line 332, in release do_task(upload_artifacts, [base_dir % "as-modules", version], async_processes) TypeError: not all arguments converted during string formatting {quote} Seems like there's an incorrect string concatenation at line 332: {code} do_task(upload_artifacts, [base_dir % "as-modules", version], async_processes) {code} Using string concatenation seems to solve the problem: {code} do_task(upload_artifacts, [base_dir + "/as-modules", version], async_processes) {code} -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2421) Optimise the call to LocalTransaction.getCommitNodes

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2421?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2421: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1589 > Optimise the call to LocalTransaction.getCommitNodes > ---------------------------------------------------- > > Key: ISPN-2421 > URL: https://issues.jboss.org/browse/ISPN-2421 > Project: Infinispan > Issue Type: Sub-task > Affects Versions: 5.2.0.Beta2 > Reporter: Mircea Markus > Assignee: Adrian Nistor > Fix For: 5.2.0.Final > > > Once ISPN-2420 is in place, we can optimise LocaTransaction.getCommitNodes to only calculate the destination IFF the topologyId has changed between the tx being prepared and now. > And we should also remove TransactionTable.useStrictTopologyIdComparison() and simplify all code that relied on it in AbstractTxLockingInterceptor. -- 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

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2421) Optimise the call to LocalTransaction.getCommitNodes

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2421?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2421: -------------------------------- Description: Once ISPN-2420 is in place, we can optimise LocaTransaction.getCommitNodes to only calculate the destination IFF the topologyId has changed between the tx being prepared and now. And we should also remove TransactionTable.useStrictTopologyIdComparison() and simplify all code that relied on it in AbstractTxLockingInterceptor. was:Once ISPN-2420 is in place, we can optimise LocaTransaction.getCommitNodes to only calculate the destination IFF the topologyId has changed between the tx being prepared and now. > Optimise the call to LocalTransaction.getCommitNodes > ---------------------------------------------------- > > Key: ISPN-2421 > URL: https://issues.jboss.org/browse/ISPN-2421 > Project: Infinispan > Issue Type: Sub-task > Affects Versions: 5.2.0.Beta2 > Reporter: Mircea Markus > Assignee: Adrian Nistor > Fix For: 5.2.0.Final > > > Once ISPN-2420 is in place, we can optimise LocaTransaction.getCommitNodes to only calculate the destination IFF the topologyId has changed between the tx being prepared and now. > And we should also remove TransactionTable.useStrictTopologyIdComparison() and simplify all code that relied on it in AbstractTxLockingInterceptor. -- 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

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2421) Optimise the call to LocalTransaction.getCommitNodes

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2421?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2421: -------------------------------- Assignee: Adrian Nistor (was: Mircea Markus) Fix Version/s: 5.2.0.Final (was: 6.0.0.Final) Affects Version/s: 5.2.0.Beta2 > Optimise the call to LocalTransaction.getCommitNodes > ---------------------------------------------------- > > Key: ISPN-2421 > URL: https://issues.jboss.org/browse/ISPN-2421 > Project: Infinispan > Issue Type: Sub-task > Affects Versions: 5.2.0.Beta2 > Reporter: Mircea Markus > Assignee: Adrian Nistor > Fix For: 5.2.0.Final > > > Once ISPN-2420 is in place, we can optimise LocaTransaction.getCommitNodes to only calculate the destination IFF the topologyId has changed between the tx being prepared and now. -- 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

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2732) Support more efficient operations when value is a collection

by Ray Tsang (JIRA)

Ray Tsang created ISPN-2732: ------------------------------- Summary: Support more efficient operations when value is a collection Key: ISPN-2732 URL: https://issues.jboss.org/browse/ISPN-2732 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Reporter: Ray Tsang Assignee: Mircea Markus Support operations such as append, push/pop, etc for being able to store collection/list as value Support operation such as slice to retrieve parts of collections. Some collections in mind are: Deque, PriorityQueue (heap, sorted list), etc. Perhaps expand on Delta and DeltaAware, and as counterparts to AtomicHashMap. If using current map interface, maybe something along the line of: map.put("key", new AppendDelta("...")); map.get("key", new RangeSlice(1, 5)); or advancedCache.applyDelta(...); and advancedCache.retrieveSlice(...)? -- 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

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2731) NPE in XSiteAdminOperations

by Erik Salter (JIRA)

Erik Salter created ISPN-2731: --------------------------------- Summary: NPE in XSiteAdminOperations Key: ISPN-2731 URL: https://issues.jboss.org/browse/ISPN-2731 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 5.2.0.CR1 Reporter: Erik Salter Assignee: Mircea Markus If an XSite JMX operation fails because of a node being down/suspected, a null response is put into the aggregate map. (We've seen a variation of this where the response is dropped by UNICAST2 and the operation times out before JGroups retransmits it) This causes a NPE in XSiteAdminOperations line 241. -- 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

11 years, 12 months

1
0
0 / 0

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

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2632?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2632: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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: Dan Berindei > Priority: Blocker > 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

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2420) Increment the topology id when a node leaves the cache

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2420?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2420: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Increment the topology id when a node leaves the cache > ------------------------------------------------------ > > Key: ISPN-2420 > URL: https://issues.jboss.org/browse/ISPN-2420 > Project: Infinispan > Issue Type: Feature Request > Components: State transfer > Affects Versions: 5.2.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 6.0.0.Final > > > We currently increment the topology id only when we "rebalance" the consistent hash (i.e. we add new owners). This allows us to to do some optimizations after a leave, like not forwarding commands (because there are no new owners). > Unfortunately, it is not very intuitive, because it doesn't match how JGroups works, so it can cause bugs like ISPN-2417. > Additionally, it turns out there are many places where we care that a node left, so the code is more complex to handle this (e.g. TransactionTable.useStrictTopologyIdComparison()), or it is more slow for the common case when there is no leaver (e.g. LocalTransaction.getCommitNodes()). -- 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

11 years, 12 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2013