[JBoss JIRA] (ISPN-8453) Commit should fail if cache is in degraded mode
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-8453?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8453:
----------------------------------
Fix Version/s: 9.4.8.Final
(was: 9.4.7.Final)
> Commit should fail if cache is in degraded mode
> -----------------------------------------------
>
> Key: ISPN-8453
> URL: https://issues.jboss.org/browse/ISPN-8453
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 8.1.9.Final, 8.2.8.Final, 9.1.2.Final, 9.2.0.Alpha2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 9.4.8.Final
>
>
> When the originator receives a {{CacheNotFoundResponse}} and the cache is in degraded mode, the transaction is marked as partially completed, but the commit completes successfully.
> I believe that is not correct, because the originator could crash after the commit but before the merge, and in that case the transaction will not be applied on all the owners. The transaction manager will ignore any commit exception in {{NON_XA}}/{{useSynchronization}} mode, but at least in {{FULL_XA}}/{{NON_DURABLE_XA}} mode we can signal to the user that the transaction may be lost.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 11 months
[JBoss JIRA] (ISPN-8356) Embedded distribution names are confusing
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-8356?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8356:
----------------------------------
Fix Version/s: 9.4.8.Final
(was: 9.4.7.Final)
> Embedded distribution names are confusing
> -----------------------------------------
>
> Key: ISPN-8356
> URL: https://issues.jboss.org/browse/ISPN-8356
> Project: Infinispan
> Issue Type: Enhancement
> Components: Build
> Affects Versions: 9.1.1.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 9.4.8.Final
>
>
> The binary distribution names for embedded libraries are confusing:
> I propose the following names
>
> - infinispan-${version}-all.zip -> infinispan-embedded-${version}-all.zip
> - infinispan-${version}-minimal.zip -> infinispan-embedded-${version}-minimal.zip
> - infinispan-${version}-remote.zip -> infinispan-remote-${version}.zip
> The website labelling needs to be modified accordingly too
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 11 months
[JBoss JIRA] (ISPN-8241) Refactor RocksDB clearThreshold
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-8241?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8241:
----------------------------------
Fix Version/s: 9.4.8.Final
(was: 9.4.7.Final)
> Refactor RocksDB clearThreshold
> -------------------------------
>
> Key: ISPN-8241
> URL: https://issues.jboss.org/browse/ISPN-8241
> Project: Infinispan
> Issue Type: Sub-task
> Components: Loaders and Stores
> Affects Versions: 9.1.0.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 9.4.8.Final
>
>
> Currently the RocksDB store utilises a "clearThreshold" to try to delete entries individually before deleting and re-initiating the database. We should deprecate this threshold and always delete/reinit the database.
> Currently when deleting the database, we utilise Util.recursiveFileRemove which does not confirm that the file has actually been deleted. Instead, we should provide a nio based implementation instead, similar to the one stated [here|https://stackoverflow.com/questions/779519/delete-directories-recurs...]. This has the advantage that an IOException is thrown by java.nio.file.Files::delete
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 11 months