MaxCompute:Service notices in 2024

December 23, 2024 (UTC+8): Notice on support for new regions outside China by MaxFrame

Dear MaxCompute users,

Starting December 23 (Monday), 2024 (UTC+8), Alibaba Cloud will extend its support to include the regions of Singapore, Japan (Tokyo), and Indonesia (Jakarta).

MaxFrame is a distributed computing framework developed by Alibaba Cloud. It supports Python programming interfaces and directly utilizes MaxCompute's computing resources and data interfaces. MaxFrame maintains compatibility with Pandas and Xgboost interfaces, while also automatically implementing distributed processing. This enables Python developers using MaxCompute to more efficiently and conveniently perform large-scale data processing, machine learning (ML) and AI data preprocessing, and model development. For more information, see Overview.

If you have questions, contact technical support through the MaxCompute Developer Community DingTalk group (ID: 11782920), your private DingTalk group, or the official MaxFrame user support DingTalk group (ID: 37130012987).

Thank you for your cooperation.

November 28, 2024 (UTC+8): Notice on the MaxCompute SLA update

Dear MaxCompute users,

Alibaba Cloud will update the service-level agreement (SLA) of MaxCompute. The following content describes the update details.

• Sections 1.1 to 1.10 are added to provide the terms related to service unavailability definition.

• The exception terms (k), (l), and (m) are added to Section 1.11.

For SLA details, see MaxCompute Service Level Agreement.

The new SLA will apply to MaxCompute from January 1 (Wednesday), 2025 (UTC+8). If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

November 14, 2024 (UTC+8): Notice on the security upgrade for MaxCompute LogView

Dear MaxCompute users,

Alibaba Cloud plans to perform a security upgrade for MaxCompute LogView in the following regions from 14:00 on December 2 (Monday), 2024 (UTC+8): China (Hong Kong), China East 2 Finance, China North 2 Finance (invitational preview), China North 2 Ali Gov 1, China South 1 Finance, Japan (Tokyo), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), Germany (Frankfurt), UK (London), US (Silicon Valley), US (Virginia), UAE (Dubai), and SAU (Riyadh - Partner Region). After the security upgrade, the LogView URL generated for a job that is submitted by using the shared resource group for scheduling of DataWorks DataStudio and DataAnalysis is redirected to the MaxCompute console. You can access the LogView URL of the project to which the job belongs only if both of the following requirements are met:

• You have a valid Alibaba Cloud account that has passed real-name verification.

• You are a member of the MaxCompute project to which the job belongs. If you are not a member, you can request the project administrator to add you as a member.

If the identity for accessing the MaxCompute data source configured in the DataWorks workspace is different from the user identity, the user may fail to access the LogView URL of the job because the user is not a member of the MaxCompute project to which the job belongs. For example, a DataWorks workspace is in standard mode. You submitted a job in the development environment to the production environment. If you are not a member of the MaxCompute project in the production environment, you cannot access the LogView URL of the job that you submit and belongs to the project in the production environment.

To prevent the preceding issue, you must make sure that both of the following requirements are met:

• All team members who need to access the LogView URL have created Alibaba Cloud accounts and completed real-name verification.

• Team members are added as members of the MaxCompute project in a timely manner, and the required permissions on the specified objects are granted to the members.

  Note

  For more information about user management and authorization operations, see User planning and management and MaxCompute permissions.

The upgraded Logview will no longer display job execution results by default.

During or after the upgrade, if you have questions about LogView access and permission configuration or require technical support, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

November 13, 2024 (UTC+8): Notice on the release of the intelligent diagnostics feature for MaxCompute jobs

Dear MaxCompute users,

The intelligent diagnostics feature for MaxCompute jobs is released in different regions from November 13 (Wednesday), 2024 (UTC+8). This feature can intelligently diagnose SQL jobs based on the detailed execution information of the jobs.

• Failed jobs: This feature allows the system to match the possible causes and categories based on the error information and provide the relevant error description and solutions.

• Slow-running jobs: This feature allows the system to diagnose the exceptions of jobs, such as resource insufficiency, data skew, data bloat, and mode rollback, based on the resource usage and execution details of a job, and provide the causes and solutions.

