Rules
Do not pack storm.yaml in an application JAR package
If storm.yaml is packed in an application JAR package, 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 package 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 packages are packed in an application JAR package, 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 packages exist in the application JAR package. If yes, delete the log4j-related JAR packages.
Do not pack storm-core-X.X.X.jar in an application JAR package
If storm-core-X.X.X.jar is packed in an application JAR package, 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 package. 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 package packing code is inconsistent with the local project code, an error is reported during application running.
Last Article: Application Scenarios
Next Article: Suggestions
Did this article solve your problem?
Thank you for your score！Your feedback would help us improve the website.