[JBoss JIRA] (ISPN-11554) Off-heap state transfer does not preserve the timestamp of entries
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11554?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11554:
-----------------------------------
Sprint: DataGrid Sprint #42
> Off-heap state transfer does not preserve the timestamp of entries
> ------------------------------------------------------------------
>
> Key: ISPN-11554
> URL: https://issues.redhat.com/browse/ISPN-11554
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.4.18.Final, 10.1.5.Final, 11.0.0.Dev03
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Dev04
>
>
> The ISPN-4075 fix made state transfer preserve the timestamp of mortal/transient entries with OBJECT and BINARY storage, but not with OFF_HEAP storage.
> {{OffHeapEntryFactoryImpl.create()}} doesn't even receive the entry's created/last access timestamps, instead it always writes {{timeService.wallClockTime()}}.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (ISPN-11556) SFS file location not relative to global persistent-location
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11556?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11556:
-----------------------------------
Sprint: DataGrid Sprint #42
> SFS file location not relative to global persistent-location
> ------------------------------------------------------------
>
> Key: ISPN-11556
> URL: https://issues.redhat.com/browse/ISPN-11556
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration, Core
> Affects Versions: 10.1.5.Final, 11.0.0.Dev03
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 11.0.0.Dev04, 10.1.6.Final
>
>
> Currently if a user specifies the location `/blah` in the SFS configuration, this location will be used regardless of the configure `persistent-location`. Instead, we should create the file location using `PersistenceUtil#getQualifiedLocation` and an exception will be thrown if `/blah` is not the root of the configure `persistent-location`.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (ISPN-11480) GlobalComponentRegistry shutdownHook should call EmbeddedCacheManager#stop
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11480?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11480:
-----------------------------------
Sprint: DataGrid Sprint #41, DataGrid Sprint #42 (was: DataGrid Sprint #41)
> GlobalComponentRegistry shutdownHook should call EmbeddedCacheManager#stop
> --------------------------------------------------------------------------
>
> Key: ISPN-11480
> URL: https://issues.redhat.com/browse/ISPN-11480
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 11.0.0.Alpha2, 10.1.5.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 11.0.0.Dev04, 10.1.6.Final
>
>
> Currently if a SIGTERM is called on a Infinispan processor, the shutdown hook calls {{GlobalComponentRegistry::stop}} which results in caches not leaving the cluster gracefully. In particular this affects the behaviour of 2 node Infinispan clusters when utlised in a Kubernetes StatefulSet, as it will result in the cluster becoming degraded during a rolling upgrade.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (ISPN-11534) Deprecate DefaultCacheManager constructors with default configuration
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11534?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11534:
-----------------------------------
Sprint: DataGrid Sprint #42
> Deprecate DefaultCacheManager constructors with default configuration
> ---------------------------------------------------------------------
>
> Key: ISPN-11534
> URL: https://issues.redhat.com/browse/ISPN-11534
> Project: Infinispan
> Issue Type: Bug
> Components: API, Core
> Affects Versions: 11.0.0.Dev03
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Dev04
>
>
> {{DefaultCacheManager}} no longer has a default cache by default. In order to use the constructors with a default {{Configuration}} parameter, the user also has to define a default cache name in the {{GlobalConfiguration}}, but that is surprising.
> We should remove these constructors, as the user can use the {{ConfigurationBuilderHolder}} constructor to define a default cache (and other caches as well) before starting the cache manager.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (ISPN-11527) Lazily create the org.infinispan.LOCKS cache
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11527?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11527:
-----------------------------------
Sprint: DataGrid Sprint #42
> Lazily create the org.infinispan.LOCKS cache
> --------------------------------------------
>
> Key: ISPN-11527
> URL: https://issues.redhat.com/browse/ISPN-11527
> Project: Infinispan
> Issue Type: Enhancement
> Components: Clustered Locks
> Affects Versions: 11.0.0.Dev03
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 11.0.0.Dev04, 10.1.6.Final
>
>
> Currently clustered locks are not available in the server, however the {{DistributedMassIndexerLock}} depends on a clustered lock, so it's necessary for the org.infinispan.LOCKS cache to be available on the server. However, if indexing is never used this is a waste of resources, therefore we should only create the cache as required.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (ISPN-11538) Always launch the server process in the background
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11538?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11538:
-----------------------------------
Sprint: DataGrid Sprint #42
> Always launch the server process in the background
> --------------------------------------------------
>
> Key: ISPN-11538
> URL: https://issues.redhat.com/browse/ISPN-11538
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 11.0.0.Dev03
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 11.0.0.Dev04
>
>
> Currently {{server.sh}} defaults to executing the java process in the foreground, however we also provide the {{LAUNCH_ISPN_IN_BACKGROUND}} env variable which executes the Java process in the background and forwards any OS signals to it.
> As OS signals are correctly forwarded to the background process by the server.sh script, we should only execute the server in this way. This removes the need for setting the LAUNCH_ISPN_IN_BACKGROUND in the image and tests, whilst removing one other knob from the configuration.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months