[JBoss JIRA] (ISPN-3723) REST RollUps from 5.2.4 to 6.0.0 -- migrates 0 entries (probably due to PersistenceException)
by Tomas Sykora (JIRA)
[ https://issues.jboss.org/browse/ISPN-3723?page=com.atlassian.jira.plugin.... ]
Tomas Sykora updated ISPN-3723:
-------------------------------
Description:
Trying to process REST rolling upgrades using latest infinispan server 6.0.0 snapshot as a TARGET node and old 5.2.4 server as a source node.
20 entries stored on source node successfully,
recordKnownGlobalKeySet does not nothing (this is ok) REST is able to provide full key set
but then,
operation "synchronizeData" using "rest" issued on new node is returning:
14:05:23,252 INFO [org.infinispan.upgrade.RollingUpgradeManager] (pool-1-thread-1) ISPN000216: 0 entries migrated to cache default in 30 milliseconds
however, there is 20 entries stored in the old node.
Please see attached file for more detailed stack trace.
was:
Trying to process REST rolling upgrades using latest infinispan server 6.0.0 snapshot as a TARGET node and old 5.2.4 server (jdg 6.1.GA) as a source node.
20 entries stored on source node successfully,
recordKnownGlobalKeySet does not nothing (this is ok) REST is able to provide full key set
but then,
operation "synchronizeData" using "rest" issued on new node is returning:
14:05:23,252 INFO [org.infinispan.upgrade.RollingUpgradeManager] (pool-1-thread-1) ISPN000216: 0 entries migrated to cache default in 30 milliseconds
however, there is 20 entries stored in the old node.
Please see attached file for more detailed stack trace.
> REST RollUps from 5.2.4 to 6.0.0 -- migrates 0 entries (probably due to PersistenceException)
> ---------------------------------------------------------------------------------------------
>
> Key: ISPN-3723
> URL: https://issues.jboss.org/browse/ISPN-3723
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 6.0.0.CR1
> Reporter: Tomas Sykora
> Assignee: Mircea Markus
> Attachments: restRollUpsPersistenceExceptionCantMigrate
>
>
> Trying to process REST rolling upgrades using latest infinispan server 6.0.0 snapshot as a TARGET node and old 5.2.4 server as a source node.
> 20 entries stored on source node successfully,
> recordKnownGlobalKeySet does not nothing (this is ok) REST is able to provide full key set
> but then,
> operation "synchronizeData" using "rest" issued on new node is returning:
> 14:05:23,252 INFO [org.infinispan.upgrade.RollingUpgradeManager] (pool-1-thread-1) ISPN000216: 0 entries migrated to cache default in 30 milliseconds
> however, there is 20 entries stored in the old node.
> Please see attached file for more detailed stack trace.
--
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, 1 month
[JBoss JIRA] (ISPN-3724) REST RollUps 5.2.4 to 6.0.0 -- target can't fetch entries (Unsupported protocol version 60)
by Tomas Sykora (JIRA)
[ https://issues.jboss.org/browse/ISPN-3724?page=com.atlassian.jira.plugin.... ]
Tomas Sykora updated ISPN-3724:
-------------------------------
Description:
Trying to process REST rolling upgrades using latest infinispan server 6.0.0 snapshot as a TARGET node and old 5.2.4 server as a source node.
Put entry to the SOURCE node.
Start TARGET node, specifying source node as a REST RCS.
Calling get on the TARGET node will cause PersistenceException caused by Caused by: java.io.IOException: Unsupported protocol version 60
Please, see full stack trace in attached file.
was:
Trying to process REST rolling upgrades using latest infinispan server 6.0.0 snapshot as a TARGET node and old 5.2.4 server (jdg 6.1.GA) as a source node.
Put entry to the SOURCE node.
Start TARGET node, specifying source node as a REST RCS.
Calling get on the TARGET node will cause PersistenceException caused by Caused by: java.io.IOException: Unsupported protocol version 60
Please, see full stack trace in attached file.
> REST RollUps 5.2.4 to 6.0.0 -- target can't fetch entries (Unsupported protocol version 60)
> -------------------------------------------------------------------------------------------
>
> Key: ISPN-3724
> URL: https://issues.jboss.org/browse/ISPN-3724
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 6.0.0.CR1
> Reporter: Tomas Sykora
> Assignee: Mircea Markus
> Attachments: RestRollUpsUnsupportedProtocol60
>
>
> Trying to process REST rolling upgrades using latest infinispan server 6.0.0 snapshot as a TARGET node and old 5.2.4 server as a source node.
> Put entry to the SOURCE node.
> Start TARGET node, specifying source node as a REST RCS.
> Calling get on the TARGET node will cause PersistenceException caused by Caused by: java.io.IOException: Unsupported protocol version 60
> Please, see full stack trace in attached file.
--
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, 1 month
[JBoss JIRA] (ISPN-3727) intermittent test failure AsyncReplExtendedStatisticTest.testReplaceWithOldVal
by Mircea Markus (JIRA)
Mircea Markus created ISPN-3727:
-----------------------------------
Summary: intermittent test failure AsyncReplExtendedStatisticTest.testReplaceWithOldVal
Key: ISPN-3727
URL: https://issues.jboss.org/browse/ISPN-3727
Project: Infinispan
Issue Type: Task
Reporter: Mircea Markus
Assignee: Pedro Ruivo
Failed tests:
AsyncReplExtendedStatisticTest>BaseClusteredExtendedStatisticTest.testReplaceWithOldVal:190->BaseClusteredExtendedStatisticTest.assertCacheValue:253->MultipleCacheManagersTest.assertEventuallyEquals:554->AbstractInfinispanTest.eventually:173->AbstractInfinispanTest.eventually:45->AbstractInfinispanTest.eventually:62
expected [true] but found [false]
--
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, 1 month
[JBoss JIRA] (ISPN-3722) State transfer must be enabled for Lucene Directory if clustered caches are used
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-3722?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-3722:
------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/2200
> State transfer must be enabled for Lucene Directory if clustered caches are used
> --------------------------------------------------------------------------------
>
> Key: ISPN-3722
> URL: https://issues.jboss.org/browse/ISPN-3722
> Project: Infinispan
> Issue Type: Bug
> Components: Lucene Directory
> Affects Versions: 6.0.0.CR1
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Fix For: 6.1.0.Final
>
>
> take a look at the following code:
> {code:java}
> public Set<String> getFileList() {
> Set<String> fileList = (Set<String>) cache.get(fileListCacheKey);
> if (fileList == null) {
> fileList = new ConcurrentHashSet<String>();
> Set<String> prev = (Set<String>) cache.putIfAbsent(fileListCacheKey, fileList);
> if ( prev != null ) {
> fileList = prev;
> }
> }
> return fileList;
> }
> {code}
> when it requests the file list, the joiner does not have the data locally and it tries to do a putIfAbsent with an empty set. However, when it reaches the primary owner (if not changed), it will return the current file list.
> After, it tries to read the files returned in the set and it cannot find it, throwing an IOException -- "Read past EOF"
> A validation should be made in order to not allow clustered caches without state transfer.
--
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, 1 month
[JBoss JIRA] (ISPN-3722) State transfer must be enabled for Lucene Directory if clustered caches are used
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-3722?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-3722:
--------------------------------
Fix Version/s: 6.1.0.Final
(was: 6.0.0.Final)
> State transfer must be enabled for Lucene Directory if clustered caches are used
> --------------------------------------------------------------------------------
>
> Key: ISPN-3722
> URL: https://issues.jboss.org/browse/ISPN-3722
> Project: Infinispan
> Issue Type: Bug
> Components: Lucene Directory
> Affects Versions: 6.0.0.CR1
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Fix For: 6.1.0.Final
>
>
> take a look at the following code:
> {code:java}
> public Set<String> getFileList() {
> Set<String> fileList = (Set<String>) cache.get(fileListCacheKey);
> if (fileList == null) {
> fileList = new ConcurrentHashSet<String>();
> Set<String> prev = (Set<String>) cache.putIfAbsent(fileListCacheKey, fileList);
> if ( prev != null ) {
> fileList = prev;
> }
> }
> return fileList;
> }
> {code}
> when it requests the file list, the joiner does not have the data locally and it tries to do a putIfAbsent with an empty set. However, when it reaches the primary owner (if not changed), it will return the current file list.
> After, it tries to read the files returned in the set and it cannot find it, throwing an IOException -- "Read past EOF"
> A validation should be made in order to not allow clustered caches without state transfer.
--
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, 1 month