Master Inceptor UI: Navigate Local, Holddesk, and Executors for Optimal Job Management

Local

Similar to the Cluster tab, the Local page records the number of stages in the upper left corner. It shows the current counts of Active, Completed, and Failed stages for the cluster, as illustrated below.

This page indicates that the cluster currently has three Completed Stages and zero Active or Failed Stages.

Storage

The Storage page used to store information about in‑memory tables but has been largely deprecated, so it is not described further.

Holddesk

The Holddesk page provides information about each Holddesk in‑memory table, including Table Name, Block Number, and Total Size. Clicking the Holddesk button opens the interface shown below.

After entering a table link you can see the block locations and sizes; for example, the second row tpcds_holodesk_2.customer_address table is displayed as follows.

The page shows the table name and two lists: Host Information (which machines store the blocks and their sizes) and TableInfo (block names, hosts, and specifications). Users can assess whether block distribution is uniform and detect data skew, adjusting with techniques such as bucketing.

Environment

The Environment page records environment configuration information; it is useful for environment checks, but details are omitted here.

Executors

The Executors page lists information about each executor in the cluster. The list comprises twelve dimensions, as shown in the screenshot.

By examining this list, users can verify that the number of executors matches the expected configuration, check Shuffle Read/Write volumes to judge task distribution, and ensure Executor IDs are continuous (except for the entry). Gaps in IDs indicate executor restarts, which may require performance or resource analysis.

Summary

Understanding and analyzing the Local, Holddesk, and Executors pages helps optimize tasks, detect data skew, and monitor executor health in Inceptor.