Rules
Do Not Pack storm.yaml in an Application JAR Package
If storm.yaml is packed in an application JAR file, a conflict occurs between storm.yaml used by an application and storm.yaml in a cluster after the application is submitted. As a result, the application is unavailable.
Use a decompression tool to decompress the JAR file to check whether the file exists in the root directory. If yes, delete the file.
Do Not Pack log4j-related JAR Packages in an Application JAR Package
If log4j-related JAR files are packed in an application JAR file, a conflict occurs between log4j in the system and log4j in the application after the application is submitted. As a result, the application is unavailable.
Before packing, check whether log4j-related JAR files exist in the application JAR package. If yes, delete the log4j-related JAR files.
Do Not Pack storm-core-X.X.X.jar in an Application JAR File
If storm-core-X.X.X.jar is packed in an application JAR file, a conflict occurs between storm-core-0.10.0.jar in the system and storm-core-X.X.X.jar in the application after the application is submitted. As a result, the application is unavailable.
Before packing, check whether storm-core-X.X.X.jar exists in the application JAR file. If yes, delete it.
Ensure that the JAR Package Packing Code Is Consistent with the Local Project Code When a Topology Is Submitted Remotely
If the JAR file packing code is inconsistent with the local project code, an error is reported during application running.
Last Article: Development Specifications
Next Article: Suggestions
Did this article solve your problem?
Thank you for your score！Your feedback would help us improve the website.