[JBoss JIRA] (ISPN-12352) Set license information when missing
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12352?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12352:
-----------------------------------
Sprint: DataGrid Sprint #49, DataGrid Sprint #50 (was: DataGrid Sprint #49)
> Set license information when missing
> ------------------------------------
>
> Key: ISPN-12352
> URL: https://issues.redhat.com/browse/ISPN-12352
> Project: Infinispan
> Issue Type: Enhancement
> Components: Build
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 11.0.4.Final, 12.0.0.Dev04
>
>
> There are some dependencies that don't report the licenses in the expected places (pom.xml for maven, package.json for nodejs). In those cases, the license is reported as "unknown" or empty.
> Create a new class in infinispan-tools where it receives an XML (manually created) with the licenses for "problematic" dependencies and merge it in the licenses.xml file. It shouldn't touch correct reported licenses.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (ISPN-12005) Store purge should ignore errors
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12005?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12005:
-----------------------------------
Sprint: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48, DataGrid Sprint #49, DataGrid Sprint #50 (was: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48, DataGrid Sprint #49)
> Store purge should ignore errors
> --------------------------------
>
> Key: ISPN-12005
> URL: https://issues.redhat.com/browse/ISPN-12005
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Loaders and Stores
> Affects Versions: 10.1.5.Final, 11.0.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 12.0.0.Final, 11.0.4.Final
>
>
> Purging of expired entries from stores is a pretty involved process, especially with {{RocksDBStore}}. When there's a problem unmarshalling the expired bucket or deleting an expired key, the purge task bails out immediately, without processing the remaining keys. To make matters worse, the exception it not logged anywhere. The only sign that something is wrong is a growing store (in the case of {{RocksDBStore}}, a growing number of SST files).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (ISPN-12102) Validate configuration before storing it
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12102?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12102:
-----------------------------------
Sprint: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48, DataGrid Sprint #49, DataGrid Sprint #50 (was: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48, DataGrid Sprint #49)
> Validate configuration before storing it
> ----------------------------------------
>
> Key: ISPN-12102
> URL: https://issues.redhat.com/browse/ISPN-12102
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 11.0.1.Final
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 12.0.0.Dev05
>
>
> Although {{ConfigurationBuilder}} does some validation, sometimes it needs something more. As an example, the cross-site replication needs a running {{Transport}} to check if xsite is really supported.
> As a side effect, the console is broken when you try to define the following cache without {{RELAY2}} being present in the JGroups stack.
> {code:xml}
> <infinispan>
> <cache-container>
> <distributed-cache name="xsite">
> <backups>
> <backup site="site2"/>
> </backups>
> </distributed-cache>
> </cache-container>
> </infinispan>
> {code}
> This happens because the {{Configuration}} is stored and the {{Cache}} with the exception is stored as well.
> The fix proposed it adds a method to {{ModuleLifecyle}} where the {{Configuration}} can be validated before it is store in the "global state".
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (ISPN-11978) Java ScriptEngine
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11978?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11978:
-----------------------------------
Sprint: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48, DataGrid Sprint #49, DataGrid Sprint #50 (was: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48, DataGrid Sprint #49)
> Java ScriptEngine
> -----------------
>
> Key: ISPN-11978
> URL: https://issues.redhat.com/browse/ISPN-11978
> Project: Infinispan
> Issue Type: Enhancement
> Components: Tasks
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> Since Java 11 the Nashorn script engine has been deprecated and marked for removal.
> We can use either the Java compiler API or JShell to implement a ScriptEngine for Java.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (ISPN-12095) CLI: Add support for cluster backup/restore
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12095?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12095:
-----------------------------------
Sprint: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48, DataGrid Sprint #49, DataGrid Sprint #50 (was: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48, DataGrid Sprint #49)
> CLI: Add support for cluster backup/restore
> -------------------------------------------
>
> Key: ISPN-12095
> URL: https://issues.redhat.com/browse/ISPN-12095
> Project: Infinispan
> Issue Type: Enhancement
> Components: CLI
> Affects Versions: 11.0.1.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> It should be possible to backup/restore a cluster via the CLI:
> {code:java}
> bin/cli.sh -c localhost:11222 --restore <archive-file>
> bin/cli.sh -c localhost:11222 --backup <archive-file>
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (ISPN-12250) Add exponential back-off for cross-site network failures
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12250?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12250:
-----------------------------------
Sprint: DataGrid Sprint #48, DataGrid Sprint #49, DataGrid Sprint #50 (was: DataGrid Sprint #48, DataGrid Sprint #49)
> Add exponential back-off for cross-site network failures
> --------------------------------------------------------
>
> Key: ISPN-12250
> URL: https://issues.redhat.com/browse/ISPN-12250
> Project: Infinispan
> Issue Type: Bug
> Components: Cross-Site Replication
> Affects Versions: 12.0.0.Dev02
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 11.0.4.Final, 12.0.0.Dev04
>
>
> If the remote site doesn't exist (crash or shutdown), the IRAC algorithm keeps trying to send the updates to the remote site (until automatic take offline is triggered, when configured).
> Add an exponential backoff to avoid CPU consumption.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months