[
https://issues.apache.org/jira/browse/FC-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18061818#comment-18061818
]
Shawn McKinney commented on FC-327:
-----------------------------------
[~ben.manes] based on this explanation It sounds like we want something between
warm replica and hot. The dataset(s) must accept records added locally
(in-process) and periodically refresh to gather records that may have been
added elsewhere (remote processes). Not convinced a caching mechanism is not
needed, because of the extreme cases where the number of objects stored could
overwhelm memory resources. Think millions of records and no serialization to
disk. I haven't run into that use case personally and so it remains an outlier,
one that I'd like to have a good answer for.
> Upgrade from ehcache v2
> -----------------------
>
> Key: FC-327
> URL: https://issues.apache.org/jira/browse/FC-327
> Project: FORTRESS
> Issue Type: Improvement
> Affects Versions: 3.0.0
> Reporter: Shawn McKinney
> Priority: Major
> Fix For: 4.0.0
>
>
> Fortress core uses ehcache v2. It is getting long in tooth, has a number of
> CVE's, and needs to be replaced. Here we'll look at alternatives.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
