August 2013 - infinispan-issues - Jboss List Archives

[Community] Announcement: Planed outage: 2013-08-24 5:00 PM UTC

by Libor Krzyžanek

Libor Krzyžanek [https://community.jboss.org/people/lkrzyzanek] posted the announcement <b>Announcement</b>: "Planed outage: 2013-08-24 5:00 PM UTC" To view the announcement, visit: https://community.jboss.org/index.jspa -------------------------------------------------------------- Forums/Wiki/Blogs at community.jboss.org will be unavailable for about 4 hours due to upgrade. -------------------------------------------------------------- Announcement expires on August 28, 2013

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3320) DistL1WriteSkewTest.testRemoveIgnoreReturnValueOnNonExistingKey fails randomly

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3320?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3320: ------------------------------ Description: http://ci.infinispan.org/viewLog.html?buildId=2456&tab=buildResultsDiv&bu... probably due to my last changes in write skew check... failing tests: * DistL1WriteSkewTest.testPutIgnoreReturnValueOnNonExistingKey * DistL1WriteSkewTest.testRemoveIgnoreReturnValueNonExistingKey * DistL1WriteSkewTest.testRemoveIgnoreReturnValueOnNonExistingKey was: http://ci.infinispan.org/viewLog.html?buildId=2456&tab=buildResultsDiv&bu... probably due to my last changes in write skew check... > DistL1WriteSkewTest.testRemoveIgnoreReturnValueOnNonExistingKey fails randomly > ------------------------------------------------------------------------------ > > Key: ISPN-3320 > URL: https://issues.jboss.org/browse/ISPN-3320 > Project: Infinispan > Issue Type: Bug > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 6.0.0.Alpha3 > > Attachments: logs.tar.gz > > > http://ci.infinispan.org/viewLog.html?buildId=2456&tab=buildResultsDiv&bu... > probably due to my last changes in write skew check... > failing tests: > * DistL1WriteSkewTest.testPutIgnoreReturnValueOnNonExistingKey > * DistL1WriteSkewTest.testRemoveIgnoreReturnValueNonExistingKey > * DistL1WriteSkewTest.testRemoveIgnoreReturnValueOnNonExistingKey -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3320) DistL1WriteSkewTest.testRemoveIgnoreReturnValueOnNonExistingKey fails randomly

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3320?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3320: ------------------------------ Attachment: logs.tar.gz > DistL1WriteSkewTest.testRemoveIgnoreReturnValueOnNonExistingKey fails randomly > ------------------------------------------------------------------------------ > > Key: ISPN-3320 > URL: https://issues.jboss.org/browse/ISPN-3320 > Project: Infinispan > Issue Type: Bug > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 6.0.0.Alpha3 > > Attachments: logs.tar.gz > > > http://ci.infinispan.org/viewLog.html?buildId=2456&tab=buildResultsDiv&bu... > probably due to my last changes in write skew check... > failing tests: > * DistL1WriteSkewTest.testPutIgnoreReturnValueOnNonExistingKey > * DistL1WriteSkewTest.testRemoveIgnoreReturnValueNonExistingKey > * DistL1WriteSkewTest.testRemoveIgnoreReturnValueOnNonExistingKey -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3419) Write Skew check must be performed only in the primary owner

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3419?page=com.atlassian.jira.plugin.... ] Work on ISPN-3419 started by Pedro Ruivo. > Write Skew check must be performed only in the primary owner > ------------------------------------------------------------ > > Key: ISPN-3419 > URL: https://issues.jboss.org/browse/ISPN-3419 > Project: Infinispan > Issue Type: Bug > Components: Transactions > Affects Versions: 6.0.0.Alpha2 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 6.0.0.Alpha3 > > > The following case can create data inconsistency: > A: txA reads k with version v1 and writes on k (say valueA) > primary-owner of k: txA acquire lock on k, validates and return v2 (increment(v1)) > non-primary-onwer of k: txA registers a backup lock, validates and returns v2 (increment(v1)) > A: txA commits with version v2. > primary-owner of k: applies txA //commit in the non-primary-owner is delayed > B: txB remote reads k with version v2 and writes on k (say valueB) and prepare the transaction > primary-owner of k: txB waits until the lock is relased. > non-primary-onwer of k: txA registers a backup lock, validates and returns v2 (increment(v1), because it has not applied the txA) > primary-owner of k: lock is release, txB is validated and it return v3 (increment(v2)) > B collects all the response and merge them. However, the map.value() can return first the response from primary-owner (v3) and them the response from the non-primary-owner (v2). The result version map will be k=>v2. > txB will update k with the same previous version and a different value. from here the data will become inconsistent. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2264) DistL1WriteSkewTest.testSharedCounter failing randomly

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-2264?page=com.atlassian.jira.plugin.... ] Work on ISPN-2264 started by Pedro Ruivo. > DistL1WriteSkewTest.testSharedCounter failing randomly > ------------------------------------------------------ > > Key: ISPN-2264 > URL: https://issues.jboss.org/browse/ISPN-2264 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Pedro Ruivo > Labels: testsuite_stability > Fix For: 6.0.0.Alpha3 > > > {code}Failed tests: > testSharedCounter(org.infinispan.container.versioning.DistL1WriteSkewTest): > Timed out waiting for updater threads{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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3419) Write Skew check must be performed only in the primary owner

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3419?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3419: ------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/2016 > Write Skew check must be performed only in the primary owner > ------------------------------------------------------------ > > Key: ISPN-3419 > URL: https://issues.jboss.org/browse/ISPN-3419 > Project: Infinispan > Issue Type: Bug > Components: Transactions > Affects Versions: 6.0.0.Alpha2 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 6.0.0.Alpha3 > > > The following case can create data inconsistency: > A: txA reads k with version v1 and writes on k (say valueA) > primary-owner of k: txA acquire lock on k, validates and return v2 (increment(v1)) > non-primary-onwer of k: txA registers a backup lock, validates and returns v2 (increment(v1)) > A: txA commits with version v2. > primary-owner of k: applies txA //commit in the non-primary-owner is delayed > B: txB remote reads k with version v2 and writes on k (say valueB) and prepare the transaction > primary-owner of k: txB waits until the lock is relased. > non-primary-onwer of k: txA registers a backup lock, validates and returns v2 (increment(v1), because it has not applied the txA) > primary-owner of k: lock is release, txB is validated and it return v3 (increment(v2)) > B collects all the response and merge them. However, the map.value() can return first the response from primary-owner (v3) and them the response from the non-primary-owner (v2). The result version map will be k=>v2. > txB will update k with the same previous version and a different value. from here the data will become inconsistent. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2264) DistL1WriteSkewTest.testSharedCounter failing randomly

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-2264?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-2264: ------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/2016 > DistL1WriteSkewTest.testSharedCounter failing randomly > ------------------------------------------------------ > > Key: ISPN-2264 > URL: https://issues.jboss.org/browse/ISPN-2264 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Pedro Ruivo > Labels: testsuite_stability > Fix For: 6.0.0.Alpha3 > > > {code}Failed tests: > testSharedCounter(org.infinispan.container.versioning.DistL1WriteSkewTest): > Timed out waiting for updater threads{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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3425) Add support for strictPeerToPeer attribute to the server distribution

