Help Center/ MapReduce Service/ Troubleshooting/ Using Storm/ Failed to Submit the Storm Topology
Updated on 2023-11-30 GMT+08:00
View PDF
Share

Failed to Submit the Storm Topology

Symptom

An MRS streaming cluster is installed, and ZooKeeper, Storm, and Kafka are installed in the cluster.

A topology fails to be submitted by running commands on the client.

Possible Causes

  • The Storm service is abnormal.
  • The client user is not authenticated or the authentication has expired.
  • The storm.yaml file in the submitted topology conflicts with that on the server.

Cause Analysis

A user fails to submit the topology. The possible cause is that the client or Storm is faulty.

  1. Check the Storm status.

    For versions earlier than MRS 3.x: Log in to MRS Manager. On the MRS Manager page, choose Services > Storm to check the status of Storm. The status is Good, and the monitoring metrics are correctly displayed.

    For MRS 3.x or later: Log in to FusionInsight Manager. Choose Cluster > Services > Storm to check the status of Storm. It is found that the status is Good and the monitoring metrics are correctly displayed.

  2. Check the submission logs of the client. The logs contain "KeeperExceptionSessionExpireException".

    The preceding error occurs because security authentication is not performed before the topology is submitted or the TGT expires after authentication.

    For details about the solution, see 1.

  3. Check the client submission log. It is found that the "ExceptionInIntializerError" exception information is printed, and the message "Found multiple storm.yaml resources" is displayed. The following is an example:

    This error occurs because the storm.yaml file in the service JAR package conflicts with that on the server.

    For details about the solution, see 2.

  4. If the fault is not caused by the preceding reasons, see Failed to Submit the Storm Topology and Message "Failed to check principle for keytab" Is Displayed.

Solution

  1. An authentication error occurs.

    1. Log in to the node where the client resides and switch to the client directory.
    2. Run the following command to submit the task again: (Replace the service JAR package and topology based on the site requirements.)

      source bigdata_env

      kinit Username

      storm jar storm-starter-topologies-0.10.0.jar storm.starter.WordCountTopology test

  2. The topology package is abnormal.

    Check the service JAR package, delete the storm.yaml file from the service JAR package, and submit the task again.

Parent topic: Using Storm