I have disabled config ```"security.delegation.tok...
# troubleshooting
g
I have disabled config
Copy code
"security.delegation.tokens.enabled": "false"
"security.delegation.token.provider.s3.enabled": "false"
in my spec config, job manager is running fine, but facing an issue with the task manager.
issue:
Copy code
2023-09-15 21:00:16,203 INFO  org.apache.flink.runtime.security.token.DelegationTokenReceiverRepository [] - Delegation token receiver hadoopfs loaded and initialized
2023-09-15 21:00:16,203 INFO  org.apache.flink.runtime.security.token.DelegationTokenReceiverRepository [] - Delegation token receiver hbase loaded and initialized
2023-09-15 21:00:16,203 INFO  org.apache.flink.core.plugin.DefaultPluginManager            [] - Plugin loader with ID found, reusing it: external-resource-gpu
2023-09-15 21:00:16,203 INFO  org.apache.flink.core.plugin.DefaultPluginManager            [] - Plugin loader with ID found, reusing it: metrics-datadog
2023-09-15 21:00:16,203 INFO  org.apache.flink.core.plugin.DefaultPluginManager            [] - Plugin loader with ID found, reusing it: metrics-graphite
2023-09-15 21:00:16,203 INFO  org.apache.flink.core.plugin.DefaultPluginManager            [] - Plugin loader with ID found, reusing it: metrics-influx
2023-09-15 21:00:16,204 INFO  org.apache.flink.core.plugin.DefaultPluginManager            [] - Plugin loader with ID found, reusing it: metrics-jmx
2023-09-15 21:00:16,204 INFO  org.apache.flink.core.plugin.DefaultPluginManager            [] - Plugin loader with ID found, reusing it: metrics-prometheus
2023-09-15 21:00:16,204 INFO  org.apache.flink.core.plugin.DefaultPluginManager            [] - Plugin loader with ID found, reusing it: metrics-slf4j
2023-09-15 21:00:16,204 INFO  org.apache.flink.core.plugin.DefaultPluginManager            [] - Plugin loader with ID found, reusing it: metrics-statsd
2023-09-15 21:00:16,204 INFO  org.apache.flink.core.plugin.DefaultPluginManager            [] - Plugin loader with ID found, reusing it: s3
2023-09-15 21:00:16,204 INFO  org.apache.flink.core.plugin.DefaultPluginManager            [] - Plugin loader with ID found, reusing it: s3-fs-hadoop
2023-09-15 21:00:16,204 INFO  org.apache.flink.core.plugin.DefaultPluginManager            [] - Plugin loader with ID found, reusing it: s3-fs-presto
2023-09-15 21:00:16,205 INFO  org.apache.flink.runtime.security.token.DelegationTokenReceiverRepository [] - Delegation token receiver s3-hadoop loaded and initialized
2023-09-15 21:00:16,206 INFO  org.apache.flink.runtime.security.token.DelegationTokenReceiverRepository [] - Delegation token receiver s3-presto loaded and initialized
2023-09-15 21:00:16,207 INFO  org.apache.flink.runtime.security.token.DelegationTokenReceiverRepository [] - Delegation token receiver s3-hadoop loaded and initialized
2023-09-15 21:00:16,207 ERROR org.apache.flink.runtime.security.token.DelegationTokenReceiverRepository [] - Failed to initialize delegation token receiver s3-hadoop
java.lang.IllegalStateException: Delegation token receiver with service name {} has multiple implementations [s3-hadoop]
	at org.apache.flink.util.Preconditions.checkState(Preconditions.java:215) ~[flink-dist-1.17.1.jar:1.17.1]
	at org.apache.flink.runtime.security.token.DelegationTokenReceiverRepository.lambda$loadReceivers$0(DelegationTokenReceiverRepository.java:75) ~[flink-dist-1.17.1.jar:1.17.1]
	at java.util.Iterator.forEachRemaining(Unknown Source) ~[?:?]
saw https://issues.apache.org/jira/browse/FLINK-31839, but it is mentioned that it is already resolved in 1.17.1,
m
Can you add your findings to that Jira ticket?
g
I got the issue, in my custom image, s3-fs-hadoop jar was present in 2 folders in plugins, so got the issue, shouldn't when calling loadReceiver in factor class, it should do a distinct 🤔 , let me know @Martijn Visser, I will be happy to fix this, should I create jira for it. https://github.com/apache/flink/blob/release-1.17.1/flink-runtime/src/main/java/or[…]k/runtime/security/token/DelegationTokenReceiverRepository.java
m
I don’t think you should do a distinct, because you might need multiple dependencies for one plugin.