[GEODE-10206] Geode assumes CMS garbage collector, which JDK 17 lacks

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.15.0
• Fix Version/s: 1.15.0
• Component/s: core, docs, gfsh
• Labels: Java17 pull-request-available
• Assignee: Darrel Schneider
• Reporter: Dale Emery
• Created: 31/Mar/22 18:43
• Updated: 22/Jun/22 20:45
• Resolved: 06/May/22 16:28

Description

Several places in Geode code and documentation assume that Concurrent Mark Sweet (CMS) garbage collector exists, and that these VM arguments are meaningful:

• -XX:+UseConcMarkSweepGC
• -XX:CMSInitiatingOccupancyFraction

The CMS garbage collector is not available on JDK 17. JDK 17 warns that it does not recognize these arguments.

These production classes rely on CMS args at runtime:

• extensions/geode-modules: ResourceManagerValidator.validateSunArguments() recommends configuring the CMS args.
• geode-gfsh: StartMemberUtils passes the CMS args when max heap is set.

These test classes use the CMS args at runtime:

• geode-for-redis: OutOfMemoryDUnitTest passes a CMSInitiatingOccupancyFraction arg when starting a server.

User-facing Javadoc comments on these classes refer to the CMS args:

• geode-core: EvictionAttributes
• geode-core: ResourceManager

Code comments in these classes refer to the CMS args:

• geode-modules: AbstractCache

These properties files in geode-modules-assembly define or refer to the CMS args:

• scripts/setenv.properties
• tcserver/geode-cs/configuration-prompts.properties
• tcserver/geode-p2p/configuration-prompts.properties

These documentation files in geode-docs refer to the CMS args:

• configuring/running/running_the_cacheserver.html.md.erb
• managing/heap_use/heap_management.html.md.erb
• managing/monitor_tune/system_member_performance_garbage.html.md.erb

Issue Links

• links to: GitHub Pull Request #7646