July 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3379) Move hbase cache store to its own repository

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-3379: ------------------------------------- Summary: Move hbase cache store to its own repository Key: ISPN-3379 URL: https://issues.jboss.org/browse/ISPN-3379 Project: Infinispan Issue Type: Sub-task Components: Loaders and Stores Affects Versions: 6.0.0.Alpha1 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 6.0.0.Alpha2 -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3378) Move cassandra cache store to its own repository

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3378?page=com.atlassian.jira.plugin.... ] Tristan Tarrant resolved ISPN-3378. ----------------------------------- Fix Version/s: 6.0.0.Final Resolution: Done > Move cassandra cache store to its own repository > ------------------------------------------------ > > Key: ISPN-3378 > URL: https://issues.jboss.org/browse/ISPN-3378 > Project: Infinispan > Issue Type: Sub-task > Components: Loaders and Stores > Affects Versions: 6.0.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Alpha2, 6.0.0.Final > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3378) Move cassandra cache store to its own repository

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-3378: ------------------------------------- Summary: Move cassandra cache store to its own repository Key: ISPN-3378 URL: https://issues.jboss.org/browse/ISPN-3378 Project: Infinispan Issue Type: Sub-task Components: Loaders and Stores Affects Versions: 6.0.0.Alpha1 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 6.0.0.Alpha2 -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3377) Move non-primary cachestores to their own repositories

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-3377: ------------------------------------- Summary: Move non-primary cachestores to their own repositories Key: ISPN-3377 URL: https://issues.jboss.org/browse/ISPN-3377 Project: Infinispan Issue Type: Task Components: Loaders and Stores Affects Versions: 6.0.0.Alpha1 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 6.0.0.Alpha2 -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3373) HotRod topology cache should allow disabling awaitInitialTransfer

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3373?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3373: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > HotRod topology cache should allow disabling awaitInitialTransfer > ----------------------------------------------------------------- > > Key: ISPN-3373 > URL: https://issues.jboss.org/browse/ISPN-3373 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols, Server > Affects Versions: 6.0.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Alpha2 > > > When a server with a hotrod endpoint joins a cluster where state transfer has been disabled (ISPN-3140), waiting for initial state transfer should also be disabled on the topology cache, otherwise failures occur. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3365) org.infinispan.lucene.DatabaseStoredIndexTest.indexWasStored fails with AssertionError

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3365?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3365: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > org.infinispan.lucene.DatabaseStoredIndexTest.indexWasStored fails with AssertionError > -------------------------------------------------------------------------------------- > > Key: ISPN-3365 > URL: https://issues.jboss.org/browse/ISPN-3365 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Affects Versions: 6.0.0.Alpha1 > Environment: RHEL5_x86_64, IBMJDK1.7 > Reporter: Vitalii Chepeliuk > Assignee: Sanne Grinovero > Labels: testsuite_stability > Attachments: infinispan-lucene-v3.log.zip > > > Stacktrace > java.lang.AssertionError: > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:24) > at org.testng.AssertJUnit.assertFalse(AssertJUnit.java:41) > at org.testng.AssertJUnit.assertFalse(AssertJUnit.java:49) > at org.infinispan.lucene.DatabaseStoredIndexTest.indexWasStored(DatabaseStoredIndexTest.java:111) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:613) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:715) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:345) > at java.util.concurrent.FutureTask.run(FutureTask.java:177) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:626) > at java.lang.Thread.run(Thread.java:780) > Standard Output > Key found in store, shouldn't have persisted this or should have cleaned up all readlocks on directory close:_3.fdt|RL|testing index > Key found in store, shouldn't have persisted this or should have cleaned up all readlocks on directory close:_3.tis|RL|testing index > Key found in store, shouldn't have persisted this or should have cleaned up all readlocks on directory close:segments_4|RL|testing index > Key found in store, shouldn't have persisted this or should have cleaned up all readlocks on directory close:_3.nrm|RL|testing index > Key found in store, shouldn't have persisted this or should have cleaned up all readlocks on directory close:_3.prx|RL|testing index > Key found in store, shouldn't have persisted this or should have cleaned up all readlocks on directory close:_3.fdx|RL|testing index > [testng-DatabaseStoredIndexTest] Test indexWasStored(org.infinispan.lucene.DatabaseStoredIndexTest) failed. > Add link to jenkins job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3376) CLI upgrade command does not work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3376?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3376: ----------------------------------------------- Vitalii Chepeliuk <vchepeli(a)redhat.com> made a comment on [bug 989970|https://bugzilla.redhat.com/show_bug.cgi?id=989970] Description of problem: See Description of ISPN-3376 > CLI upgrade command does not work > --------------------------------- > > Key: ISPN-3376 > URL: https://issues.jboss.org/browse/ISPN-3376 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 6.0.0.Alpha1 > Reporter: Vitalii Chepeliuk > Assignee: Tristan Tarrant > Attachments: standalone-hotrod-rolling-upgrade.xml > > > Run my backup server with default standalone.xml configuration > ./standalone.sh -c standalone.xml -Djboss.socket.binding.port-offset=111 -Djboss.node.name=BACKUPER > Run my new server with > ./standalone.sh -c standalone-hotrod-rolling-upgrade.xml -Djboss,node.name=UPGRADER > 1) run command on BACKUPER > [remoting://localhost:10110/local/default]> upgrade --dumpkeys default > ISPN019502: Dumped keys for cache default > 2) run command on UPGRADER > [remoting://localhost:9999/local/default]> upgrade --synchronize=hotrod default > ISPN019026: An error occurred while synchronizing data for cache 'hotrod' using migrator 'default' from the source server -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3376) CLI upgrade command does not work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3376?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-3376: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=989970 > CLI upgrade command does not work > --------------------------------- > > Key: ISPN-3376 > URL: https://issues.jboss.org/browse/ISPN-3376 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 6.0.0.Alpha1 > Reporter: Vitalii Chepeliuk > Assignee: Tristan Tarrant > Attachments: standalone-hotrod-rolling-upgrade.xml > > > Run my backup server with default standalone.xml configuration > ./standalone.sh -c standalone.xml -Djboss.socket.binding.port-offset=111 -Djboss.node.name=BACKUPER > Run my new server with > ./standalone.sh -c standalone-hotrod-rolling-upgrade.xml -Djboss,node.name=UPGRADER > 1) run command on BACKUPER > [remoting://localhost:10110/local/default]> upgrade --dumpkeys default > ISPN019502: Dumped keys for cache default > 2) run command on UPGRADER > [remoting://localhost:9999/local/default]> upgrade --synchronize=hotrod default > ISPN019026: An error occurred while synchronizing data for cache 'hotrod' using migrator 'default' from the source server -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3376) CLI upgrade command does not work