This feature can help you identify issues such as job errors or slow-running jobs and allows you to analyze and resolve the issues. For more information about this feature and how to use the feature, see Intelligent diagnostics for jobs.

If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

October 30, 2024 (UTC+8): Notice on the upgrade of MaxCompute Tunnel and implementation of cross-region traffic governance

MaxCompute will upgrade the Tunnel service and perform cross-region traffic governance from November 18 (Monday), 2024 (UTC+8). The following content describes the details.

• Read and write performance and traffic control of Tunnel

  • In Streaming Tunnel, the maximum speed for single-slot data writes is increased from 1 MB/s to 10 MB/s, and the maximum number of single-slot write requests per second is increased from 10 to 100. In Batch Tunnel, the maximum speed for single-slot data writes is 10 MB/s.

  • The method for calculating the number of slots that are used in Streaming Tunnel is optimized. Before the optimization, the number of slots specified when you create a StreamUploadSession interface is considered as the number of slots that are used. After the optimization, one slot is used each time a record is written to a RecordPack object. After the write operation is complete, the slot is released. The optimized method also applies to Batch Tunnel. For more information, see Overview of the data transfer service.

• Cross-region traffic governance

  You cannot connect to a MaxCompute project by using an endpoint of a region where the project is not deployed. You must configure the endpoint or Tunnel endpoint of the region where the project is deployed. For the supported endpoints, see Endpoints.

If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

October 28, 2024 (UTC+8): Notice on the impact of conversions from dynamic partitions into static partitions for all DML operations on the behavior of UPDATE, DELETE, and MERGE INTO operations

Dear MaxCompute users,

From October 24 (Thursday), 2024 (UTC+8), the feature to convert dynamic partitions into static partitions is enabled by default for all DML operations that are performed in MaxCompute. This feature helps improve query performance. The implementation changes the behavior of UPDATE, DELETE, and MERGE INTO operations. When you perform the UPDATE, DELETE, or MERGE INTO operation on a partition that does not exist, the following error messages may appear:

• ODPS-0110061: Failed to run ddltask - Operation DELETE expect target partition exist, but object not found.

• ODPS-0422141: Partition not found - Partition 'projectName.tableName(pt=xxx)' does not exist.

In this case, you can add the session-level configuration SET odps.optimizer.cbo.rule.filter.black=re; to disable the implementation. Then, you can perform the UPDATE, DELETE, or MERGE INTO operation as expected.

If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

October 22, 2024 (UTC+8): Notice on the release of MaxCompute SDK for Go

Dear MaxCompute users,

MaxCompute SDK for Go was released on October 22 (Tuesday), 2024 (UTC+8). MaxCompute SDK for Go is a set of API operations for Go programming. You can call these API operations to send requests written in Go to manage MaxCompute. For example, you can access and manage projects, process data tables, and transfer data. For more information, see Overview of SDK for Go.

If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

October 15, 2024 (UTC+8): Notice on the discontinuation of the Alibaba Cloud classic network connection mode and updates of endpoints in MaxCompute

Dear MaxCompute users,

The Alibaba Cloud classic network connection mode of MaxCompute will be discontinued on November 30 (Saturday), 2024 (UTC+8) and the internal network for connecting cloud services will be used instead. Make sure that you can access your MaxCompute service from a virtual private cloud (VPC) or the internal network for connecting cloud services before the discontinuing date. This prevents network disconnections from affecting your business. The endpoints that are used for access from a VPC or the internal network for connecting cloud services in Alibaba Finance Cloud regions, Alibaba Gov Cloud regions, and regions outside the Chinese mainland are updated. We recommend that you update relevant configurations at the earliest opportunity. For the supported endpoints, see Endpoints.

If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

October 14, 2024 (UTC+8): Notice on the purchase of multiple level-1 subscription computing quotas of MaxCompute for the same Alibaba Cloud account in the same region

Dear MaxCompute users,

From October 14 (Monday), 2024 (UTC+8), MaxCompute allows you to purchase multiple level-1 subscription computing quotas for the same Alibaba Cloud account in the same region. Resources of different level-1 subscription computing quotas are independent of each other.

This feature is suitable for the following scenarios:

• For an Alibaba Cloud account, subscription computing resources of different business packages must be strongly isolated.

