During the test, the results appear inconsistent topology and local sandbox environment to start submitted topology running. View log log did not find the problem reason, they had resorted to a remote debugg big move. Here are the steps:
- Configuration yaml increase the allocation topology.work in yaml years. childopts,
topology.worker.childopts : "-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=13006"-agentlib: jdwp = transport = dt_socket, server = y, suspend = n, address = 13006, is on the parameter jdk1.5 + jdwp (Java Debug Wire Protocol) commands specify here socket transmission, use port 13,006 ( You can specify the port itself).
-
Submit submit topology topology command is a command jstorm submitted topology, remember to replace the configuration file for the modified configuration.
-
Enter jstorm nimbus monitoring page, view the topology of the worker to run on which machines.
Find their topology, click enter, 
click on the Task Stats, 
you can see their tasks, select one to record the ip -
Create a remote in the idea of
the task host modified to record ip, port fill 13006 (Custom), click ok to save. - Click the debug button
appears as shown, you can successfully debug the