@niclyx  I think you are diverging form the original query asked in this community question which has an accepted solution. When it comes to a mutual TLS exchange/handshake, this is not something NiFi created or has made any modification to.  There are many different resources on the web to learn about MutualTLS and how it works.  NiFi only cares that the TLS handshake was successful and if no other method of authentication was setup, it received a clientAuth certificate from which it will use the full DN as the identity for the authenticated user. I recommend starting a new community questions if you have new questions. Matt ... View more

I believe the type checking for logical types is more strict now as of https://issues.apache.org/jira/browse/AVRO-2493 and NiFi 1.17.0 (when we upgraded to Avro 1.11.1). Are you using "int" or "string" as the normal Avro type? According the spec (https://avro.apache.org/docs/1.11.1/specification/#timestamp-millisecond-precision) it must be "long". ... View more

@niclyx    You need to be careful with increasing concurrent tasks on components.  Doing so can actually decrease performance if not done carefully.  All components are  requesting thread from the configured thread pools. Over subscribing on one processor can adversely affect others. Did you check disk and network I/O during timeframe of decreased performance? Did you inspect NiFi app log for any warns or errors related to writing new content to content_repository? Did you monitor JVM garbage collection stats (how often and how long they took)? Was performance throughput tied to specific processors within the dataflow(s)?  Where the bottleneck points all dealing with interfacing with an external service? If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt ... View more