• For an Alibaba Cloud account, different financial accounts are required for splitting bills by business. Before this feature is introduced, if you use subscription computing resources of MaxCompute, you cannot use level-2 quotas to split bills. After you enable this feature, you can purchase multiple level-1 quotas to split bills by order.

For more information about the quotas of MaxCompute, see Manage quotas for computing resources in the MaxCompute console.

If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

September 27, 2024 (UTC+8): Notice on the release of the storage cost optimization feature in MaxCompute.

Dear MaxCompute users,

The storage cost optimization feature of MaxCompute will be released in public cloud regions in the Chinese mainland from September 27 (Friday), 2024 (UTC+8). This feature allows you to determine whether the storage tier of a table or partition can be changed from standard storage to infrequent access (IA) or long-term storage based on the default optimization policy and the last access time of the table or partition. The default optimization policy recommends that you change the standard storage tier of a table or partition that is not accessed within the previous 30 days to the IA storage tier and change the standard storage tier of a table or partition that is not accessed within the previous 180 days to the long-term storage tier. You can estimate the storage cost savings (catalog price) after the storage tier is changed. This helps you configure tiered storage policies.

For more information about the feature and how to use the feature, see Optimize storage costs.

If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

September 20, 2024 (UTC+8): Notice on RAM permission management in the MaxCompute console

Dear MaxCompute users,

To ensure security, MaxCompute will provide RAM permission management for specific features in the console from October 8 (Tuesday), 2024 (UTC+8). By default, an Alibaba Cloud account has the permissions to access or manage all features in the console. RAM users can access the features only after they are granted the required permissions. The following table shows the features for which RAM permission management is added and the relevant permission actions.

For more information about permission actions, see RAM permissions.

To ensure the normal use of features in the console, you must grant RAM permissions to RAM users of relevant modules before October 8 (Tuesday), 2024 (UTC+8).

If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

September 19, 2024 (UTC+8): Notice on the invitational preview of new MaxCompute features released at Apsara Conference 2024

Dear MaxCompute users,

At Apsara Conference 2024, several new features of MaxCompute are released for invitational preview. The new features include the data lakehouse solution 2.0 based on OpenLake, SQL-based or MaxFrame-based processing of unstructured data in object tables, Delta Table (incremental table format), incremental computing based on incremental materialized views, and MaxCompute Query Acceleration (MCQA) 2.0. The features are available for trials in the China (Hangzhou), China (Shanghai), China (Beijing), and China (Shenzhen) regions in the public cloud. If you want to dive deep into the features, fill in the application form for the invitational preview of the new features.

After the application is approved, you can try the new features by using one of the following methods:

• MaxCompute console: When you create a project in the MaxCompute console, select Project for Invitational Preview of New Features at Apsara Conference for the Project Type parameter.

• DataWorks console: When you associate MaxCompute computing resources with your workspace in DataWorks Data Studio of a new version for the invitational preview, turn on Participate in Public Preview of DataStudio of New Version for your workspace during the workspace creation process.

September 5, 2024 (UTC+8): Notice on the optimized UI for quota management in the MaxCompute console

Dear MaxCompute users,

The UI for the quota management of subscription computing resources in the MaxCompute console is optimized. The new UI will be available in all regions from September 11 (Wednesday), 2024 (UTC+8). This UI is optimized based on the use of time-based scaling. If you do not need to use the time-based scaling feature of quotas, you can directly configure and manage the quotas of subscription computing resources on the Basic Configurations tab. If you need to use the time-based scaling feature of quotas, you can configure the scaling settings on the Scaling Configuration tab after you configure settings on the Basic Configurations tab.

The following changes occur on the UI for subscription computing resource quota management on the Quotas page in the MaxCompute console.

• The Quota Templates tab is renamed Basic Configurations. On the Basic Configurations tab, you can perform the following operations:

  • Click Edit Basic Configurations to modify configurations. For example, you can create a level-2 quota and configure the basic parameters of the level-2 quota, including the Exclusive or Not, Maximum Number of CUs for a Single Job, Enable Priority, Non-reserved CUs, and Scheduling Policy parameters. You can also configure the Reserved CUs [minCU,maxCU] and Elastically Reserved CUs parameters. However, the two parameters apply only to the effective quota resource configuration plan (previously referred to as the quota plan). If you use time-based scaling, we recommend that you configure the Reserved CUs [minCU,maxCU] and Elastically Reserved CUs parameters on the Scaling Configuration tab.

  • In the quota list on the Basic Configurations tab, delete level-2 quotas. The deletion logic is the same as that before the optimization on the original Quota Templates tab.

