[NIFI-12370] DistributedMapCacheClientService leaks threads

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.21.0, 1.22.0, 1.23.2
• Fix Version/s: 2.0.0-M1, 1.24.0
• Assignee: David Handermann
• Reporter: Eric Secules
• Created: 15/Nov/23 01:07
• Updated: 21/Nov/23 17:46
• Resolved: 15/Nov/23 07:30

Description

1. Using the attached flow template first enable and run the flow. This should exercise the cache.
2. run `nifi.sh diagnostics --verbose` and save the file
3. Disable and delete the controller services
4. run `nifi.sh diagnostics --verbose` and save the file with a different name
5. compare the thread dumps. The second file should not have any threads related to the DistributedMapCacheClientService but it will.
6. create and enable new controller services and link them to the Wait and Notify processors
7. run `nifi.sh diagnostics --verbose` and save the file with a different name
8. There should be threads from two separate DistributedMapCacheClientServices like this:

"NettyDistributedMapCacheClient[d06c8ea0-018b-1000-2904-26aa7612632a]-3-1"
"NettyDistributedMapCacheClient[d06c8ea0-018b-1000-2904-26aa7612632a]-3-2"
"NettyDistributedMapCacheClient[d06c8ea0-018b-1000-2904-26aa7612632a]-3-3"
"NettyDistributedMapCacheClient[d06c8ea0-018b-1000-2904-26aa7612632a]-3-4"
"NettyDistributedMapCacheClient[d0774323-018b-1000-5e78-07a7455a2bd2]-5-1"
"NettyDistributedMapCacheClient[d0774323-018b-1000-5e78-07a7455a2bd2]-5-2"

Slack Thread: https://apachenifi.slack.com/archives/C0L9VCD47/p1700009443394479

 

Issue Links

• is related to: NIFI-11580 NiFi does not stop gracefully when using DistributedMapCacheClient and Server
• links to: GitHub Pull Request #8027