Other O&M FAQ and solutions for MaxCompute projects and jobs - MaxCompute

Answers to common O&M questions for MaxCompute projects and jobs.

Category	Questions
Project operations and maintenance	How do I delete a MaxCompute project?
	How do I check the storage space a table occupies?
	How do I view the operation history of a user?
	How do I view resource package information?
	How do I view storage resource usage?
Job management	Can I abort multiple jobs at once?

How do I delete a MaxCompute project?

Log on to the MaxCompute console as an Alibaba Cloud account or a Resource Access Management (RAM) user with the Super_Administrator project role, then follow the steps in Delete a table or a MaxCompute project.

Run DESC <table_name>; in the MaxCompute client to view the storage consumed by a single table.

MaxCompute does not currently provide a way to view total project storage.

Use the audit log feature to query user operation records.

Log on to the ActionTrail Management Console.
In the left navigation pane, choose Events > Advanced Event Query, then select a region from the top-left corner.
If no query information is available, click Create Trail, complete the Quickly Create Trail form, and click Confirm.
On the Advanced Event Query page, filter by:
- Service Name: MaxCompute
- Region: Select the target region
- Event Name: DeleteProject
In the Actions column, click View Details for the matching event.
In the Event Record section, check the userAgent field to identify how the deletion was performed. For example, "userAgent" : "maxcompute.console.alibabacloud.com" means the project was deleted through the console.

Run the MaxCompute list resources command to list the resource packages in a project.

Use Resource Observation to monitor resource usage trends for all projects in a quota group:

Resource type	Information provided
CPU	CPU utilization over a specified period
Memory	Memory usage over a specified period

For detailed storage consumption records, see View billing details.

Batch-aborting jobs is not supported. To abort a job, run kill instanceid for each job individually.