[JBoss JIRA] (ISPN-12173) Explanation for eviction leads confusion
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12173?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12173:
-----------------------------------
Sprint: DataGrid Sprint #47, DataGrid Sprint #48 (was: DataGrid Sprint #47)
> Explanation for eviction leads confusion
> ----------------------------------------
>
> Key: ISPN-12173
> URL: https://issues.redhat.com/browse/ISPN-12173
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation
> Affects Versions: 12.0.0.Dev01
> Reporter: Wolf-Dieter Fink
> Assignee: Donald Naro
> Priority: Major
> Labels: eviction
>
> chapter 8.2. Eviction ([https://infinispan.org/docs/dev/titles/configuring/configuring.html#evict...]
> Starts with a sentence that leads confusion
> "Eviction lets you control the size of the data container by removing cache entries to make space when adding new entries."
>
> The wording "removing cache entries to make space" sound like the entry will be removed like a remove('key') invocation or expiration.
> But this is not the case. It should be clear that the entry is evicted from memory on exactly this instance, no other instance is affected.
> To prevent from not deterministic behaviour if different instances within the cluster are used for request eviction should not be configured without persistence (as mentioned) but the initial statement should be more precise
>
> Proposal
> Eviction lets you contol the size of data container in this local instance by dropping (evict) one choosen entry from memory only without further effects.
> This is a local action for this node and does not affect any other node within the cluster
> To prevent from inconsistency eviction should not be used without a configured persistence
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (ISPN-12204) Add JDBC Meta Table
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12204?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12204:
-----------------------------------
Sprint: DataGrid Sprint #47, DataGrid Sprint #48 (was: DataGrid Sprint #47)
> Add JDBC Meta Table
> -------------------
>
> Key: ISPN-12204
> URL: https://issues.redhat.com/browse/ISPN-12204
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores
> Affects Versions: 12.0.0.Dev01
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 12.0.0.Dev02
>
>
> Currently there is no way to determine what version of Infinispan created a Jdbc store, which makes it difficult/impossible to migrate stored data from one Infinispan version to another if a binary incompatibility is introduced.
> Similarly it's not possible for us to verify that the configured number of segments match those present in an existing store.
> We should add an additional table to store such metadata.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (ISPN-12177) Persist IRAC version during shutdown
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12177?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12177:
-----------------------------------
Sprint: DataGrid Sprint #47, DataGrid Sprint #48 (was: DataGrid Sprint #47)
> Persist IRAC version during shutdown
> ------------------------------------
>
> Key: ISPN-12177
> URL: https://issues.redhat.com/browse/ISPN-12177
> Project: Infinispan
> Issue Type: Bug
> Components: Cross-Site Replication
> Affects Versions: 11.0.1.Final
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> The IRAC version is reset after a complete shutdown. It should be persisted in the global state to avoid unnecessary conflicts and/or data inconsistency.
> If the global state is disabled, the users have to deal with it.
> Also, make it possible to "compute" the version if the data is persisted and when receiving state from the remote site.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (ISPN-12036) Automatic SerializationContextInitializer registration
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12036?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12036:
-----------------------------------
Sprint: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48 (was: DataGrid Sprint #46, DataGrid Sprint #47)
> Automatic SerializationContextInitializer registration
> ------------------------------------------------------
>
> Key: ISPN-12036
> URL: https://issues.redhat.com/browse/ISPN-12036
> Project: Infinispan
> Issue Type: Enhancement
> Components: Configuration
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 12.0.0.Dev01
>
>
> For usability and convenience, we should toggle the service attribute of the AutoProtoSchemaBuilder annotation to true so that service files are always generated.
> ProtobufMetadataManagerImpl should then automatically scan for services and register them.
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (ISPN-12038) RocksDB compression options incomplete and incorrectly applied
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12038?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12038:
-----------------------------------
Sprint: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48 (was: DataGrid Sprint #46, DataGrid Sprint #47)
> RocksDB compression options incomplete and incorrectly applied
> --------------------------------------------------------------
>
> Key: ISPN-12038
> URL: https://issues.redhat.com/browse/ISPN-12038
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 11.0.0.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 11.0.1.Final
>
>
> The RocksDB store compression configuration has several issues:
> * it uses string names which are not in sync with the library
> * some new compression options are missing (XPRESS and ZSTD)
> * the free-form properties for setting compression are always overwritten with the default store setting (NONE)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 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 (was: DataGrid Sprint #46, DataGrid Sprint #47)
> 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)
5 years, 7 months
[JBoss JIRA] (ISPN-12047) Merge Async and Sync Cross-Site attributes
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12047?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12047:
-----------------------------------
Sprint: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48 (was: DataGrid Sprint #46, DataGrid Sprint #47)
> Merge Async and Sync Cross-Site attributes
> ------------------------------------------
>
> Key: ISPN-12047
> URL: https://issues.redhat.com/browse/ISPN-12047
> Project: Infinispan
> Issue Type: Enhancement
> Affects Versions: 11.0.0.Final
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 11.0.1.Final
>
>
> With IRAC, we only perform synchronous cross-site requests however, we are still exposing async attributes like {{AsyncXSiteRequestsReceived}}, {{AverageAsyncXSiteReplicationTime}}, {{MaximumAsyncXSiteReplicationTime}}, etc.
> Those are never updated anymore. They can be removed and use the sync* attributes.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months