[JBoss JIRA] (ISPN-7912) Prevent RocksDBStore writes blocking on full expiry queue
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-7912?page=com.atlassian.jira.plugin... ]
Dan Berindei closed ISPN-7912.
------------------------------
Fix Version/s: 10.1.0.Final
Resolution: Done
ISPN-10963 removed the expiry queue
> Prevent RocksDBStore writes blocking on full expiry queue
> ---------------------------------------------------------
>
> Key: ISPN-7912
> URL: https://issues.redhat.com/browse/ISPN-7912
> Project: Infinispan
> Issue Type: Sub-task
> Components: Loaders and Stores
> Affects Versions: 9.1.0.Alpha1
> Reporter: Ryan Emerson
> Priority: Major
> Fix For: 10.1.0.Final
>
>
> Currently you can only insert 10000 elements into the rocks db store until you will block a thread until the expiration reaper is ran. Instead we should offer elements to the queue and upon failure utilise the persistence executors to run purge.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (ISPN-12005) Store purge should ignore errors
by Dan Berindei (Jira)
Dan Berindei created ISPN-12005:
-----------------------------------
Summary: 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: 11.0.0.Final, 10.1.5.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 12.0.0.Final, 11.0.1.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)
5 years, 9 months
[JBoss JIRA] (ISPN-12004) Add JGroups stack.combine INSERT_BEFORE
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-12004:
--------------------------------------
Summary: Add JGroups stack.combine INSERT_BEFORE
Key: ISPN-12004
URL: https://issues.redhat.com/browse/ISPN-12004
Project: Infinispan
Issue Type: Enhancement
Components: Configuration
Affects Versions: 11.0.0.Final
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 12.0.0.Final
The JGroups stack combiner supports INSERT_AFTER. It is also useful to add INSERT_BEFORE as well as INSERT_ABOVE and INSERT_BELOW aliases to better fit with the JGroups terminology.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (ISPN-11996) Allow customize memory and memory swap for Testcontainers images
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11996?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11996:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 11.0.1.Final
Assignee: Diego Lovison
Resolution: Done
> Allow customize memory and memory swap for Testcontainers images
> ----------------------------------------------------------------
>
> Key: ISPN-11996
> URL: https://issues.redhat.com/browse/ISPN-11996
> Project: Infinispan
> Issue Type: Enhancement
> Affects Versions: 11.0.0.CR1
> Reporter: Diego Lovison
> Assignee: Diego Lovison
> Priority: Major
> Fix For: 11.0.1.Final
>
>
> In order to avoid the OS kill the bash script, we need to allow a custom memory and memory swap for Testcontainers images.
>
> The combo CentOS8 and docker ( unsupported ) is failing because, after some time, CentOS is killing the bash script with the exit code 137.
> Allowing a custom memory and memory swap configuration fixes the issue.
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (ISPN-11998) Eviction new and legacy attributes should stay in sync
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11998?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11998:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Eviction new and legacy attributes should stay in sync
> ------------------------------------------------------
>
> Key: ISPN-11998
> URL: https://issues.redhat.com/browse/ISPN-11998
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration, Core
> Affects Versions: 11.0.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.1.Final
>
>
> The old-style eviction attributes (storage-type, eviction-strategy, eviction-type, size) are available programmatically both via {{memory()}} and via {{memory().heapConfiguration()}}, and changes to either the new attributes or to the legacy attributes should update all of them.
> The builder does not expose {{heapConfiguration()}}, but parsing a JSON with a legacy configuration (e.g. {{{"local-cache":\{ "memory":{"object":{"size":5000}}}}}}) will set those attributes directly.
> Additionally, the XSD does not include values OBJECT and BINARY for the storage attribute, but the parser accepts them, and serializing a configuration will sometimes write them in the XML. In theory we can replace OBJECT with HEAP, but we can't do the same trick with BINARY because we don't know the media type in the builder (it depends on the user marshaller). This may change in the future, but it's better if we preserve the actual values for now.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months