[JBoss JIRA] (ISPN-8443) Activator should delete entries from all stores on removing entries
by Vojtech Juranek (JIRA)
Vojtech Juranek created ISPN-8443:
-------------------------------------
Summary: Activator should delete entries from all stores on removing entries
Key: ISPN-8443
URL: https://issues.jboss.org/browse/ISPN-8443
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 9.2.0.Alpha1
Reporter: Vojtech Juranek
Assignee: Vojtech Juranek
Currently activator {{onRemove}} method deletes entries only from shared cache stores. It should remove entries no matter if the store is shared or not.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (ISPN-8442) Activator not called in off-heap data conatiner
by Vojtech Juranek (JIRA)
Vojtech Juranek created ISPN-8442:
-------------------------------------
Summary: Activator not called in off-heap data conatiner
Key: ISPN-8442
URL: https://issues.jboss.org/browse/ISPN-8442
Project: Infinispan
Issue Type: Bug
Components: Eviction, Off Heap
Affects Versions: 9.2.0.Alpha1, 9.1.0.Final
Reporter: Vojtech Juranek
Assignee: Vojtech Juranek
Off-heap container doesn't call activator. This resuls into various issue - e.g if passivation is enabled, cache entry is evicted and later on removed, it's still present in cache, as cache still sees it in cache store.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (ISPN-7865) Distributed Stream thread usage for key aware operations can be improved
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7865?page=com.atlassian.jira.plugin.... ]
Ryan Emerson resolved ISPN-7865.
--------------------------------
Fix Version/s: 9.2.0.Alpha2
(was: 9.2.0.Final)
Resolution: Done
> Distributed Stream thread usage for key aware operations can be improved
> ------------------------------------------------------------------------
>
> Key: ISPN-7865
> URL: https://issues.jboss.org/browse/ISPN-7865
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core, Distributed Execution and Map/Reduce
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 9.2.0.Alpha2
>
>
> Currently iterator will block a thread on the remote server when it is trying to send back a response. It would be better if we used full async API to instead request blocks of values as the iterator consumes them. We should make sure we always maintain a distributed batch size worth.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (ISPN-8338) Cache start methods should run privileged
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-8338?page=com.atlassian.jira.plugin.... ]
Ryan Emerson resolved ISPN-8338.
--------------------------------
Resolution: Done
> Cache start methods should run privileged
> -----------------------------------------
>
> Key: ISPN-8338
> URL: https://issues.jboss.org/browse/ISPN-8338
> Project: Infinispan
> Issue Type: Task
> Components: Security
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 9.2.0.Alpha2
>
>
> When a cache is starting and it has security, it is possible that an internal component would throw an exception stating it doesn't have security access. Normally this is fixed by surrounding this in a SecurityActions call. However when a cache is starting all of these components are known to be Infinispan core and should be fine trusting it. This JIRA is to wrap start automatically with SecurityActions.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (ISPN-8441) The module spec used by server config of indexed-entities/indexed-entity and modules/module accepts only deployments
by Adrian Nistor (JIRA)
Adrian Nistor created ISPN-8441:
-----------------------------------
Summary: The module spec used by server config of indexed-entities/indexed-entity and modules/module accepts only deployments
Key: ISPN-8441
URL: https://issues.jboss.org/browse/ISPN-8441
Project: Infinispan
Issue Type: Enhancement
Components: Server
Affects Versions: 9.1.0.Final
Reporter: Adrian Nistor
Assignee: Adrian Nistor
Fix For: 9.2.0.Final
The module name must start with "deployment." due to the use ServiceModuleLoader.moduleServiceName() method to resolve a service name from a module name. This only knows to handle deployments from 'deployment' dir, regular modules from the 'modules' dir are not handled.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (ISPN-8408) POM inheritance is broken
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-8408?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8408:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.2.0.Alpha2
Resolution: Done
> POM inheritance is broken
> -------------------------
>
> Key: ISPN-8408
> URL: https://issues.jboss.org/browse/ISPN-8408
> Project: Infinispan
> Issue Type: Bug
> Components: Build process
> Reporter: Tristan Tarrant
> Assignee: Ryan Emerson
> Fix For: 9.2.0.Alpha2, 9.2.0.Final
>
>
> There are a number of problems with our project structure:
> - the parent pom uses the bom as its own parent: it should instead import it (i.e. revert ISPN-3998)
> - the server pom inherits from the wildfly pom. This was done at a time when the server build was a fork of the wildfly one. With the introduction of feature packs this is no longer necessary.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (ISPN-8440) Enabled ConflictResolution on partition merge with PreferConsistencyStrategy
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-8440?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-8440:
-------------------------------
Description: Currently conflict resolution only occurs on a partition merge when the PreferAvailabilityStrategy is utilised (ALLOW_READ_WRITES). This should also occur when utilising the PreferConsistencyStrategy as it's possible for cache entries to become conflicted before a split-brain has been detected. (was: Currently conflict resolution only occurs on a partition merge when the PreferAvailabilityStrategy is utilised (ALLOW_READ_WRITES). This should also occur when utilising the PreferConsistencyStrategy. )
> Enabled ConflictResolution on partition merge with PreferConsistencyStrategy
> ----------------------------------------------------------------------------
>
> Key: ISPN-8440
> URL: https://issues.jboss.org/browse/ISPN-8440
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Affects Versions: 9.1.1.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Fix For: 9.2.0.Final
>
>
> Currently conflict resolution only occurs on a partition merge when the PreferAvailabilityStrategy is utilised (ALLOW_READ_WRITES). This should also occur when utilising the PreferConsistencyStrategy as it's possible for cache entries to become conflicted before a split-brain has been detected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (ISPN-8400) Adjust merge policies for JDG Online Services
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-8400?page=com.atlassian.jira.plugin.... ]
Ryan Emerson commented on ISPN-8400:
------------------------------------
After reviewing the semantics of the caching and in-memory services, I have realised that it's necessary for ISPN-8440 to be implemented in order for us to satisfy both the conflict resolution and partition handling semantics.
> Adjust merge policies for JDG Online Services
> ---------------------------------------------
>
> Key: ISPN-8400
> URL: https://issues.jboss.org/browse/ISPN-8400
> Project: Infinispan
> Issue Type: Feature Request
> Components: Cloud Integrations
> Reporter: Sebastian Łaskawiec
> Assignee: Ryan Emerson
>
> Both Shared Memory and Caching Service require custom merge policies.
> In Caching Service we need to clear out all conflicted entries upon split brain. Shared Memory service might be a little bit more tricky and we might want to use some different strategy (but that needs to be checked out).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (ISPN-8440) Enabled ConflictResolution on partition merge with PreferConsistencyStrategy
by Ryan Emerson (JIRA)
Ryan Emerson created ISPN-8440:
----------------------------------
Summary: Enabled ConflictResolution on partition merge with PreferConsistencyStrategy
Key: ISPN-8440
URL: https://issues.jboss.org/browse/ISPN-8440
Project: Infinispan
Issue Type: Enhancement
Components: Core
Affects Versions: 9.1.1.Final
Reporter: Ryan Emerson
Assignee: Ryan Emerson
Fix For: 9.2.0.Final
Currently conflict resolution only occurs on a partition merge when the PreferAvailabilityStrategy is utilised (ALLOW_READ_WRITES). This should also occur when utilising the PreferConsistencyStrategy.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months