@mt13  Looking at this It seems like the property nifi.cluster.protocol.heartbeat.missable.max made configurable on NiFi 1.12, before this it is using the default value of 8. Which is the reason you are not able to get the expected timeframe results. But instead of looking to tune the timeouts to higher values, you should look to tune the dataflow designs. The lack of heartbeat is mostly occurring due to high resource utilization either memory or CPU or network. The choice of processors and incoming data has to be analyzed for a more stable cluster. In NiFi-1.12 a new feature was added to review the node status history from NIFi UI > Global Menu > Node Status History. It shows the resources utilization in graphical form for each node which would be a great indicator to analyze the load, incoming traffic, heap utilization, etc. ... View more

@Chakkara The behavior you are seeing is looking similar to NIFI-8470 . A quick fix for the issue on NiFi-1.13 is to alter the table column to varchar. The behavior introduced by NIFI-8223 . This is fixed in NiFi 1.14 so an upgrade can be done if table schema alter is not an option. ... View more

Jaro, nipiapi Windows automated testing not attempted.  Are there any particular things you want to achieve using nipiapi+Windows combination?   -Akash ... View more

@justenji  The timestamp details are not exposed by NiFi on Flow but NiFi does maintain it in flow history. [Only if NiFi is secured with SSL] So you can try https://${hostname}:${NIFI_PORT}/nifi-api/flow/history/components/{componentId} to get the details. But it will provide all history of that component you have to parse it as per your need. Note that this info gets purged as per flow history parameters in nifi.properties so you will have these details not from beginning but beginning of the date [days/hours] mentioned in properties. If you are looking for flow timestamp when it is exported to NiFi-Registry then checkout for  https://${hostname}:${NR_PORT}//nifi-registry-api/buckets/{bucketId}/flows/{flowId}    Br, Akash ... View more

@sunile_manjee  I am not very familiar with AWS ELB but you can try to use HandleHttpRequest and HandleHttpResponse processors and check if it serves your use case ... View more