The Clusters view shows cluster topology as a tree view. In the image above, a cluster named
sbuser contains four running nodes, each of which contains a JVM engine.
A cluster is a logical grouping of one or more nodes. Even a single node launched alone is always part of a cluster, and a node can belong to only one cluster.
StreamBase Studio installs and starts nodes dynamically and automatically when you ask Studio to run or debug an EventFlow or LiveView fragment. By default, Studio installs nodes into a single cluster named the same as the system login name of the user who started Studio. So, by default, the Clusters view shows only the nodes installed by Studio.
If you install and start nodes on the command line with epadmin using the same cluster name, those nodes also appear in the Clusters view.
The currently selected node, shows
(stopped) to indicate that node's state. The
started state does not necessarily mean that the node contains a running fragment, but only indicates that the node is in the installed
and started state.
You can optionally set the Clusters view to show all nodes and clusters in the IP subnet of the current machine.
When Studio exits, it automatically stops and removes any nodes it started in that session. No explicit action is required to either create or destroy a cluster and its member nodes. When all nodes in a cluster are removed, the cluster is destroyed. A StreamBase Application is active as long as a cluster is active and has at least one node installed and running. When all nodes in a cluster are stopped and removed, the application is removed.
The Clusters view's toolbar buttons are convenient shortcuts for their epadmin counterpart commands, such as epadmin stop node and epadmin remove node. To understand the use and need for these buttons, you must understand the node lifecycle for StreamBase Runtime nodes.
Do not use these Clusters view buttons to terminate a normally running fragment!
To stop normally running EventFlow fragments, use the ) in Studio's top toolbar, or its F9 equivalent. (Or see Stopping a Fragment for alternatives.)button (
To stop LiveView fragments, use the Terminate LiveView Fragment button () or its Ctrl+F9 (Windows) or command+F9 (Mac) equivalents.
In the normal Studio workflow, you rarely need to use the Clusters View toolbar buttons. Studio creates and starts nodes automatically, then stops and removes the nodes it opened when Studio shuts down.
So, you only need to stop or remove a node in event of an error condition that has left a node orphaned. You might also deliberately stop and remove a node:
If you have changed the environment, node installation properties, or deployment parameters in a node's Run Configuration dialog. These changes do not affect currently installed nodes, but only take effect when the node is next installed.
If you wish to use Clusters view node management features on nodes you installed and started in the same cluster outside of Studio with the epadmin command.
With these cautions in mind, the following describes the actions of the Clusters view toolbar.
- Stop Node
Stops the selected node.
- Remove Node
Removes the selected node. If you select a node that is currently started, and containing an EventFlow or LiveView running fragment, Studio prompts for confirmation:
- Force Remove Node
Forcefully removes the selected node. If you select a node that is currently started, and containing an EventFlow or LiveView running fragment, Studio prompts for confirmation:
Exports a snapshot of the currently selected node's logs and runtime state, based on the contents of its node directory. This might be requested by TIBCO Support to aid in troubleshooting a failed node deployment.
This button determines the set of installed nodes to display in the Clusters view. The button toggles between showing only the nodes in the same Studio workspace (default) and showing all nodes in the IP subnet of the current machine. Local workspace nodes include nodes installed by Studio even if you change the default cluster name during this Studio session, and those installed from the command line with epadmin, as long as the cluster name matches.
The Cluster name setting can be managed in the → panel of the Studio Preferences dialog, and is the system login name of the current user by default.
Forces a refresh of the displayed clusters and nodes.
When there is an active launch and deployment, selecting a Clusters view toolbar button (epadmin command. For example, selecting the button is analogous to doing a kill -9 command in Linux (a decision to
not perform a graceful shutdown, for some specific reason).
You can copy selected rows in the Clusters view to the system clipboard as plain text or CSV values.
In the Clusters and Nodes panel, you can select one row at a time. Right-click a row to show its Copy action.
In the Properties panel, you can select more than one row by holding the Ctrl key (Windows) or command key (Mac) while clicking to select. Press press Ctrl+A (Windows) or command+A (Mac) to select all rows, or use the Select All option from the context menu. Right-click to show the context menu.
In the Clusters and Nodes panel, the Copy action copies the node name or engine name of the selected row.
In the Properties panel, the Copy action copies both Name and Value cell contents of the selected rows.
- Copy as CSV
Copies the selected rows to the clipboard as a string with Name cell contents separated by a comma from Value cell contents. Following CSV standard practice, quotes are not used to delimit cell values that contain spaces.
- Copy Name
Copies the contents of the selected row's Name cell.
- Copy Value
Copies the contents of the selected row's Value cell. This option has many uses, including:
With a node selected, copy the value from the Node Name row. This lets you paste a long node name into an epadmin command's servicename= parameter without retyping.
With an engine selected, copy the value from the Add Server dialog in the SB Manager perspective.row to copy the fragment's current StreamBase URI into an
Use the Cluster panel of Studio Preferences to specify the default cluster name and to specify the default naming pattern for nodes.