-
abnormal information
org.apache.nifi.controller.UninheritableFlowException: Failed to connect node to cluster because local flow is different than cluster flow. at org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:1026) at org.apache.nifi.controller.StandardFlowService.load(StandardFlowService.java:539) at org.apache.nifi.web.server.JettyServer.start(JettyServer.java:1028) at org.apache.nifi.NiFi.<init>(NiFi.java:158) at org.apache.nifi.NiFi.<init>(NiFi.java:72) at org.apache.nifi.NiFi.main(NiFi.java:301)Delete the problem node ${NIFI_HOME}/conf/flow.xml.gz file, and then restart the node.
[root@cdh01 conf]$ rm -rf flow.xml.gz [root@cdh01 conf]$ ../bin/nifi.sh restart
Read More:
- When setting up etcd cluster, an error is reported. Etcd: request cluster ID mismatch error resolution is only applicable to new etcd cluster or no data cluster
- A solution to the problem that the number of nodes does not increase and the name of nodes is unstable after adding nodes dynamically in Hadoop cluster
- Elasticsearch cluster cannot be started. The following prompt fails to send join request to master appears
- [Solved] org.mongodb.driver.cluster – Exception in monitor thread while connecting to server node1:27017
- Solve the problem of testing redis cluster“ java.lang.NumberFormatException : For input string: “ [email protected]@17002 “And so on
- Unity Android solves the problem of information flow advertisement closing and error reporting
- The local program cannot access the test environment redis cluster through public IP_ compromise
- Invalid cluster ID. ignore in building Doris database environment
- What to do if you repeatedly format a cluster
- Nacos starts in cluster mode and reports an error
- Redis cli create creates an error when creating a cluster
- Error reported when debugging Hadoop cluster under windows failed to find winutils.exe
- Hadoop cluster: about course not obtain block: error reporting
- (2) unrecoverable error: corrupted cluster config file
- Solution to the problem of failure to elect leaders when offline service is reported in Nacos
- Summary of k8s single master cluster deployment
- After node.js is installed, use the instruction node version in vscode to show that it is not an external or internal instruction. The solution is as follows:
- NxL job cluster nginx routing forwarding and reverse proxy
- Redis cluster error: (error) moved solution
- Spring boot integrates es cluster error report collection