• The original Quota Plans and Time Plans tabs are combined into the Scaling Configuration tab, and only the Reserved CUs [minCU,maxCU] and Elastically Reserved CUs parameters are retained. On the Scaling Configuration tab, you can perform the following operations:

  • Create a quota resource configuration plan: This operation is the same as the Add Plan feature. You can configure the Reserved CUs [minCU,maxCU] and Elastically Reserved CUs parameters for quotas.

  • View a list of quota resource configuration plans: You can view a list of quota resource configuration plans and the details of each plan. This helps you compare the plan configurations.

  • Manage the time plans: The capabilities provided by the time plan feature remain unchanged.

  • Preview time-based scaling: This is a new feature. You can select a level-2 quota to view the trend charts of the compute unit (CU) allocation in different time periods.

  • View the global scaling configuration: This is a new feature. You can view the details of all quota resource configuration plans in a table. This allows you to view the minimum and maximum numbers of CUs of all quotas and the number of elastically reserved CUs in different time periods.

For more information about quota management, see Manage quotas for computing resources in the MaxCompute console. If you have questions, contact technical support in your private DingTalk group, join the DingTalk group (ID: 37130012987) for MaxFrame technical support, or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

August 29, 2024 (UTC+8): Notice on RAM permission management in the MaxCompute console

Dear MaxCompute users,

To ensure security, MaxCompute will provide the RAM permission management for specific features in the console from September 10 (Tuesday), 2024 (UTC+8). By default, an Alibaba Cloud account has the permissions to access or manage all features in the console. RAM users can access the features only after they are granted the required permissions. The following table describes the features for which RAM permission management is added and the relevant permission actions.

For more information about permissions, see RAM permissions.

To ensure the normal use of features in the console, you must grant RAM permissions to RAM users of relevant modules before September 10 (Tuesday), 2024 (UTC+8). For example, if you want a RAM user to have management permissions on quotas, you must attach the following policy to the RAM user:

{
  "Version": "1",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "odps:UpdateQuota",
        "odps:UpdateQuotaPlan",
        "odps:UpdateSubQuotas",
        "odps:UpdateQuotaSchedule",
        "odps:CreateQuotaPlan",
        "odps:DeleteQuotaPlan",
        "odps:CreateQuotaSchedule",
        "odps:ListQuotaRoutingRules",
        "odps:CreateQuotaRoutingRule",
        "odps:GetQuotaRoutingRule",
        "odps:RemoveQuotaRoutingRule",
        "odps:UpdateQuotaRoutingRule"         
      ],
      "Resource": "*"
    }
  ]
}

If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

August 19, 2024 (UTC+8): Notice on the upgrade of the resource observation feature in MaxCompute

Dear MaxCompute users,

Metrics that are related to storage resources and job performance are added for the resource observation feature provided by MaxCompute.

• Metrics related to storage resources

  These metrics allow you to view changes in storage resource usage and storage usage distribution. You can view the total storage usage and the storage usage percentages of different storage types in the selected region. You can also view the storage usage trends of different storage types and the detailed table or partition storage information based on the project and the time range that you select. This way, you can determine whether the storage usage unexpectedly spikes. If a spike occurs, you can optimize the top N projects, tables, or partitions that consume the most storage resources at the earliest opportunity.

• Metrics related to job performance

  • These metrics allow you to view the top 10 jobs that consume the most CPU-hours or memory-hours and the top 10 signatures and ExtNodeIds of jobs that are ranked based on the highest total CPU-hours, highest average CPU-hours, highest total memory-hours, and highest average memory-hours within the selected filter range.

  • These metrics allow you to view the top 10 jobs that have the longest durations and the top 10 signatures and ExtNodeIds of jobs that are ranked based on the longest total durations and longest average durations.

  • These metrics allow you to view the trend of data amounts that are scanned by jobs within a period of time.

  • These metrics allow you to view the trend of data amounts that are scanned by jobs per CU-hour within a period of time.

  You can use the preceding metrics to quickly identify jobs that consume the most resources and time, and manage the jobs at the earliest opportunity. You can also compare the data amounts that are scanned per CU-hour to determine whether performance deteriorates in a specific period of time. If performance deteriorates in a specific period of time, you can use the job management feature to identify the cause and resolve the issue at the earliest opportunity.

