[
https://issues.apache.org/jira/browse/GEODE-6310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761213#comment-16761213
]
ASF subversion and git services commented on GEODE-6310:
--------------------------------------------------------
Commit 1d18477daf46fbe285acba904dbe2f6dd52e9c36 in geode's branch
refs/heads/feature/GEODE-6291 from Owen Nichols
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1d18477 ]
GEODE-6310 limit classgraph file descriptor consumption (#3124)
* properly wraps all scanner uses in try-with-resources to ensure
temporary files are cleaned up and file descriptors are closed
* limits thread usage based on heap size, cpu count, and max file
descriptor limits
* removes usage of a non-public classgraph API, to ensure
binary-compatibility with versions of classgraph up to 4.4.12
* based on review feedback, simplify to just always use 1 thread
> upgrade classgraph version
> --------------------------
>
> Key: GEODE-6310
> URL: https://issues.apache.org/jira/browse/GEODE-6310
> Project: Geode
> Issue Type: Bug
> Components: locator
> Reporter: Owen Nichols
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Observed that file descriptor is rapidly increasing to a high value such
> 20K-30K during starting up a cacheserver process with embedded locator.
> Problem goes away when classgraph-4.0.6.jar is replaced with
> classgraph-4.6.7.jar.
> A previous attempt to update Geode's classgraph version (GEODE-5996) was
> reverted due to increased memory usage concerns. In latest classgraph,
> memory usage can now be controlled by limiting number of threads, so we
> should be able to more forward once again.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
