[jira] [Updated] (GEODE-9736) publishes that find no pattern subscribers can cause server to run out of memory
[ https://issues.apache.org/jira/browse/GEODE-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-9736: - Labels: unreleased (was: ) > publishes that find no pattern subscribers can cause server to run out of > memory > > > Key: GEODE-9736 > URL: https://issues.apache.org/jira/browse/GEODE-9736 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: unreleased > Fix For: 1.15.0 > > > Currently each time a publish is done the server will check existing pattern > subscribers to see if they want the publish. If it finds no subscribers it > remembers that and the publish channel. > Since you can just keep making up new publish channels that have no memory, > remembering these can cause the server to run out of memory. > If you hit this problem you will see an instance of > PatternSubscriptionManager with a large "patternSubscriptionCache" > ConcurrentHashMap. It will be full of entries whose value is an instance of > Collections$EmptyList -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9736) publishes that find no pattern subscribers can cause server to run out of memory
[ https://issues.apache.org/jira/browse/GEODE-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-9736: Labels: (was: needsTriage) > publishes that find no pattern subscribers can cause server to run out of > memory > > > Key: GEODE-9736 > URL: https://issues.apache.org/jira/browse/GEODE-9736 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > > Currently each time a publish is done the server will check existing pattern > subscribers to see if they want the publish. If it finds no subscribers it > remembers that and the publish channel. > Since you can just keep making up new publish channels that have no memory, > remembering these can cause the server to run out of memory. > If you hit this problem you will see an instance of > PatternSubscriptionManager with a large "patternSubscriptionCache" > ConcurrentHashMap. It will be full of entries whose value is an instance of > Collections$EmptyList -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9736) publishes that find no pattern subscribers can cause server to run out of memory
[ https://issues.apache.org/jira/browse/GEODE-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-9736: - Labels: needsTriage (was: ) > publishes that find no pattern subscribers can cause server to run out of > memory > > > Key: GEODE-9736 > URL: https://issues.apache.org/jira/browse/GEODE-9736 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Darrel Schneider >Priority: Major > Labels: needsTriage > > Currently each time a publish is done the server will check existing pattern > subscribers to see if they want the publish. If it finds no subscribers it > remembers that and the publish channel. > Since you can just keep making up new publish channels that have no memory, > remembering these can cause the server to run out of memory. > If you hit this problem you will see an instance of > PatternSubscriptionManager with a large "patternSubscriptionCache" > ConcurrentHashMap. It will be full of entries whose value is an instance of > Collections$EmptyList -- This message was sent by Atlassian Jira (v8.3.4#803005)