For more information about the feature and how to use the feature, see Use resource observation.

If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

July 31, 2024 (UTC+8): Notice on the discontinuing of PyTorch algorithm components

Dear MaxCompute users,

PyTorch algorithm components of earlier versions will be officially discontinued in all clusters of Platform for AI (PAI) on August 30, 2024 (UTC+8) due to the overall system upgrade. For PyTorch jobs that are submitted to MaxCompute by using the pai -name pytorch100/pytorch131/pytorch151 PAI command, we recommend that you migrate the jobs before the discontinuing date. We also recommend that you use Deep Learning Containers (DLC) to submit PyTorch jobs. For more information, see Submit training jobs. From August 31, 2024 (UTC+8), existing jobs that use PyTorch algorithm components of earlier versions are no longer guaranteed by the PAI service-level agreement (SLA).

If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

July 18, 2024 (UTC+8): Notice on the discontinuing of specific API operations

Dear MaxCompute users,

Specific API operations of MaxCompute will be discontinued on July 31 (Wednesday), 2024 (UTC+8). The following content describes details.

• Discontinued API operations and new API operations for replacement

  Versions and names of discontinued API operations		Versions and names of new API operations
  Version	API operation name
  2019-06-12	CreateProject	2022-01-04: CreateProject
  	DeleteProject	Not available
  	GetProject	2022-01-04: GetProject
  	OpenMaxComputeService	Not available

• Discontinuation reasons

  • API operations of version 2019-06-12 are no longer available in MaxCompute. This is because the feature implementation method has been changed and long-term system detection results show that no calls are made from external customers.

  • To provide more detailed information about quotas, Alibaba Cloud plans to modify the response content of the GetQuota operation of version 2022-01-04 provided by MaxCompute. Long-term system detection results also show that no calls are made from external customers. Due to the preceding reasons, the GetQuota operation no longer provides services.

• Impacts

  After the API operations are discontinued, the InvalidApi.NotFound or InvalidAction.NotFound error code is returned for calls of the API operations involved in code.

• Replacement or implementation recommendations

  If the code execution depends on the SDKs of the discontinued API operations, such as specific requests, responses, or relevant code in the SDKs, the dependencies may not be found during subsequent upgrades of the SDKs. To address this issue, provide a new method instead or delete the relevant features. If the code directly depends on the discontinued API operations, provide a new method instead or delete the relevant features.

If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

July 4, 2024 (UTC+8): Notice on the availability of the Start Time, Wait Time, and Execution Duration parameters on the Jobs page

Dear MaxCompute users,

MaxCompute provides the following parameters on the Jobs page:

• Start Time: the time when the job received the first batch of computing resources. For jobs that run for a short period of time or do not consume computing resources, such as the jobs that involve DDL statements, the job submission time is used instead.

• Wait Time: the duration from the time the job is submitted to the time the job starts to run.

• Execution Duration: the duration from the start time to the end time of the job.

By default, the preceding parameters are hidden on the Jobs page. You can select these parameters in the Choose Display Fields dialog box to display the parameters. Based on the preceding parameters, you can quickly determine whether a job slowly runs when a long period of time is spent waiting for resource allocation. You can further determine whether the slow job is caused by resource insufficiency or resource competition among multiple jobs based on the parameters and job analysis results. Then, you can optimize job execution, adjust job priorities, or manage computing resources based on your business scenarios.

For more information about the feature and how to use the feature, see Manage jobs.

If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

July 3, 2024 (UTC+8): Notice on the release of the MaxFrame feature

Dear MaxCompute users,

The distributed computing framework MaxFrame is officially released in the China (Shanghai), China (Beijing), China (Ulanqab), China (Shenzhen), and China (Chengdu) regions on July 3 (Wednesday), 2024 (UTC+8). The MaxFrame feature will be available soon in other regions.

