[KAFKA-6288] Broken symlink interrupts scanning the plugin path

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.11.0.2, 1.0.0
• Fix Version/s: 0.11.0.3, 1.0.1, 1.1.0, 2.0.0
• Component/s: connect
• Assignee: Konstantine Karantasis
• Reporter: Yeva Byzek
• Created: 01/Dec/17 02:06
• Updated: 25/Apr/18 09:42
• Resolved: 04/Feb/18 23:12

Description

KAFKA-6087 introduced support for scanning relative symlinks in the plugin path. However, if a relative symlink points to a target that doesn't exist, then scanning the plugin path is interrupted. The consequence is that the unscanned connectors in the plugin path may effectively not be usable.

Desired behavior is that the symlink with the non-existent target is skipped and scanning the plugin path continues.

Example of error message:

[2017-11-30 20:19:26,226] ERROR Could not get listing for plugin path: /usr/share/java. Ignoring. (org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader:170)
java.nio.file.NoSuchFileException: /usr/share/java/name.jar
	at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
	at sun.nio.fs.UnixPath.toRealPath(UnixPath.java:837)
	at org.apache.kafka.connect.runtime.isolation.PluginUtils.pluginUrls(PluginUtils.java:241)
	at org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader.registerPlugin(DelegatingClassLoader.java:181)
	at org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader.initLoaders(DelegatingClassLoader.java:153)
	at org.apache.kafka.connect.runtime.isolation.Plugins.<init>(Plugins.java:47)
	at org.apache.kafka.connect.cli.ConnectDistributed.main(ConnectDistributed.java:70)

Issue Links

• is related to: KAFKA-6087 Scanning plugin.path needs to support relative symlinks
• links to: GitHub Pull Request #4481