Working on a wait-notify setup, but it is running into issues. It is constantly being populated with an "Address already in use" error although there is just the one set of DistributedMapCacheServer and DistributedMapCacheClient controller services. This oddly doesn't immediately cause an issue when these are first created and the wait-notify actually works fine, but on any subsequent runs with the same input file (same Release Signal Identifier) the files do not wait at all and move through immediately.
@TRSS_Cloudera
When you "Enable" the DistributedMapCacheServer Controller service with UUID 5aaa327b-9ebb-1d5a-71ad-a349b8578a25, it is failing to enable because the port configured in that controller service is already being used by some other process on the server.
Do you have multiple DistributedMapCache controller service configured on your NiFi (perhaps they are both enabled and first is already using that port?
Did you check at OS level what process is listening on that port?
My guess here is that you have multiple DistributedMapCacheServer controller services setup configured to use same port. Thus the error on one of them about being unable to bind to the port because it is already in use.
I don't think above has anything to do with issue with your wait/notify flow since you say it works (at least with first FlowFile) as expected.
As far as the behavior of your Wait/Notify dataflow, it is hard for me to make suggestions on what you are observing with out my detail on your dataflow configuration and use case.
If you found this response assisted with your query, please take a moment to login and click on "Accept as Solution" below this post.
Thank you,
Matt
@TRSS_Cloudera
When you "Enable" the DistributedMapCacheServer Controller service with UUID 5aaa327b-9ebb-1d5a-71ad-a349b8578a25, it is failing to enable because the port configured in that controller service is already being used by some other process on the server.
Do you have multiple DistributedMapCache controller service configured on your NiFi (perhaps they are both enabled and first is already using that port?
Did you check at OS level what process is listening on that port?
My guess here is that you have multiple DistributedMapCacheServer controller services setup configured to use same port. Thus the error on one of them about being unable to bind to the port because it is already in use.
I don't think above has anything to do with issue with your wait/notify flow since you say it works (at least with first FlowFile) as expected.
As far as the behavior of your Wait/Notify dataflow, it is hard for me to make suggestions on what you are observing with out my detail on your dataflow configuration and use case.
If you found this response assisted with your query, please take a moment to login and click on "Accept as Solution" below this post.
Thank you,
Matt
