November 2017 - infinispan-issues

[JBoss JIRA] (ISPN-8398) Add authentication support for Caching Service

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8398?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8398: ------------------------------- Status: Open (was: New) > Add authentication support for Caching Service > ---------------------------------------------- > > Key: ISPN-8398 > URL: https://issues.jboss.org/browse/ISPN-8398 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Ryan Emerson > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8466) Use StatefulSets in template

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8466?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-8466. -------------------------------- Resolution: Done > Use StatefulSets in template > ---------------------------- > > Key: ISPN-8466 > URL: https://issues.jboss.org/browse/ISPN-8466 > Project: Infinispan > Issue Type: Enhancement > Components: Cloud Integrations > Reporter: Pedro Zapata > Assignee: Ryan Emerson > > Change deployment model from DeploymentConfig to StatefulSets, for symmetry, keeping the same behaviour in all services and stability. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8463) Add total container memory parameter

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8463?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-8463. -------------------------------- Resolution: Done > Add total container memory parameter > ------------------------------------ > > Key: ISPN-8463 > URL: https://issues.jboss.org/browse/ISPN-8463 > Project: Infinispan > Issue Type: Enhancement > Components: Cloud Integrations > Reporter: Pedro Zapata > Assignee: Ryan Emerson > > Add parameter TOTAL_CONTAINER_MEM - integer, in MiB, no defaults, validate to >= 256 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8468) Add total container memory parameter

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8468?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-8468. -------------------------------- Resolution: Done > Add total container memory parameter > ------------------------------------ > > Key: ISPN-8468 > URL: https://issues.jboss.org/browse/ISPN-8468 > Project: Infinispan > Issue Type: Enhancement > Components: Cloud Integrations > Reporter: Pedro Zapata > Assignee: Ryan Emerson > > Add parameter TOTAL_CONTAINER_MEM - integer, in MiB, no defaults, validate to >= 256 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8008) Add Fault-tolerance to write-behind stores

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8008?page=com.atlassian.jira.plugin.... ] Work on ISPN-8008 stopped by Ryan Emerson. ------------------------------------------ > Add Fault-tolerance to write-behind stores > ------------------------------------------ > > Key: ISPN-8008 > URL: https://issues.jboss.org/browse/ISPN-8008 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Ryan Emerson > Assignee: Ryan Emerson > > Currently when a store is configured to be write-behind, three attempts are made to write the queued modifications to the store. If all three attempts fail, then this error is simply logged and the modifications are never written to the store. > We should allow users to configure a write-behind store so that: In the event that a write-behind fails, further operations on the cache are not allowed and the modifications which failed to write to the store are queued indefinitely. Once the underlying store becomes available, the queued modifications should be written and then the cache should become available. > To determine whether a store has become available again, the AsyncCacheWriter will have to poll the store's availability. Currently the CacheWriter interface does not allow such behaviour, therefore there are two options: > * Attempt a write and catch an exception if the store is not currently available > * Add a method to return the current status of a store to the CacheWriter interface -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8536) Caching service - should_not_blow_up_because_of_oom test is failing

by Roman Macor (JIRA)

Roman Macor created ISPN-8536: --------------------------------- Summary: Caching service - should_not_blow_up_because_of_oom test is failing Key: ISPN-8536 URL: https://issues.jboss.org/browse/ISPN-8536 Project: Infinispan Issue Type: Bug Components: Cloud Integrations Reporter: Roman Macor Assignee: Sebastian Łaskawiec Sebastian is already working on this, creating JIRA just to track this and to have a reference in the test suite because some tests have to have Ignored tag for now. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8462) Enable custom EntryMergePolicy deployments on the server

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-8462?page=com.atlassian.jira.plugin.... ] Adrian Nistor edited comment on ISPN-8462 at 11/15/17 2:38 AM: --------------------------------------------------------------- [~ryanemerson] Are you thinking _DeploymentUnitProcessor_s? We can do it in a much simpler way now that ISPN-7714 is merged. was (Author: anistor): [~ryanemerson] Are you thinking IDeploymentUnitProcessors? We can do it in a much simpler way now that ISPN-7714 is merged. > Enable custom EntryMergePolicy deployments on the server > -------------------------------------------------------- > > Key: ISPN-8462 > URL: https://issues.jboss.org/browse/ISPN-8462 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.2.0.Final > > > It should be possible for users to deploy custom implementations of the EntryMergePolicy interface in the same manner that custom cache stores are deployed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8462) Enable custom EntryMergePolicy deployments on the server

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-8462?page=com.atlassian.jira.plugin.... ] Adrian Nistor edited comment on ISPN-8462 at 11/15/17 2:38 AM: --------------------------------------------------------------- [~ryanemerson] Are you thinking _DeploymentUnitProcessors_? We can do it in a much simpler way now that ISPN-7714 is merged. was (Author: anistor): [~ryanemerson] Are you thinking _DeploymentUnitProcessor_s? We can do it in a much simpler way now that ISPN-7714 is merged. > Enable custom EntryMergePolicy deployments on the server > -------------------------------------------------------- > > Key: ISPN-8462 > URL: https://issues.jboss.org/browse/ISPN-8462 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.2.0.Final > > > It should be possible for users to deploy custom implementations of the EntryMergePolicy interface in the same manner that custom cache stores are deployed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8530) Default value of "merge-policy" xsd attribute should not be a lambda

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-8530?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-8530: ------------------------------------- Thanks, for the clarification regarding parser validation [~dan.berindei], now it looks like a benign bug. > Default value of "merge-policy" xsd attribute should not be a lambda > -------------------------------------------------------------------- > > Key: ISPN-8530 > URL: https://issues.jboss.org/browse/ISPN-8530 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.1.0.Final > Reporter: Adrian Nistor > Assignee: Ryan Emerson > Fix For: 9.2.0.Final > > > A different lambda name gets generated during each build. > So an xsd created and deployed to http://docs.jboss.org/infinispan/schemas/ becomes out of sync after next build. We can fix that by redeploying the schema but we cannot assume users will always re-fetch it. > Using static inner classes (non-anonymous) would be preferable in this case even though the lambda code looks nicer. This solution maintains backward compat with 9.1 too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8500) Off-heap returns expired entries

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8500?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8500: -------------------------------- Summary: Off-heap returns expired entries (was: Off-heap returns expited entries) > Off-heap returns expired entries > -------------------------------- > > Key: ISPN-8500 > URL: https://issues.jboss.org/browse/ISPN-8500 > Project: Infinispan > Issue Type: Bug > Components: Expiration, Off Heap > Affects Versions: 9.1.0.Final, 9.2.0.Alpha2 > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > > When expiration is turned on and off-heap is used, data container returns also entries which should be expired. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2017