September 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3018) Implement a REST cache store which supports Rolling Upgrades

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3018?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3018: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 6.0.0.Beta1 Resolution: Done > Implement a REST cache store which supports Rolling Upgrades > ------------------------------------------------------------ > > Key: ISPN-3018 > URL: https://issues.jboss.org/browse/ISPN-3018 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Blocker > Fix For: 6.0.0.Beta1, 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3458) HotRod rolling upgrade target migrator should live in the Remote Store

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3458?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3458: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > HotRod rolling upgrade target migrator should live in the Remote Store > ---------------------------------------------------------------------- > > Key: ISPN-3458 > URL: https://issues.jboss.org/browse/ISPN-3458 > Project: Infinispan > Issue Type: Task > Components: Loaders and Stores, Migration tools, Remote protocols > Affects Versions: 6.0.0.Alpha3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Beta1, 6.0.0.Final > > > Drop the upgrade-tools component and move the HotRod target migrator into the RemoteCacheStore -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3456) REST server should return 404 when attempting to remove a non-existent entry

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3456?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3456: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > REST server should return 404 when attempting to remove a non-existent entry > ---------------------------------------------------------------------------- > > Key: ISPN-3456 > URL: https://issues.jboss.org/browse/ISPN-3456 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 6.0.0.Alpha3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Beta1 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3318) Migrate data from one cache store to another

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3318?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3318: ---------------------------------- Status: Pull Request Sent (was: Coding In Progress) > Migrate data from one cache store to another > -------------------------------------------- > > Key: ISPN-3318 > URL: https://issues.jboss.org/browse/ISPN-3318 > Project: Infinispan > Issue Type: Task > Components: Loaders and Stores > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 6.0.0.Final > > > Find a generic way to transfer data from one cache store to another, which could involve different Infinispan versions. This is handy to migrate file cache store based users to single file cache store (ISPN-2806). > Ideally, this should be added as a recipe for rolling upgrades. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3318) Migrate data from one cache store to another

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3318?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3318: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 6.0.0.Beta1 Resolution: Done > Migrate data from one cache store to another > -------------------------------------------- > > Key: ISPN-3318 > URL: https://issues.jboss.org/browse/ISPN-3318 > Project: Infinispan > Issue Type: Task > Components: Loaders and Stores > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 6.0.0.Beta1, 6.0.0.Final > > > Find a generic way to transfer data from one cache store to another, which could involve different Infinispan versions. This is handy to migrate file cache store based users to single file cache store (ISPN-2806). > Ideally, this should be added as a recipe for rolling upgrades. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3463) Ensure persistent data removal before or after the test

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3463?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3463: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Ensure persistent data removal before or after the test > ------------------------------------------------------- > > Key: ISPN-3463 > URL: https://issues.jboss.org/browse/ISPN-3463 > Project: Infinispan > Issue Type: Task > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 6.0.0.Beta1 > > > http://ci.infinispan.org/viewLog.html?buildId=3019&tab=buildResultsDiv&bu... > some cache store tests are failing because the old data is never removed -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3467) Remove support for strictPeerToPeer = true

by Dan Berindei (JIRA)

Dan Berindei created ISPN-3467: ---------------------------------- Summary: Remove support for strictPeerToPeer = true Key: ISPN-3467 URL: https://issues.jboss.org/browse/ISPN-3467 Project: Infinispan Issue Type: Task Components: Configuration, RPC, Server Affects Versions: 6.0.0.Alpha3 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 6.0.0.Beta2, 6.0.0.Final The {{transport.strictPeerToPeer}} setting doesn't really do anything with dist caches with L1 disabled, as commands are replicated only to members of the cache. With L1 enabled, writes/txs may or may not fail, depending on if there are any L1 requestors for the modified keys and on the value of {{clustering.l1.invalidationThreshold}} - unpredictable, so more harmful than useful. With repl caches, the setting does work as advertised: even if the cache topology contains only the nodes with the cache running, the writes/txs are sent to all the nodes in the cluster, and they will fail if the cache is not running on one of them. On the other hand, in order to retry the operation, the users would have to wait for the cache's topology to contain all the nodes in the cluster - so if they need to ensure that a cache is present on all the nodes in the cluster, they could check that {{RpcManager.getMembers().equals(Transport.getMembers()}} directly. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3459) Add support for Cache-Control http header to REST server

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-3459?page=com.atlassian.jira.plugin.... ] Martin Gencur commented on ISPN-3459: ------------------------------------- Implementation details: * Supported request headers: Cache-Control: min-fresh -> specifies that the entry must not expire in min-fresh seconds since the time of the response (if the entry is going to expire shortly, then REST does not return it, and returns NOT_FOUND) * Supported response headers: Cache-Control: max-age=xx -> this is similar to Expires, only the time is relative, in seconds (e.g max-age=10 means the entry will expire in 10 seconds since the time of the response) Cache-Control: no-transform -> this is added by default to each response that contains also max-age > Add support for Cache-Control http header to REST server > -------------------------------------------------------- > > Key: ISPN-3459 > URL: https://issues.jboss.org/browse/ISPN-3459 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Reporter: Martin Gencur > Assignee: Martin Gencur > Fix For: 6.0.0.Beta1, 6.0.0.Final > > > Apart from "Expires", the REST server should return also "Cache-Control" http header for entries that have lifespan defined. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3176) Add tests for compatibility mode to server

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3176?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3176: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add tests for compatibility mode to server > ------------------------------------------ > > Key: ISPN-3176 > URL: https://issues.jboss.org/browse/ISPN-3176 > Project: Infinispan > Issue Type: Task > Components: Server, Test Suite > Reporter: Martin Gencur > Assignee: Martin Gencur > Fix For: 6.0.0.Beta1 > > -- 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, 6 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3425?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3425: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 6.0.0.Beta1 (was: 6.0.0.CR1) Resolution: Done > 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.Beta1 > > > 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

11 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 September 2013