When a MaxCompute job runs slowly or fails, MaxCompute Studio lets you pinpoint the root cause without leaving your IDE. Use the job details view to:
-
Track job progress and resource consumption in real time
-
Identify bottlenecks such as long-tail workers and data skew
-
Examine the execution plan and SQL statement for a submitted job
-
Share or export job details for collaborative troubleshooting
Open a job instance
Two entry points are available.
From a Logview URL or local file
In the IntelliJ IDEA menu bar, go to MaxCompute
This is a common method to view job instance details. It opens the job in read-only mode and works for jobs in other projects — useful when a teammate shares a Logview URL for collaborative debugging.
From Job Explorer
Double-click a job instance in Job Explorer to open it directly.
Interface overview
The job details view has three areas:
-
Toolbar — at the top. Contains actions for stopping, refreshing, copying, and exporting.
-
Properties bar — on the left pane. Displays basic job information.
-
Details views — on the right pane. Contains the following views: Execution, Analysis, History, Script, Details, Summary, Result, and Plan.
Basic information
The properties bar shows the job ID, creator, status, start and end times, computing resource usage, and input and output tables. For running jobs, this information refreshes automatically on a scheduled basis.
Double-click a table name to view basic information about that table.
Monitor job progress
Execution view
The Execution view displays job dependencies as a directed acyclic graph (DAG) across three layers: Fuxi Job, Fuxi Task, and Operation. The Fuxi Task layer is shown by default.
The numbered elements in the view:
| No. | Element |
|---|---|
| ① | Click to switch to another layer |
| ② | Zoom in and zoom out |
| ③ | Dependency table |
| ③ | Fuxi task worker |
| ⑤ | Thumbnail |
| ⑥ | Click to display job dependencies |
| ⑦ | Fuxi Task layer (displayed by default) |
Fuxi Job layer
Click MaxCompute job to switch to the Fuxi Job layer. Each worker in this layer shows the name, start time, and end time of a Fuxi task.
Fuxi Task layer
Double-click a Fuxi job worker to go to the Fuxi Task layer. If multiple Fuxi jobs exist, the Fuxi Task layer of the last Fuxi job is shown by default.
This layer displays task dependencies, input tables, output tables, and partitions. Each Fuxi task worker shows:
-
Instance count — in
a/b/cformat, whereais the number of running instances,bis the number of completed instances, andcis the total. -
I/O records — input and output record counts at the current point in time.
-
Progress bar — an orange bar with a percentage, derived from the analysis of running instances.
-
Connecting lines — each line shows the number of output records; the arrow indicates data flow direction.
After a job completes, open the Progress Chart drop-down list to overlay a heat map on the DAG. Available options:
-
Input Heat Chart (Record)
-
Output Heat Chart (Record)
-
Input Heat Chart (Byte)
-
Output Heat Chart (Byte)
-
TaskTime Heat Chart
-
InstanceTime Heat Chart
The heat map uses different colors to distinguish between the heat sources of different workers.
Operation layer
Double-click a Fuxi task to go to the Operation layer, which shows how the Fuxi task runs internally. Click a worker to view all Operation layer details.
For non-SQL jobs, only the Fuxi Job and Fuxi Task layers are available. The Operation layer is not supported.
Job playback
Job playback lets you replay the execution history of a completed job in 12 seconds, so you can see how subtasks progressed over time, determine their order and relative duration, and identify the critical path.
Click >
Playback estimates I/O data based on execution time — it does not reflect the actual I/O volume at each point in time. Jobs in the Running state do not support playback.
Timeline view
The Timeline view renders the distributed execution of a job as a Gantt chart. Adjust the display granularity to show all compute workers on the chart. Use the available filters to surface:
-
Critical path
-
Workers that processed the largest volume of data
-
Workers with the longest execution time
The Gantt chart makes time bottlenecks and long-tail workers immediately visible across the job.
Diagnose performance issues
Analysis view
The Analysis view shows long-tail workers and workers with data skew, plotted as scatter charts and column charts. Click any worker in a chart to open its details page and inspect the underlying Fuxi instance metrics.
Details view
The Details view shows Fuxi task lists and compute worker lists for SQL data manipulation language (DML) jobs. Each job maps to one or more Fuxi jobs. Each Fuxi job is divided into Fuxi tasks (stages), and each Fuxi task contains multiple Fuxi instances (workers).
The view contains:
-
The Fuxi job tab
-
The Fuxi task list
-
The details and compute worker list for each Fuxi task
Right-click a Fuxi instance to view its standard output, standard errors, and debugging information.
View results and errors
The Result view displays output based on job type:
| Job type | Display |
|---|---|
SELECT with odps.sql.select.output.format set to HumanReadable |
Results in text format |
SELECT without an output format parameter |
Results in table format |
| Script that exports data to a table | Output table name with a link to the table details |
| Abnormal job | Error details |
Other views
| View | Content |
|---|---|
| History | Time consumed in each phase of the job |
| Script | SQL statement and parameter settings for the submitted job |
| Summary | Job details in JSON format |
| Plan | Execution plan |
Toolbar reference
| Icon | Action |
|---|---|
| Expand or collapse the left and right panes to focus on a specific view | |
| Stop the job. Only the project owner or administrator has permission to stop jobs. | |
| Manually refresh the details pane. Basic information about running jobs (status and quotas) refreshes automatically. | |
| Copy the Logview URL | |
| Generate a Logview URL and open it | |
| Save job details as a local file | |
| Toggle auto refresh. When enabled, MaxCompute Studio refreshes all job details on a scheduled basis. |