Known issues and limitations in MiNiFi C++ Agent 1.22.10

Learn about the known issues and limitations that you might experience while using MiNiFi C++ Agents. You can find information about the areas of impact, affected product versions, and possible workarounds.

nifi.c2.agent.heartbeat.period must be an integer for EFM validation

EFM fails to parse the agent manifest if the nifi.c2.agent.heartbeat.period is specified using the 'time period' format (for example: '30 sec'). The result is missing metadata and manifest updates, which significantly diminish the management capabilities with EFM.

Workaround

If you use MiNiFi with EFM, change the nifi.c2.agent.heartbeat.period property to an integer in milliseconds. For example use 30000 for 30 seconds, or 5000 for 5 seconds.

Versions affected:

CEM MiNiFi C++ agent 1.22.01 and higher

Fixed in version:

CEM MiNiFi C++ agent 1.23.02-h1

MiNiFi process crash in certain scenarios after C2 property update

If a C2 flow update is used to publish a non-empty flow, and it is followed by a C2 property update with agent restart, without a process/service restart between the flow update and the property update, then the MiNiFi process crashes. If used with the windows service manager or kubernetes, then those service managers automatically restart the agent after a crash. State is persisted as usual, so no data is lost, unless volatile repositories are in use.

Workaround:

None.

Reach out to Cloudera if you need a hotfix for this issue.

Version affected:

CEM MiNiFi C++ agent 1.22.10

Fixed in version:

CEM MiNiFi C++ agent 1.23.02