December 2012 - infinispan-issues

[JBoss JIRA] (ISPN-2574) Segment transfer not restarted if the owner fails

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2574?page=com.atlassian.jira.plugin.... ] Adrian Nistor edited comment on ISPN-2574 at 12/6/12 8:41 AM: -------------------------------------------------------------- Closing this so it can go to QE. Created a separate issue for the unit test: ISPN-2596 was (Author: anistor): Closing this so it can go to QE. Created a separate issue for the unit test: ISPN-2569 > Segment transfer not restarted if the owner fails > ------------------------------------------------- > > Key: ISPN-2574 > URL: https://issues.jboss.org/browse/ISPN-2574 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 5.2.0.Beta4 > Reporter: Radim Vansa > Assignee: Adrian Nistor > Priority: Critical > Fix For: 5.2.0.CR1 > > > Imagine this situation in distributed cache with 3 owners: > 1) The segment X is owned by nodes A, B, C > 2) Node B fails -> CH_UPDATE and then REBALANCE_START are broadcasted > 3) Node D starts transfer of segment X from C > 4) Node C fails -> another CH_UPDATE is broadcasted > 5) D handes the CH_UPDATE and removes the transfer of segment X from C, but does not start another transfer from A > The {{addedSegments}} does not contain the restarted transfer, because all transfers from write consistent hash are removed from it in the beginning - the segment is considered received here although the transfer is still in progress. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2574) Segment transfer not restarted if the owner fails

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2574?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2574: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Closing this so it can go to QE. Created a separate issue for the unit test: ISPN-2569 > Segment transfer not restarted if the owner fails > ------------------------------------------------- > > Key: ISPN-2574 > URL: https://issues.jboss.org/browse/ISPN-2574 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 5.2.0.Beta4 > Reporter: Radim Vansa > Assignee: Adrian Nistor > Priority: Critical > Fix For: 5.2.0.CR1 > > > Imagine this situation in distributed cache with 3 owners: > 1) The segment X is owned by nodes A, B, C > 2) Node B fails -> CH_UPDATE and then REBALANCE_START are broadcasted > 3) Node D starts transfer of segment X from C > 4) Node C fails -> another CH_UPDATE is broadcasted > 5) D handes the CH_UPDATE and removes the transfer of segment X from C, but does not start another transfer from A > The {{addedSegments}} does not contain the restarted transfer, because all transfers from write consistent hash are removed from it in the beginning - the segment is considered received here although the transfer is still in progress. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2596) Create unit test for ISPN-2574

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-2596: ----------------------------------- Summary: Create unit test for ISPN-2574 Key: ISPN-2596 URL: https://issues.jboss.org/browse/ISPN-2596 Project: Infinispan Issue Type: Task Components: State transfer Affects Versions: 5.2.0.Beta4 Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 5.2.0.Beta6 ISPN-2574 was fixed and closed without a unit test, and we want one. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2574) Segment transfer not restarted if the owner fails

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2574?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-2574: ------------------------------------- Ok, let's close this and create a separate issue for the unit test. > Segment transfer not restarted if the owner fails > ------------------------------------------------- > > Key: ISPN-2574 > URL: https://issues.jboss.org/browse/ISPN-2574 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 5.2.0.Beta4 > Reporter: Radim Vansa > Assignee: Adrian Nistor > Priority: Critical > Fix For: 5.2.0.CR1 > > > Imagine this situation in distributed cache with 3 owners: > 1) The segment X is owned by nodes A, B, C > 2) Node B fails -> CH_UPDATE and then REBALANCE_START are broadcasted > 3) Node D starts transfer of segment X from C > 4) Node C fails -> another CH_UPDATE is broadcasted > 5) D handes the CH_UPDATE and removes the transfer of segment X from C, but does not start another transfer from A > The {{addedSegments}} does not contain the restarted transfer, because all transfers from write consistent hash are removed from it in the beginning - the segment is considered received here although the transfer is still in progress. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2508) The async executor is executed synchronously

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2508?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2508: ----------------------------------------------- Anna Manukyan <amanukya(a)redhat.com> made a comment on [bug 869174|https://bugzilla.redhat.com/show_bug.cgi?id=869174] Hi Galder, thanks a lot for hint. The interesting thing is that, this assertion was passing successfully during JDG 6.0.1.CR1 testing, but after adding some logs, I've got what was wrong. The test is fixed. Best regards, Anna. > The async executor is executed synchronously > --------------------------------------------- > > Key: ISPN-2508 > URL: https://issues.jboss.org/browse/ISPN-2508 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Anna Manukyan > Assignee: Galder Zamarreño > Labels: testsuite_stability > > The functional tests which are testing the custom asynchronous executor, are failing with JDG-6.1.0.ER1 build due to the following reason: > the tests are verifying that the executor was executed in separate thread, i.e. asynchronously, but starting from the new Infinispan version, the executor's execution thread is the same as the one where the test is executed. > You can find the failing test results here: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-jdbc-cache-sto... > and here: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-jdbc-cache-sto... > The test is located here: > https://svn.devel.redhat.com/repos/jboss-qa/jdg/jdg-functional-tests/trun... > Best regards, > Anna. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2595) Consistent hash factory configuration is ignored

by Dan Berindei (JIRA)

Dan Berindei created ISPN-2595: ---------------------------------- Summary: Consistent hash factory configuration is ignored Key: ISPN-2595 URL: https://issues.jboss.org/browse/ISPN-2595 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.2.0.Beta5 Reporter: Dan Berindei Assignee: Dan Berindei Priority: Blocker Fix For: 5.2.0.Beta6 HashConfigurationBuilder.create() ignores the consistent hash configured by the user. Instead it always creates the HashConfiguration with a {{null}} consistent hash factory, which means one of DefaultConsistentHashFactory and TopologyAwareConsistentHashFactory is picked based on the transport properties. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2008) Optimistic concurrency in REST server is not using atomic operations

by Eugen Dück (JIRA)

Eugen Dück created ISPN-2008: -------------------------------- Summary: Optimistic concurrency in REST server is not using atomic operations Key: ISPN-2008 URL: https://issues.jboss.org/browse/ISPN-2008 Project: Infinispan Issue Type: Bug Affects Versions: 5.1.4.CR1 Reporter: Eugen Dück Assignee: Manik Surtani The REST server's optimistic currency control is not atomic. The sequence in e.g. a PUT request goes like this: * request.evaluatePreconditions * cache.put (if preconditions met) Which is not inside any lock (that would make it pessimistic, anyway), in other words, a race condition. This applies to the optimistic variants of PUT, POST, and DELETE. -- 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 years, 1 month

4
9
0 / 0

[JBoss JIRA] (ISPN-2594) CLI should prompt for password when connection requires it

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2594: ------------------------------------- Summary: CLI should prompt for password when connection requires it Key: ISPN-2594 URL: https://issues.jboss.org/browse/ISPN-2594 Project: Infinispan Issue Type: Enhancement Components: CLI Affects Versions: 5.2.0.Beta5 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 5.2.0.Beta6 -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2300) Versioned Transactional Cache issues

by Pedro Ruivo (JIRA)

Pedro Ruivo created ISPN-2300: --------------------------------- Summary: Versioned Transactional Cache issues Key: ISPN-2300 URL: https://issues.jboss.org/browse/ISPN-2300 Project: Infinispan Issue Type: Bug Components: Transactions Affects Versions: 5.2.0.Alpha3 Reporter: Pedro Ruivo Assignee: Mircea Markus Description from http://lists.jboss.org/pipermail/infinispan-dev/2012-September/011205.html 1) testPutIfAbsent, testRemoveIfPresent, testReplaceWithOldVal (methods the test cases) In this tests, it was updating the cache entry with a null version. This originates later a IllegalStateException when it tries to perform the write skew check and the version is null. I have fixed this problem in this way: if the command fails (PutCommand, RemoveCommand, ReplaceCommand), I unset the flag CHANGED in the MvccEntry to avoid to update the entry in the DataContainer. 2) testClear in distributed mode I have no clear idea how to solve this problem but it looks like the PrepareCommand (with the ClearCommand) is not sent to all the nodes in the cluster. Then, when I do a get, a remote get is performed and the key is still there. I think that it is not the desired behavior. 3) testRemoveUnexistingEntry In this test, it tries to remove a key that does not exists but it does not success due to a NullPointerException. I have looked deeper and I check that the transaction's lookup entries map has an entry with [key => null] and when it tries to perform the write skew check in that key, a NullPointerException is thrown in here [2] (line 80, WriteSkewHelper) [1] https://github.com/pruivo/infinispan/tree/t_replace_fix [2] https://github.com/pruivo/infinispan/blob/t_replace_fix/core/src/main/jav... -- 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, 1 month

4
8
0 / 0

[JBoss JIRA] (ISPN-2593) Introduce clustered.sh/clustered.xml in lieu of standalone-ha

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2593: ------------------------------------- Summary: Introduce clustered.sh/clustered.xml in lieu of standalone-ha Key: ISPN-2593 URL: https://issues.jboss.org/browse/ISPN-2593 Project: Infinispan Issue Type: Feature Request Components: Server Reporter: Tristan Tarrant Assignee: Tristan Tarrant provide a means to launch a default-clustered instance with a configuration that is optimized for most usecases. For example, a separate 'clustered' profile or shell script. Likewise, the standalone-ha.xml file should be renamed in a less EAP-centric manner. -- 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, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2012