MaxFrame is a distributed computing framework developed by Alibaba Cloud. MaxFrame supports Python programming interfaces and allows you to directly use the computing resources and data interfaces of MaxCompute. This way, Python developers can process large amounts of data and develop AI models in a more efficient and convenient manner. MaxFrame is fully compatible with Pandas interfaces and automatically implements distributed processing. You can use the massive computing resources and data of MaxCompute in a more familiar and efficient way to process data, visualize data exploration, and perform scientific computing and development based on machine learning (ML) and AI.

For more information about the features and usage notes of MaxFrame, see Overview.

If you have questions, contact technical support in your private DingTalk group, join the DingTalk group (ID: 37130012987) for MaxFrame technical support, or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

July 1, 2024 (UTC+8): Notice on the availability of computing cost optimization in four regions

Dear MaxCompute users,

The computing cost optimization feature of MaxCompute is available in the China (Hong Kong), Singapore, Indonesia (Jakarta), and Germany (Frankfurt) regions. You can use this feature to generate a resource configuration optimization plan for the computing resources in a level-1 subscription quota based on the actual number of job requests and expected resource configurations. You can also use this feature to generate a resource configuration optimization plan for a project that changes the pay-as-you-go computing resources to subscription computing resources and view the estimated optimization effect. This helps you further reduce computing costs and improve resource utilization. After the release, this feature is available in the following ten regions: China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Shenzhen), China (Chengdu), China (Hong Kong), Singapore, Indonesia (Jakarta), and Germany (Frankfurt).

For more information about the feature and how to use the feature, see Computing cost optimization.

If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

May 17, 2024 (UTC+8): Notice on a security update for MaxCompute LogView

Dear MaxCompute users,

MaxCompute plans to perform a security update for LogView in the China (Chengdu), China (Zhangjiakou), China (Shenzhen), China (Beijing), China (Shanghai), China (Hangzhou), and China (Ulanqab) regions from 14:00 on June 3 (Monday), 2024 (UTC+8). After the security update, the LogView URL generated for a job that is submitted by using the shared resource group for DataWorks, DataStudio, and DataAnalysis redirects you to the MaxCompute console. You can access the LogView URL of the project to which the job belongs only if both of the following requirements are met:

• You have a valid Alibaba Cloud account that has passed real-name verification.

• You are a member of the MaxCompute project to which the job belongs. If you are not a member, request the project administrator to add you as a member.

If the identity for accessing the MaxCompute engine configured in the DataWorks workspace is different from the user identity, the user may fail to access the LogView URL of the submitted job because the user is not a member of the MaxCompute project to which the job belongs. For example, a DataWorks workspace is in standard mode. You submitted a job in the development environment to the production environment. If you are not a member of the MaxCompute project in the production environment, you cannot access the LogView URL of the job that you submit and belongs to the project in the production environment.

To prevent the preceding issue, you must make sure that both of the following requirements are met:

• All team members who need to access the LogView URL have created Alibaba Cloud accounts and completed real-name verification.

• Team members are added as members of the MaxCompute project promptly, and the required permissions on the specified objects are granted to the members.

  Note

  For more information about user management and authorization operations, see User planning and management and MaxCompute permissions.

During or after the upgrade, if you have questions about LogView access and permission configuration or require technical support, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support. Thank you for your cooperation.

May 13, 2024 (UTC+8): Notice on an upgrade of etcd certificates in MaxCompute

Dear MaxCompute users,

{}

If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

May 8, 2024 (UTC+8): Notice on the release of the job performance observation feature in MaxCompute

Dear MaxCompute users,

The job performance observation feature of MaxCompute will be released at 20:00 on May 8 (Wednesday), 2024 (UTC+8). This feature allows you to view the trend of changes in the number of jobs, CU usage, and job runtime durations during a specified period of time.

You can use the metrics to check whether the number of jobs or resource usage surges. This allows you to resolve issues at the earliest opportunity. The system compares job runtime durations during different periods and determines whether the job slowly runs and the job performance deteriorates.

For more information about the feature and how to use the feature, see the "Job performance" section of the Use resource observation topic.

If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

April 30, 2024 (UTC+8): Notice on the storage upgrade of MaxCompute

Dear MaxCompute users,

