July 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4343) Rest rolling upgrades, distributed -- new cluster can't load from old cluster properly

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4343?page=com.atlassian.jira.plugin.... ] Pedro Ruivo commented on ISPN-4343: ----------------------------------- IMO, I think the codec needs to change. I didn't try it yet, but my idea is to change the codec to put the data as key and put the data type in the MimeMetadata. then we can get rid of MimeCacheEntry. > Rest rolling upgrades, distributed -- new cluster can't load from old cluster properly > -------------------------------------------------------------------------------------- > > Key: ISPN-4343 > URL: https://issues.jboss.org/browse/ISPN-4343 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Loaders and Stores, Server > Affects Versions: 7.0.0.Alpha4 > Reporter: Tomas Sykora > Assignee: Tomas Sykora > Priority: Critical > Labels: rolling_upgrade > Attachments: cannot_be_cast.txt, clustered-rest-rolling-upgrade.xml, clustered.xml, ISPN-4343.txt, ISPN-4343.zip, restRollUpsTraceLog.zip > > > A try to mimic the process of REST Rolling Upgrades for one old and new server in a clustered environment failed. > Scenario is quite simple, we start 2 old servers, store some data in, start 2 new servers and point clients to that new cluster. > When issuing a get on a new cluster (want to fetch old entry from old store), the operation fails with attached stack trace. > I also include current ISPN testsuite where is added testRestRollingUpgradesDiffVersionsDist test as a reproducer. > Respective changes are mirrored in my remote branch: https://github.com/tsykora/infinispan/tree/ISPN-4330 > You can run test like: > mvn clean verify -P suite.rolling.upgrades -Dzip.dist.old=/home/you/servers/previous-ispn-server-version.zip -Dtest=RestRollingUpgradesTest#testRestRollingUpgradesDiffVersionsDist -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4343) Rest rolling upgrades, distributed -- new cluster can't load from old cluster properly

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-4343?page=com.atlassian.jira.plugin.... ] Tomas Sykora commented on ISPN-4343: ------------------------------------ I will fix it and issue a PR, assigning to myself. Thank you for your help and input Pedro! > Rest rolling upgrades, distributed -- new cluster can't load from old cluster properly > -------------------------------------------------------------------------------------- > > Key: ISPN-4343 > URL: https://issues.jboss.org/browse/ISPN-4343 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Loaders and Stores, Server > Affects Versions: 7.0.0.Alpha4 > Reporter: Tomas Sykora > Assignee: Tomas Sykora > Priority: Critical > Labels: rolling_upgrade > Attachments: cannot_be_cast.txt, clustered-rest-rolling-upgrade.xml, clustered.xml, ISPN-4343.txt, ISPN-4343.zip, restRollUpsTraceLog.zip > > > A try to mimic the process of REST Rolling Upgrades for one old and new server in a clustered environment failed. > Scenario is quite simple, we start 2 old servers, store some data in, start 2 new servers and point clients to that new cluster. > When issuing a get on a new cluster (want to fetch old entry from old store), the operation fails with attached stack trace. > I also include current ISPN testsuite where is added testRestRollingUpgradesDiffVersionsDist test as a reproducer. > Respective changes are mirrored in my remote branch: https://github.com/tsykora/infinispan/tree/ISPN-4330 > You can run test like: > mvn clean verify -P suite.rolling.upgrades -Dzip.dist.old=/home/you/servers/previous-ispn-server-version.zip -Dtest=RestRollingUpgradesTest#testRestRollingUpgradesDiffVersionsDist -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4343) Rest rolling upgrades, distributed -- new cluster can't load from old cluster properly

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-4343?page=com.atlassian.jira.plugin.... ] Tomas Sykora reassigned ISPN-4343: ---------------------------------- Assignee: Tomas Sykora (was: Dan Berindei) > Rest rolling upgrades, distributed -- new cluster can't load from old cluster properly > -------------------------------------------------------------------------------------- > > Key: ISPN-4343 > URL: https://issues.jboss.org/browse/ISPN-4343 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Loaders and Stores, Server > Affects Versions: 7.0.0.Alpha4 > Reporter: Tomas Sykora > Assignee: Tomas Sykora > Priority: Critical > Labels: rolling_upgrade > Attachments: cannot_be_cast.txt, clustered-rest-rolling-upgrade.xml, clustered.xml, ISPN-4343.txt, ISPN-4343.zip, restRollUpsTraceLog.zip > > > A try to mimic the process of REST Rolling Upgrades for one old and new server in a clustered environment failed. > Scenario is quite simple, we start 2 old servers, store some data in, start 2 new servers and point clients to that new cluster. > When issuing a get on a new cluster (want to fetch old entry from old store), the operation fails with attached stack trace. > I also include current ISPN testsuite where is added testRestRollingUpgradesDiffVersionsDist test as a reproducer. > Respective changes are mirrored in my remote branch: https://github.com/tsykora/infinispan/tree/ISPN-4330 > You can run test like: > mvn clean verify -P suite.rolling.upgrades -Dzip.dist.old=/home/you/servers/previous-ispn-server-version.zip -Dtest=RestRollingUpgradesTest#testRestRollingUpgradesDiffVersionsDist -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4343) Rest rolling upgrades, distributed -- new cluster can't load from old cluster properly

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4343?page=com.atlassian.jira.plugin.... ] Pedro Ruivo commented on ISPN-4343: ----------------------------------- ah, I forgot something... I had to disconnect the Rest store from both nodes in the new cluster in your test. > Rest rolling upgrades, distributed -- new cluster can't load from old cluster properly > -------------------------------------------------------------------------------------- > > Key: ISPN-4343 > URL: https://issues.jboss.org/browse/ISPN-4343 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Loaders and Stores, Server > Affects Versions: 7.0.0.Alpha4 > Reporter: Tomas Sykora > Assignee: Dan Berindei > Priority: Critical > Labels: rolling_upgrade > Attachments: cannot_be_cast.txt, clustered-rest-rolling-upgrade.xml, clustered.xml, ISPN-4343.txt, ISPN-4343.zip, restRollUpsTraceLog.zip > > > A try to mimic the process of REST Rolling Upgrades for one old and new server in a clustered environment failed. > Scenario is quite simple, we start 2 old servers, store some data in, start 2 new servers and point clients to that new cluster. > When issuing a get on a new cluster (want to fetch old entry from old store), the operation fails with attached stack trace. > I also include current ISPN testsuite where is added testRestRollingUpgradesDiffVersionsDist test as a reproducer. > Respective changes are mirrored in my remote branch: https://github.com/tsykora/infinispan/tree/ISPN-4330 > You can run test like: > mvn clean verify -P suite.rolling.upgrades -Dzip.dist.old=/home/you/servers/previous-ispn-server-version.zip -Dtest=RestRollingUpgradesTest#testRestRollingUpgradesDiffVersionsDist -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4343) Rest rolling upgrades, distributed -- new cluster can't load from old cluster properly

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-4343?page=com.atlassian.jira.plugin.... ] Tomas Sykora commented on ISPN-4343: ------------------------------------ Ah! I overlooked that... thank you [~pruivo] very much! Cool, a bug in CLI is definitely less critical than a bug in rest rolling upgrades itself. > Rest rolling upgrades, distributed -- new cluster can't load from old cluster properly > -------------------------------------------------------------------------------------- > > Key: ISPN-4343 > URL: https://issues.jboss.org/browse/ISPN-4343 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Loaders and Stores, Server > Affects Versions: 7.0.0.Alpha4 > Reporter: Tomas Sykora > Assignee: Dan Berindei > Priority: Critical > Labels: rolling_upgrade > Attachments: cannot_be_cast.txt, clustered-rest-rolling-upgrade.xml, clustered.xml, ISPN-4343.txt, ISPN-4343.zip, restRollUpsTraceLog.zip > > > A try to mimic the process of REST Rolling Upgrades for one old and new server in a clustered environment failed. > Scenario is quite simple, we start 2 old servers, store some data in, start 2 new servers and point clients to that new cluster. > When issuing a get on a new cluster (want to fetch old entry from old store), the operation fails with attached stack trace. > I also include current ISPN testsuite where is added testRestRollingUpgradesDiffVersionsDist test as a reproducer. > Respective changes are mirrored in my remote branch: https://github.com/tsykora/infinispan/tree/ISPN-4330 > You can run test like: > mvn clean verify -P suite.rolling.upgrades -Dzip.dist.old=/home/you/servers/previous-ispn-server-version.zip -Dtest=RestRollingUpgradesTest#testRestRollingUpgradesDiffVersionsDist -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4482) Upgrade JGroups to 3.5.0.Beta9

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4482?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4482: ------------------------------- Affects Version/s: 7.0.0.Alpha4 > Upgrade JGroups to 3.5.0.Beta9 > ------------------------------ > > Key: ISPN-4482 > URL: https://issues.jboss.org/browse/ISPN-4482 > Project: Infinispan > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 7.0.0.Alpha4 > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Fix For: 7.0.0.Alpha5 > > > It contains various SASL fixes, like [JGRP-1848|https://issues.jboss.org/browse/JGRP-1848], [JGRP-1849|https://issues.jboss.org/browse/JGRP-1849], [JGRP-1852|https://issues.jboss.org/browse/JGRP-1852], [JGRP-1853|https://issues.jboss.org/browse/JGRP-1853] and other fixes. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4488) Verify performance impact of Lucene 4 and checksumming logic in the Lucene Directory

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-4488: ------------------------------------- Summary: Verify performance impact of Lucene 4 and checksumming logic in the Lucene Directory Key: ISPN-4488 URL: https://issues.jboss.org/browse/ISPN-4488 Project: Infinispan Issue Type: Task Security Level: Public (Everyone can see) Components: Lucene Directory Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 7.0.0.Beta1 We recently moved to Lucene 4, and also the Lucene Directory is now wrapping output to allow to calculate checksums. Before going Final we need to verify the performance impact, QA mentioned a significant regression compared to Lucene v3 w/o checksums. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4482) Upgrade JGroups to 3.5.0.Beta9

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4482?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4482: ------------------------------- Issue Type: Component Upgrade (was: Feature Request) > Upgrade JGroups to 3.5.0.Beta9 > ------------------------------ > > Key: ISPN-4482 > URL: https://issues.jboss.org/browse/ISPN-4482 > Project: Infinispan > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Core > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > > It contains various SASL fixes, like [JGRP-1848|https://issues.jboss.org/browse/JGRP-1848], [JGRP-1849|https://issues.jboss.org/browse/JGRP-1849], [JGRP-1852|https://issues.jboss.org/browse/JGRP-1852], [JGRP-1853|https://issues.jboss.org/browse/JGRP-1853] and other fixes. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4482) Upgrade JGroups to 3.5.0.Beta9

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4482?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4482: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.Alpha5 Resolution: Done > Upgrade JGroups to 3.5.0.Beta9 > ------------------------------ > > Key: ISPN-4482 > URL: https://issues.jboss.org/browse/ISPN-4482 > Project: Infinispan > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Core > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Fix For: 7.0.0.Alpha5 > > > It contains various SASL fixes, like [JGRP-1848|https://issues.jboss.org/browse/JGRP-1848], [JGRP-1849|https://issues.jboss.org/browse/JGRP-1849], [JGRP-1852|https://issues.jboss.org/browse/JGRP-1852], [JGRP-1853|https://issues.jboss.org/browse/JGRP-1853] and other fixes. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4482) Upgrade JGroups to 3.5.0.Beta9

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4482?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4482: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2694 > Upgrade JGroups to 3.5.0.Beta9 > ------------------------------ > > Key: ISPN-4482 > URL: https://issues.jboss.org/browse/ISPN-4482 > Project: Infinispan > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Fix For: 7.0.0.Alpha5 > > > It contains various SASL fixes, like [JGRP-1848|https://issues.jboss.org/browse/JGRP-1848], [JGRP-1849|https://issues.jboss.org/browse/JGRP-1849], [JGRP-1852|https://issues.jboss.org/browse/JGRP-1852], [JGRP-1853|https://issues.jboss.org/browse/JGRP-1853] and other fixes. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2014