by Martin Gencur (JIRA)

Martin Gencur created ISPN-3425: ----------------------------------- Summary: Add support for strictPeerToPeer attribute to the server distribution Key: ISPN-3425 URL: https://issues.jboss.org/browse/ISPN-3425 Project: Infinispan Issue Type: Feature Request Components: Server Affects Versions: 6.0.0.Alpha2 Reporter: Martin Gencur Assignee: Martin Gencur Priority: Minor Fix For: 6.0.0.CR1 The attribute has the following meaning: If set to true, RPC operations will fail if the named cache does not exist on remote nodes with a NamedCacheNotFoundException. Otherwise, operations will succeed but it will be logged on the caller that the RPC did not succeed on certain nodes due to the named cache not being available. This attribute is by default set to false and cannot be adjusted through ISPN server's configuration. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3424) exceptions.h references InetSocketAddress which is not in includes

by Radim Vansa (JIRA)

Radim Vansa created ISPN-3424: --------------------------------- Summary: exceptions.h references InetSocketAddress which is not in includes Key: ISPN-3424 URL: https://issues.jboss.org/browse/ISPN-3424 Project: Infinispan Issue Type: Bug Components: Remote protocols Affects Versions: 6.0.0.Alpha3 Reporter: Radim Vansa Assignee: Mircea Markus Priority: Minor If InetSocketAddress is an exported class, it should go to the include/ directory and nothing from include/ should include internal implementation headers. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3423) Dangling reference in C++ client

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-3423?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-3423: ------------------------------ Assignee: Mircea Markus (was: Galder Zamarreño) > Dangling reference in C++ client > -------------------------------- > > Key: ISPN-3423 > URL: https://issues.jboss.org/browse/ISPN-3423 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Reporter: Radim Vansa > Assignee: Mircea Markus > Priority: Minor > > I've noticed that {{Configuration::getProtocolVerision()}} produces a dangling reference - the {{std::string}} is autoconstructed on place from the {{const char *}} and then we return a reference to this temporary variable. -- 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

12 years, 7 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 August 2013