Nifi: Threads in nifi

help you fix your problem A common way of breaking up tasks in NiFi is to split the flow file into multiple files on the primary node. Then other nodes would pull one of the flow files and process it.
In your case, each file would contain a range of values to pull from the table. Let's say you had a hundred rows and wanted only 3 nodes to pull data. So you'd create 3 flow files each having separate attribute values:

will be helpful for those in need It depends on a few things... if you are running securely then you have certificates that are generated for each node specific to the hostname, so the host in the web requests needs to match the host in the certificates, so you can't use localhost in that case.
It also depends how NiFi's web server is configured. If nifi.web.http.host or nifi.web.https.host has a specific hostname specified, then the web server is only bound to that hostname and may not accept connections with a different hostname. In a default unsecure setup, if you leave nifi.web.http.host blank then it binds to all interfaces.

To fix this issue I would double-check if org.apache.nifi:nifi-api: is in the classpath.
If using maven I would run "mvn dependency:tree" to check.

it helps some times There should be no reason why dev tools interferes with the application. Here is the request shown in dev tools when creating a PG and selecting to import from registry...

this will help NiFi does not support direct username/password login; it integrates with LDAP, Kerberos, or OpenID Connect to perform authentication. Once the user is authenticated, NiFi issues a JWT token which is used on subsequent requests.
(You can also use client certificates, which are sent on every request.)