[ https://issues.apache.org/jira/browse/NIFI-12509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17796709#comment-17796709 ]
ASF subversion and git services commented on NIFI-12509: -------------------------------------------------------- Commit dc3b8cea86183657aaa9d01e3d36679d7f6b1339 in nifi's branch refs/heads/support/nifi-1.x from Simon Bence [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=dc3b8cea86 ] NIFI-12509 Changing default TTL of HazelcastMapCacheClient This closes #8154. Signed-off-by: Peter Turcsanyi <turcsa...@apache.org> (cherry picked from commit 3c4ccd2c647d593c04c0f2dac85df7c5a652d885) > Change default TTL for HazelcastMapCacheClient > ---------------------------------------------- > > Key: NIFI-12509 > URL: https://issues.apache.org/jira/browse/NIFI-12509 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions > Reporter: Simon Bence > Assignee: Simon Bence > Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > Current default TTL is 0, which in terms of Hazelcast means that the cache > will be ever-growing. Having Max Size Policy on the imap (backs the cache) > can be reached via instance (server side) so it looks to be a valid setup to > user 0 TTL. This makes it unreasonable to not allow the value at this point. > Note: `EmbeddedHazelcastCacheManager` has currently no opportunity to set > such a Max Size Policy. -- This message was sent by Atlassian Jira (v8.20.10#820010)