@alex15 As this is an older post you would have a better chance of receiving a resolution by starting a new thread. This will also provide the opportunity to provide details specific to your environment that could aid others in providing a more accurate answer to your question.  ... View more

This error is showing that one of your "List" processors is starting and its attempting to migrate the state information from the old way of storing state in the DistributedMapCache, to the new way in the StateManager (ZK or local WAL). The error is because the processor has a DistributedMapCacheClient configured and the client can't connect to the DistributedMapCacheServer. If you have state that you believe needs to be migrated, then ensure that the DistributedCachServer is correctly configured and running, and ensure the DistributedCacheClient is configured with the correct host and port for where the server is running. If you don't have old state that needs to be migrated, just change your "List" processor so that it doesn't use a DistributedMapCacheClient and then it will skip over this migration. The cache client was only required in older versions of NiFi before the internal StateManager was introduced. ... View more

@Oleksandr Solomko have you changed the default value of the "nifi.queue.swap.threshold" property in nifi.properties? If so, you may be running into NIFI-3897. ... View more

Thank You! It works) ... View more