[IGNITE-13439] Printing detailed classpath slowdowns node initialization

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.8.1
• Fix Version/s: 2.10, 2.9.1
• Component/s: general
• Labels: 2.9.1-rc
• Release Note: Prevent recursive directory scanning when printing actual classpath
• Assignee: Pavel Vinokurov
• Reporter: Pavel Vinokurov
• Reviewer: Ilya Kasnacheev
• Created: 11/Sep/20 09:28
• Updated: 03/Nov/20 15:10
• Resolved: 21/Sep/20 16:28

Description

If IGNITE_LOG_CLASSPATH_CONTENT_ON_STARTUP is enabled, IgniteKernel#ackClassPathContent parses the classpath and recursively traverses the file system printing all jars and class files.
Traversing the files system could take much time in case of many class files or having a root folder in the classpath.
The reasonable behavior is to print only root classpath folders.

Issue Links

• links to: GitHub Pull Request #8246