MaxCompute will perform a storage upgrade for clusters in the China (Hong Kong) region from 10:00 to 16:00 on May 15 (Wednesday), 2024 (UTC+8). Such an upgrade is a low-risk change. The upgrade process does not affect your job in most cases. If your job fails during the upgrade, rerun your job. This issue occurs at an extremely low probability.

If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

April 23, 2024 (UTC+8): Notice on lifecycle changes of MaxCompute projects in regions outside the Chinese mainland

Dear MaxCompute users,

From April 25 (Thursday), 2024 (UTC+8), the pay-as-you-go service is available in the following regions: China (Hong Kong), Japan (Tokyo), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), Germany (Frankfurt), UK (London), US (Silicon Valley), US (Virginia), UAE (Dubai), and SAU (Riyadh - Partner Region). The lifecycles of all projects in the regions are aligned with the lifecycle of the pay-as-you-go service. For the pay-as-you-go service bills generated for storage and download resource usage of projects in the regions, Product Details on the Billing Details tab is changed to MaxCompute (Pay-As-You-Go), and Billable Item on the Usage Records tab is changed to MaxCompute(Postpay). If you purchase subscription resources for your projects in the regions, only the lifecycles of the subscription resources are aligned with the lifecycle of the subscription instance.

If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

April 7, 2024 (UTC+8): Notice on new discounts applied to subscription MaxCompute services

Dear MaxCompute users,

New discounts will be applied to subscription resources of subscription MaxCompute services at 10:00 on April 7, 2024 (UTC+8). The new discounts are provided based on subscription resource specifications such as standard computing resources and Tunnel services. New discount rules:

You can enjoy a 15% discount for 1-year subscription, a 30% discount for 2-year subscription, and a 50% discount for 3-year subscription.

March 14, 2024 (UTC+8): Notice on the migration of ActionTrail event data to MaxCompute

Dear MaxCompute users,

MaxCompute allows you to create a trail by using ActionTrail and migrate ActionTrail events to MaxCompute.

The ActionTrail service allows you to trace and record the event data of your Alibaba Cloud account within the previous 90 days. If you want to analyze event data that was generated a longer period of time ago, you can create a trail by using ActionTrail to deliver the event data to MaxCompute. Then, you can query and analyze the event data.

For more information about the feature and how to use the feature, see Migrate ActionTrail event data to MaxCompute.

If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

February 29, 2024 (UTC+8): Notice on the upgrade of PyODPS nodes in DataWorks exclusive resource groups

Dear MaxCompute users,

The exclusive resource groups of DataWorks in which PyODPS nodes run will be upgraded in each region from April 8 (Monday), 2024 (UTC+8) to May 30 (Thursday), 2024 (UTC+8), to enhance the support for PyODPS. The following table describes the upgrade plan in each region. After the upgrade, the package version of PyODPS nodes remains unchanged.

During the upgrade, ongoing PyODPS jobs may be affected. If a PyODPS job that uses an exclusive resource group fails or other related issues occur, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

February 28, 2024 (UTC+8): Notice on the drills for MaxCompute single-node failures

Dear MaxCompute users,

Drills for service access reliability will be conducted in the China (Zhangjiakou) and China (Chengdu) regions from 15:00 to 16:00 on February 28, 2024 (UTC+8). In most cases, jobs are not affected by the drills. If your job fails due to the drills, rerun your job. This issue occurs at an extremely low probability.

If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.

January 25, 2024 (UTC+8): Notice on the release of the computing cost optimization feature of MaxCompute

Dear MaxCompute users,

The computing cost optimization feature is released on January 25 (Thursday), 2024 (UTC+8) to replace the computing resource optimization feature of MaxCompute.

The computing cost optimization feature is developed based on the computing resource optimization feature. The computing resource optimization feature can generate a resource configuration optimization plan for the computing resources in a level-1 subscription quota. Compared with the computing resource optimization feature, the computing cost optimization feature can also generate a resource configuration optimization plan for changing the pay-as-you-go computing resources of a project to subscription computing resources and allows you to view the estimated optimization effect. This helps you further optimize computing costs and improve resource utilization. For more information, see Computing cost optimization.

If you have questions, contact technical support in your private DingTalk group or join the DingTalk group (ID: 11782920) for MaxCompute technical support.

Thank you for your cooperation.