by Vitalii Chepeliuk (JIRA)

Vitalii Chepeliuk created ISPN-3376: --------------------------------------- Summary: CLI upgrade command does not work Key: ISPN-3376 URL: https://issues.jboss.org/browse/ISPN-3376 Project: Infinispan Issue Type: Bug Components: CLI Affects Versions: 6.0.0.Alpha1 Reporter: Vitalii Chepeliuk Assignee: Tristan Tarrant Attachments: standalone-hotrod-rolling-upgrade.xml Run my backup server with default standalone.xml configuration ./standalone.sh -c standalone.xml -Djboss.socket.binding.port-offset=111 -Djboss.node.name=BACKUPER Run my new server with ./standalone.sh -c standalone-hotrod-rolling-upgrade.xml -Djboss,node.name=UPGRADER 1) run command on BACKUPER [remoting://localhost:10110/local/default]> upgrade --dumpkeys default ISPN019502: Dumped keys for cache default 2) run command on UPGRADER [remoting://localhost:9999/local/default]> upgrade --synchronize=hotrod default ISPN019026: An error occurred while synchronizing data for cache 'hotrod' using migrator 'default' from the source server -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3376) CLI upgrade command does not work

by Vitalii Chepeliuk (JIRA)

[ https://issues.jboss.org/browse/ISPN-3376?page=com.atlassian.jira.plugin.... ] Vitalii Chepeliuk updated ISPN-3376: ------------------------------------ Attachment: standalone-hotrod-rolling-upgrade.xml added configuration file for UPGRADER > CLI upgrade command does not work > --------------------------------- > > Key: ISPN-3376 > URL: https://issues.jboss.org/browse/ISPN-3376 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 6.0.0.Alpha1 > Reporter: Vitalii Chepeliuk > Assignee: Tristan Tarrant > Attachments: standalone-hotrod-rolling-upgrade.xml > > > Run my backup server with default standalone.xml configuration > ./standalone.sh -c standalone.xml -Djboss.socket.binding.port-offset=111 -Djboss.node.name=BACKUPER > Run my new server with > ./standalone.sh -c standalone-hotrod-rolling-upgrade.xml -Djboss,node.name=UPGRADER > 1) run command on BACKUPER > [remoting://localhost:10110/local/default]> upgrade --dumpkeys default > ISPN019502: Dumped keys for cache default > 2) run command on UPGRADER > [remoting://localhost:9999/local/default]> upgrade --synchronize=hotrod default > ISPN019026: An error occurred while synchronizing data for cache 'hotrod' using migrator 'default' from the source server -- 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, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2013